Related
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?
Hello developers and LG G5 users,
I recently got the LG G5, and everything has been great! Performance is top-notch, display is stunning, and camera takes amazing pictures.
I have the RS988 model, which is the United States carrier unlocked model (not tied to any carrier). It is available at Amazon here: https://www.amazon.com/gp/aw/d/B01DJE22C2/ref=cm_cr_arp_mb_bdcrb_top?ie=UTF8.
I ask with respect and courtesy, does anyone have plans for supporting this model with custom ROMs? I see that the H850 and H830 models are supported, but not the RS988. This model is officially supported by LG for a bootloader unlock, and a working TWRP build is available.
Again, I would like to ask if anyone has plans for supporting the RS988 model with a custom ROM. Fulmics o), Resurrection Remix, AOSPA, Dirty Unicorns, OwnROM, AICP, AOSPExtended, Lineage, ANTHING!
I could even do some light testing, and I'm sure other people feel the same way.
Sincerely,
An LG G5 RS988 user,
Unscedeo
Unscedeo said:
Hello developers and LG G5 users,
I recently got the LG G5, and everything has been great! Performance is top-notch, display is stunning, and camera takes amazing pictures.
I have the RS988 model, which is the United States carrier unlocked model (not tied to any carrier). It is available at Amazon here: https://www.amazon.com/gp/aw/d/B01DJE22C2/ref=cm_cr_arp_mb_bdcrb_top?ie=UTF8.
I ask with respect and courtesy, does anyone have plans for supporting this model with custom ROMs? I see that the H850 and H830 models are supported, but not the RS988. This model is officially supported by LG for a bootloader unlock, and a working TWRP build is available.
Again, I would like to ask if anyone has plans for supporting the RS988 model with a custom ROM. I could even do some light testing, and I'm sure other people feel the same way.
Sincerely,
An LG G5 RS988 user,
Unscedeo
Click to expand...
Click to collapse
It would be nice, I have the same model. I was thinking about getting into Android development and working on this phone but that'll take a good while, most developers probably looked over this phone since it for unlockable so late and really I think stock is enough. I have it modified for my needs and it's alright. And you would think this model would get some development since it's not tied to a carrier but I guess not. If I find where to start and everything I might work on this device and of somehow I figure things out I'll be in development for at least 2-3 years for this device.
Please make custom ROM for rs988
You're to late Guys. The G5 is almost completely abdoned and the Most Devs (Who had a Choice) are gone. Outdated 7.0 Stock Firmware and a lack of good Sources are killing the Rest. Besides that is asking for any Development on it just crazy. You don't need to ask! If there is nothing, there will come nothing....
Never LG again! To many mistakes and not a piece Developer friendly at all. Try to sell Your G5 and You will See what i mean!
He's right about the lack of good sources I had an H830 and the roms for it take away useful features for the lg g5. And all have the same bugs. I tried them but kept going back to stock.
There used to be a time when custom roms made the phone better. That time seems to have passed, it is getting harder and harder to root carrier phones, not just lg.
The rs988 is a smooth running phone, with root we get full control of our phone. If you are not happy with that feel free to port over a rom, but please stop asking for dev support.
We are on our own with this phone.
I'm kinda glad this phone has been abandoned and looked upon so poorly.
I bought a brand new rs988 build date 3/17 for 249.00 B&H Photo about 6 weeks ago. The build quality is better, the screen is better, and no gps issues.
Since the Nougat update the phone is so much improved but if you don't like Nougat you can always downgrade back to marshmallow. (benefit of unlocked bootloader)
I bought genuine batteries from NewEgg recently for 5.99 a piece.
It's one of the few unlocked phones that work on Verizon.
But for me the "always listing" (just like the pixel) very few phones have that feature. The removable battery, the IR blaster, expandable storage are requirements.
If I need waterproofing I throw on my fre lifeproof I bought new for 20 bucks.
Just because something is hard doesn't mean it's not worth it. This phone has been given up on too quickly.
At the current price I wouldn't be surprised if some come back to it.
Peace
Yes, I understand everyone's thoughts about development stopping for the LG G5. I am rooted and the stock ROM is excellent, I was just simply inquiring about custom ROM status. Didn't mean to bug or annoy any developers. It would just be nice if there was support, that's all.
wolfu11 said:
I bought genuine batteries from NewEgg recently for 5.99 a piece.
Click to expand...
Click to collapse
By the way, could you send me the link to this? That price is just insane. The lowest I've seen is $11 at Walmart.
Tbh even though I have an h850 I don't see development stopping for custom ROMs on G5, it's being worked on. Slowly yeah,it's summer time,can't expect anyone to give up on some holiday and enjoyment to tinker around. Most of the stuff is already there to support RS988. LineageOS is official for G5,Mokee is official for G5 (2 versions on both for now), besides NFC bug(that's being worked on and there's already a half working solution) Bluetooth bug (not syncing to some products but working) and video saving( just a matter of time when it will be fixed) G5 in general is a fully supported by custom ROMs.We have a lot of unofficial builds too. Getting an official build instead of unofficial one is an advantage not a deal breaker and building your own build isn't that hard anyway. I've studied that for 5 days and have a build for H850 already. And it just took me 5 days cause of my slow internet speed. So a negative attitude won't do any good, positive thinking,catlogs, sharing your findings, sharing your fixes, might see a change.
If you can't wait, build
onestyle007 said:
Tbh even though I have an h850 I don't see development stopping for custom ROMs on G5, it's being worked on. Slowly yeah,it's summer time,can't expect anyone to give up on some holiday and enjoyment to tinker around. Most of the stuff is already there to support RS988. LineageOS is official for G5,Mokee is official for G5 (2 versions on both for now), besides NFC bug(that's being worked on and there's already a half working solution) Bluetooth bug (not syncing to some products but working) and video saving( just a matter of time when it will be fixed) G5 in general is a fully supported by custom ROMs.We have a lot of unofficial builds too. Getting an official build instead of unofficial one is an advantage not a deal breaker and building your own build isn't that hard anyway. I've studied that for 5 days and have a build for H850 already. And it just took me 5 days cause of my slow internet speed. So a negative attitude won't do any good, positive thinking,catlogs, sharing your findings, sharing your fixes, might see a change.
If you can't wait, build
Click to expand...
Click to collapse
Hiya, have you got any good guides I can possibly use to start building from source? I would love to do this.
Thanks
seraphism said:
Hiya, have you got any good guides I can possibly use to start building from source? I would love to do this.
Thanks
Click to expand...
Click to collapse
I'm on my phone now,but have some bookmarked on my laptop. When I get home I'll pass some. For starters search XDA and use Google building Android from source, plus go on LineageOS manifest GitHub. Repo sync first,it will take a while. By the way, you'll need a stronger PC or laptop if you want to build fast also Linux or osx or on Windows you'll need Linux in virtual PC. SSD drive recommend.
Unscedeo said:
Yes, I understand everyone's thoughts about development stopping for the LG G5. I am rooted and the stock ROM is excellent, I was just simply inquiring about custom ROM status. Didn't mean to bug or annoy any developers. It would just be nice if there was support, that's all.
By the way, could you send me the link to this? That price is just insane. The lowest I've seen is $11 at Walmart.
Click to expand...
Click to collapse
Unfortunately they are sold out now....
View attachment 4212964
View attachment 4212965
Don't get Me wrong. I've put much efforts into this Phone since i still think it's a good piece of Hardware. I'm also Out of Money so i have to stick with it. But it makes Me crazy sometimes as a Ex Samsung, HTC, SONY and Nexus User/Dev to have a LG.
-The Sources
-The Community (XDA)
-The Bootloader (Recovery Access, Bootloader Message)
-The Build Quality (Light Shadows on the Display, the bottom Gap, Volume Rocker Stucks)
And the most Important Thing - UPDATES
We are using a 2016 Flagship and No Android 7.1? Still?
What about Android 0? Do we get a real Update or just a Copy OS from the V20? Like with the actual/past Updates?
I'm really done with LG. That they ditched us with the Modules is another Big Point for Me as G5 User. I would at least be more happy with a V20 since it wasn't a Joke like the G5....
For those interested, the following LG G5 variants have the same FCC ID of ZNFVS987:
Code:
VS987 - Verizon Wireless variant
US992 - U.S. Cellular variant
RS988 - General North America variant
Presumably, the variants are of the same hardware, but have different firmware.
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
onestyle007 said:
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
Click to expand...
Click to collapse
OK, great! Thank you for starting the development train.
I am new to this kind of stuff, but I am willing to do it. Is have some knowledge of ADB/Fastboot and looking at partitions. So basically what I need to do is extract the boot.img from my phone, and then create a device tree for the phone. Where should I put the tree when it's done?
Unscedeo said:
OK, great! Thank you for starting the development train.
I am new to this kind of stuff, but I am willing to do it. Is have some knowledge of ADB/Fastboot and looking at partitions. So basically what I need to do is extract the boot.img from my phone, and then create a device tree for the phone. Where should I put the tree when it's done?
Click to expand...
Click to collapse
When all that is done,well then you or any other developer uses that tree with already synced repo from any of the custom ROMs along with the G5 repos to try and make a build.
First thing's first,to get a device tree. Building a rom from the source comes later, and luckily there's more than one tutorial on how to get it done. Then it's figuring out what doesn't work and how to fix it.
Source?
So I extracted boot.img, have the file. When I go to the link you gave me for creating a device tree, it says that I need the source code. Sorry if I'm acting like a noob, but where do I get that? I found this link: http://opensource.lge.com/osSch/list?types=NAME&search=lgrs988, but I don't know if I should use it.
Unscedeo said:
So I extracted boot.img, have the file. When I go to the link you gave me for creating a device tree, it says that I need the source code. Sorry if I'm acting like a noob, but where do I get that? I found this link: http://opensource.lge.com/osSch/list?types=NAME&search=lgrs988, but I don't know if I should use it.
Click to expand...
Click to collapse
Can you screenshot what exactly it's asking from you? And by the way, I doubt it's lg open source, probably just google android source. But let me see it first.
By the way, another tut on how to make a device tree
https://forum.xda-developers.com/showthread.php?t=2010281
onestyle007 said:
Can you screenshot what exactly it's asking from you? And by the way, I doubt it's lg open source, probably just google android source. But let me see it first.
By the way, another tut on how to make a device tree
https://forum.xda-developers.com/showthread.php?t=2010281
Click to expand...
Click to collapse
Never mind, I figured out how to unpack the boot.img. I now have the basic files created, including AndroidBoard.mk, AndroidProducts.mk, etc. I just created the files that are listed in this tutorial (the one you gave me): https://forum.xda-developers.com/showthread.php?t=2010281
So I also found this on Github, which states that it is the device tree for the RS988: https://github.com/jcadduono/android_device_lge_rs988. I don't know if that is what you want me to make, and if it is, can we use that? If that isn't the right tree, I am currently on writing the BoardConfig.mk file, which is one of the steps in the tutorial mentioned above. it says to use a "cousin device" tree. What should I use for that?
Thanks
Thanks for this..
Again.. thanks for the heads up on how to get the ball rolling on this.. I should have some time to unlock my bootloader and post the boot.img and other necessary files this weekend..
Cheers!
onestyle007 said:
Okay,let's start with the basics. First we are going to make the device tree so at least devs without your phone version would try to build a custom rom ( non stock based) for rs988.
Following parts of this tutorial extract boot.img and share it here.
https://forum.xda-developers.com/showpost.php?p=45721523&postcount=1
Then after that, following this tutorial we'll make your device tree.
https://forum.xda-developers.com/showpost.php?p=69576711&postcount=1
Click to expand...
Click to collapse
Any luck with our rs988? ?
Sent from my SM-G950N using Tapatalk
Once galactic stryder started to collected crowd funding to buy a new le max 2 and then also ordered it and then it now arrived because of some issues. Anybody can tell me what happened to the money of yours you donated? And why he is not developing? Just curious to know that!
Heyyo, he posted a while back that he has had stuff going on in life so it was delayed a few months for software development.
Tbh even once he starts it could be a few months before he has a properly working x2 build as he uses his own kernels with some stuff based on Darkobas (Oreo) and I haven't seen anything happening there either... So really who knows when we shall see some AOSPA x2 stuff.
Such is the way with crowdfunding anyways. We funded a device for him and it will take time for things to get done. I know I donated a bunch too but hey I am barely making progress on Oreo but I try with my limited software development skills and time.
He wrote to me that let max 2 "will be supported on our AOSPA 8 from April"
Let's wait for the guy solve his issues. Nobody forced us to donate. I am sure that he didn't run away with the LeMax2 :laugh: Any user should understand that developers are also people with jobs, family, etc. Heck, even to reply to xda Q&A takes time (thanks @ThE_MarD), so it's often to see that there's no answer from the dev to "why torch is not working" question or stuff like that.
Honestly speaking, even without him, the development of X2 is at a very good level by my standards.
I think we should also donate to infrag and all the others who worked really hard to fix the builds for this device.
Thanks to all for info
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
nope that's not correct bro recently he updated his profile and added le max2 and I can see some commits done in his lambda kernel so everyone cheers and hope for good
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
Forgive me, but it's a sad statement.
Actually, a passionate and skilled guy who did a good job with a very similar phone, offered to work on improving support for this device. I can't event think he needed another underpriced (because of lack of official support from manufacturer, bankrupt) smartphone
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
He is very active kernel dev for Le pro 3, so it wasnt like, hey lets give new phone to random guy.
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thanks for clearing situation
Nice to see you after long break, hope you like yours new device
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thank you galactic stryder!
https://forum.xda-developers.com/showpost.php?p=75925873&postcount=318
Wear 24 DevelopmentContributors: @JaredTamana, @davwheat
Current Status: ActiveCurrent Kernel Status: Building, NFC driver working but still potentially WIPSystem ROM Status: Still WIP. Current task: collecting/compiling files, modifying .jarsTHIS ROM IS NOT YET AVAILABLE TO DOWNLOAD AS AN END-USER ROM
This project has a few goals:
- Bringing NFC/Google Pay support to Wear24 [Feasible, main goal]
- Bringing system updates to the Wear24, ie System H [Probably doable, second goal]
- Adding/fixing functionality in the Wear24 (such as new radio bands, no cloud icon, etc) [Maybe possible but needs more research, low on the list)
- Other projects are being considered for the Wear24, but no news on them at this time.
Links
Social
Wear24Dev Blog, periodic updates on this project: http://wear24dev.blogspot.com
Wear24 NFC Discord, open chat so users can see us develop in real-time! Also, tech support. https://discord.gg/8XyTeUC
Development
Wear24-NFC-Kernel GitHub, this is our source for building the kernel. Instructions for building it yourself are in the README. https://github.com/davwheat/Wear24-NFC-Kernel
Travis-CI Build Logs for Kernel: https://travis-ci.org/davwheat/Wear24-NFC-Kernel
Wear24-NFC-ROM GitHub, will soon contain the files needed to make an image/zip, depending on how we decide to distribute. https://github.com/davwheat/Wear24-NFC-ROM
JaredTamana's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/folders/1h6gz-oLMPZ90nwt7BLhWVgHii1DRCW5c
davwheat's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/fold...droid-msm-dorado-3.18-nougat-mr1-wear-release
tetra release for enabling NFC: https://forum.xda-developers.com/sm...ony-smartwatch-3-nfc-support-package-t3219713
NXP Setup Guidelines: https://github.com/NXPNFCProject/NF...r/AN11762-Android_NXP_NFC_Setup_Guideline.pdf
Special Thanks
janjan: Dev guidance
@bensdeals: Donor, help
@yochanmarquos, u/lerxi: Development help.
-- RESERVED -- Because you never know
Someone should have a TWRP backup handy with the images you are looking for. Correct me if I'm wrong, but all the images you require are inside a TWRP backup image.
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Please. I beg you to make this happen. Thanks for even trying
I'm definitely interested in this. If I knew I could get Google Pay working on this device, I would definitely buy one. I'll happily throw a few dollars your way too, if you can release something that works.
Hoping I found it
JaredTamana said:
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Click to expand...
Click to collapse
Is this what you're looking for? (Sorry, I'm not allowed to post url yet so just remove space before .com)
github .com/FlorentRevest/android_device_sony_tetra
My Wear24 just came in from eBay . It's a really good looking device. I might be able to help you test at some stage. Also willing to donate ducats if you get far enough. Good Luck :good:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
YTSec said:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
Click to expand...
Click to collapse
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
** NEWS **
Semi-daily updates will be going on this Blogger Page so I don't clog up the thread
http://wear24dev.blogspot.com
Hi, can i flash this rom to zte quartz 2017?
Hi, can i flash this rom to zte quartz 2017?
Eshal said:
Hi, can i flash this rom to zte quartz 2017?
Click to expand...
Click to collapse
Eshal, this ROM hasn't even been built yet. I cannot guarantee compatibility with your device because I'm not building for your device. You can try flashing whatever you like, but I'm not liable for your device.
This ROM is still in its first steps and I quite literally have nothing to release yet. I've just finished bringing backups over to my PC.
JaredTamana said:
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
Click to expand...
Click to collapse
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
YTSec said:
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
Click to expand...
Click to collapse
Glad to hear it! Make sure to read the main thread as to tips on how to do it. Use lots of heat, and don't forget the Y000 (0.6) screwdriver.
Kernel builds are now passing, and I've begun debugging the boot process. More info on the Blogspot
Sorry for the late reply, I'm just waiting on a toolkit that works on it, then I'll start ripping it apart to help out! Also, I got that new UI which is great.
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
VlitalityX said:
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
Click to expand...
Click to collapse
Hiya! Sorry for the lack of updates. I've hit a wall with that Binder error. All documentation online seems to be about x86 machines and ranges from IO errors to SELinux errors. I've already tried compiling without SELinux in a few different ways to no avail. I've tried contacting development channels on IRC, but no one seems to have the answers I need (most times I don't even get a reply...)
I'm still brainstorming. I took a look at the kmsg from the stock build and there's a LOT being sent to logs there that isn't from my kernel. I'm not sure where to go next, and I don't want to go knocking on the door of every single developer that might know the answer. The problem is the Binder errors are so vague about what's causing the failed transaction that I can't even start to understand what's wrong.
yochananmarqos said:
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
Click to expand...
Click to collapse
Thanks! I do remember seeing this. Problem is, if I can't even build a stock kernel, nothing else can be done. I need the device booting first before I can move to system changes.
I wrote an email to the chief technical officer of ZTE and asked if development for the Axon 7 is still ongoing. Here is a screenshot of the answer.
Can you link exactly who you wrote to? I would like to confirm this.
MishaalRahman said:
Can you link exactly who you wrote to? I would like to confirm this.
Click to expand...
Click to collapse
Pm for now to avoid possible email spamming.
As for all the others who read this, here is a little more explanation:
He is the technical chief officer of zte and stands in direct contact with the dev team. He is also the reason we got the zip for disabling system write protection in the first place. Without him i wouldn't have gotten the update.zip (with disabled system write protection) and @raystef66 couldn't have made a flashable zip for us.
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
amphi66 said:
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
Click to expand...
Click to collapse
Volte works on Oreo china
amphi66 said:
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
Click to expand...
Click to collapse
VoLTE should work on any of the big Oreo ROMs. WFC is hit or miss (even on stock ROM). I'm assuming Oreo is gonna be the last android version we can install and still have these things work (unless some dev out there finds a way to get past this roadblock in the future). Either way, I kinda doubt ZTE would provide any further updates for us beyond Oreo. I'm assuming that the response given in the OP meant that they would fix everything that's still broken and missing on 8.0; not begin development for Pie (especially since the Axon 10 is just around the corner, pulling resources into a 3-year-old phone just isn't a sound decision from a business standpoint).
HunterBlade said:
pulling resources into a 3-year-old phone just isn't a sound decision from a business standpoint).
Click to expand...
Click to collapse
It is if ZTE expect some form of customer loyalty on future purchase decisions. Would you buy the Axon 10/11/12 etc. based on your Axon 7 experience? Yes they had disruptions from trade sanctions etc. but that's not the consumers fault and imo ZTE should be doing everything they can to restore faith in their brand.
They're basically starting again.
They need an affordable flagship like the Axon 7 was. If they don't, it will be hard to gather enough sales to start a customer pool and try for return purchase later on.
Current customers are wary, sceptical and untrusting after that whole fiasco and rightly so.
amphi66 said:
Great contact! Thanks.
Anyway to get the PIE IMS so we can get wifi calling working on Oreo or Pie?
Click to expand...
Click to collapse
VoLTE nd Wifi calling wok fine for me on ZTE's Oreo B20.
RobboW said:
They're basically starting again.
They need an affordable flagship like the Axon 7 was. If they don't, it will be hard to gather enough sales to start a customer pool and try for return purchase later on.
Current customers are wary, sceptical and untrusting after that whole fiasco and rightly so.
Click to expand...
Click to collapse
They just need to copy and paste the Axon 7 with newer specs.
Maybe bumping it to 6" in order to have more internal space would do the trick.
I still can't understand how did they think that the Axon 9 Pro was a good idea. They litterally took all that was great about the A7 and...deleted it.
Now...a bit of an on topic question. Instead of releasing 8.0, could they not enter the Android One program with it...especially since they were aiming for stock experience?
Maybe it's been asked before, but what are the implications of entering the AO program,because IIRC, I may have read some time ago something about a partition not existing on the device and ZTE not gambling with a large release, but I can't remember specifically?
TorqueSsS said:
They just need to copy and paste the Axon 7 with newer specs.
Maybe bumping it to 6" in order to have more internal space would do the trick.
I still can't understand how did they think that the Axon 9 Pro was a good idea. They litterally took all that was great about the A7 and...deleted it.
Now...a bit of an on topic question. Instead of releasing 8.0, could they not enter the Android One program with it...especially since they were aiming for stock experience?
Maybe it's been asked before, but what are the implications of entering the AO program,because IIRC, I may have read some time ago something about a partition not existing on the device and ZTE not gambling with a large release, but I can't remember specifically?
Click to expand...
Click to collapse
The vendor partition stuff is something else entirely. Some people believed that ZTE would bring Treble support to the Axon while that made very little sense (Treble is a requirement for phones that SHIP with Oreo and above, but it's optional for Oreo, and its main advantage is it makes it easier for OEMs to update major Android versions). It was developed by djkuz and NFound eventually anyways, but only because of the generic ROM benefits
I don't think you can simply slap Android One certification on the middle of a product's life, but even if they could, it would make absolutely zero sense for them... Why be commited to security updates and newer Android versions on a phone that has surely stopped giving any revenue since long ago? Plus I'm not even sure if people prefer stock Android to stuff like One UI where you have a bunch of options
Do not expect to much from ZTE for the Axon 7. Until now they did not release a stable OS and it will not change for the next update.
dodo34 said:
Do not expect to much from ZTE for the Axon 7. Until now they did not release a stable OS and it will not change for the next update.
Click to expand...
Click to collapse
Marshmallow and Nougat were perfectly stable, if not the chinese versions. i'd say that counts.
The important thing is them fixing Daydream because it doesn't only entail adding daydream back, to run it properly you need to have thermals and the kernel properly tuned. Daydream should put the phone at ~1.3 GHz but I believe they'll have to mess around to make it work as intended anyways
plus all this is useful for LOS
Marshmallow and Nougat had a very bad design and UI because of mifavor. Oreo is nice but extremly unstable.
dodo34 said:
Do not expect to much from ZTE for the Axon 7. Until now they did not release a stable OS and it will not change for the next update.
Click to expand...
Click to collapse
What next update?
I thought this device was EOL as far as zte was concerned. There hasn't been an official update since august of last year and that had a security update of july '18. That's 6+ months ago. I think we're on our own now....
gpz1100 said:
What next update?
I thought this device was EOL as far as zte was concerned. There hasn't been an official update since august of last year and that had a security update of july '18. That's 6+ months ago. I think we're on our own now....
Click to expand...
Click to collapse
how can you ignore the OP this much??
??
seriously, read the OP first
Also, the chinese version still gets updates, the last one was abt 2 weeks ago?
Choose an username... said:
how can you ignore the OP this much??
??
seriously, read the OP first
Also, the chinese version still gets updates, the last one was abt 2 weeks ago?
Click to expand...
Click to collapse
Not ignoring OP at all... Simply going by zte's past actions. I've seen these sort of promises with other devices (moto x pure comes to mind) in the past. I'll believe it when I see it.
Got a link to this update from 2 weeks ago? What was the actual update?
gpz1100 said:
Not ignoring OP at all... Simply going by zte's past actions. I've seen these sort of promises with other devices (moto x pure comes to mind) in the past. I'll believe it when I see it.
Got a link to this update from 2 weeks ago? What was the actual update?
Click to expand...
Click to collapse
All I'm saying is, @GodOfPsychos contacted this ZTE guy, he said that an update was going to be released, and then XDA'S EDITOR IN CHIEF contacted that guy and got the same response (with which an article was made). They can bail at any time, but it's not like they are promising Pie anyways
I'm guessing you can't see the attached screenie in the OP? I can see it just fine from XDA Labs
We won't get official Android Pie for Axon 7.
The most I read into that is update to include cut out features like Daydream, probably a security update too. Just a finish of what Oreo 8.0 was supposed to be. I don't think we will even see official Oreo 8.1
If they had just kept with the whole "best sounding phone" idea I'd probably already have bought another ZTE. It was the thing that distinguished them in the crowded market of samey-same phones. At this point I'm clinging to my Axon 7 with my tight little hands, and any update to its stability will be appreciated. [Full disclosure, I'm running the GSI Liquid Remix unofficial build of Pie, but if they do update the official Oreo and get it rock solid, I could see downgrading just to be on an official ROM.]