Database Users

[Q] Is it as simple as compiling cyanogenmod?

Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.

evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?

s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.

I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.

Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.

@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers

What about devices that have CM10 only?

lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.

JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.

As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.

mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.

Please, support for RAZR i (x86)

lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)

Hello!

Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
How come there is only one cm based kernel?
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care

Rudjgaard said:
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Click to expand...
Click to collapse
Welcome to this forum and I hope you'll enjoy working with the community here
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
Click to expand...
Click to collapse
AFAIK, there aren't any CM bug now, there was a camera lag at start up weeks ago, but now it's solved,
the only thing left is that camera quality on AOSP-Based ROM is not as good as it is on stock Sony FW,
The great thing going on now is that we're gonna have official AOSP support from Sony soon (all thanks to @jerpelea)
check these:
Unified kernel for msm8974 devices
Xperia AOSP Project
these are still new and their early stages, and hopefully we'll start using them soon:good:
How come there is only one cm based kernel?
Click to expand...
Click to collapse
To be honest, there aren't many devs how own or work for this device, even the cm-based kernel we have is ported from Z1 !
also I'm working on a brand new one with the latest features, but I think it'll take some time
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Click to expand...
Click to collapse
Well as I mentioned, we don't have any major problems, as this device can get whatever Z1 can get, and Z1 is popular
except for one thing! the double tap to wake feature can't be ported from Z1 to our device as the two devices don't share the same touchscreen!
That's all I can remember right now
if you need any help, I'm always available,
and I'm looking forward to seeing your work
Best Regards,
Omar.

Thank you very much for your long and exhaustive answer.
I did see a camera workaround in the cm system.
Has anyone tried porting stock camera to cm? (Is it the actual camera hal responsible for qualiy or Sony proprietary rendering sw on album(are pics better/worse in fact when viewed on PC or from the phone's album? We did that on the lg with great results..
What about device blobs for the kernel are they closed source or do we have support from Sony?
Thanks again for all the info
Cheers

XZ1 Nougat

Hello dear developers,
I think some of you know, that the XZ3 is in the Android preview program for Nougat. https://developer.sony.com/develop/smartphones-and-tablets/android-n-developer-preview/
As far as I can see in wikipedia the hardware of Z1 and Z3 are very similar. The Z3 is the last of the Z series with very similar hardware.
Because there are so many Xperia devices, the community of developers is very thinned out. There is not even one MarshMallow release which is running without problems until now and Google is already short before releasing Nougat.
Sadlly I am no developer on my own. I already fail at creating the necessary Linux environment. But there are many great developers and skilled people here on the forum. Wouldn't it be a great idea that you bundle your skills, skip the MM release and create the maybe last ROM update for our beloved XZ1? A release of stock based N.
It is just an idea, but it would be great if some of you would capture the idea :fingers-crossed:

wrong forum, xperia z1 won't have a stable MM ROM........................

->--- said:
Hello dear developers,
I think some of you know, that the XZ3 is in the Android preview program for Nougat. https://developer.sony.com/develop/smartphones-and-tablets/android-n-developer-preview/
As far as I can see in wikipedia the hardware of Z1 and Z3 are very similar. The Z3 is the last of the Z series with very similar hardware.
Because there are so many Xperia devices, the community of developers is very thinned out. There is not even one MarshMallow release which is running without problems until now and Google is already short before releasing Nougat.
Sadlly I am no developer on my own. I already fail at creating the necessary Linux environment. But there are many great developers and skilled people here on the forum. Wouldn't it be a great idea that you bundle your skills, jump over the MM release and create the maybe last ROM update for our beloved XZ1? A release of N.
It is just an idea, but it would be great if some of you would capture the idea :fingers-crossed:
Click to expand...
Click to collapse
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...

optimumpro said:
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
Click to expand...
Click to collapse
I've wondered for a long time now: you talk crap about Sony's software, complain about their blobs being 'crap', and claim Sony isn't friendly to OSS, yet you continue to develop and deploy custom ROMs for the Z1. If it's such a hurdle to develop, why not move to a developer friendly platform/device like the Nexus 6P? I appreciate your work for the Z1, but I think you're beating the dead horse at this point.

kentexcitebot said:
I've wondered for a long time now: you talk crap about Sony's software, complain about their blobs being 'crap', and claim Sony isn't friendly to OSS, yet you continue to develop and deploy custom ROMs for the Z1. If it's such a hurdle to develop, why not move to a developer friendly platform/device like the Nexus 6P? I appreciate your work, but I think you're beating the dead horse at this point.
Click to expand...
Click to collapse
LP 5.1 is pretty good. It is better than stock. Today I replaced the rear camera module (the old one stopped focusing) and camera is superb. No bugs in LP.
I may move to Nexus, but the phone I buy has to be metal or glass, plus Z1 has enough life ahead of it. I don't care about M or N. From my point of view, Google changes SDK, so that prior features won't work, and in exchange gives us a few different icons and slightly different interface.
Security updates are coming and lp will be supported for a long while. Normal users don't care about versions either. They want a stable device and they get it in LP...

optimumpro said:
I may move to Nexus, but the phone I buy has to be metal or glass, plus Z1 has enough life ahead of it.
Click to expand...
Click to collapse
The OnePlus 3 is the next best developer-friendly platform after the Nexus devices. Warranty doesn't go bad if you root or unlock bootloader. It even got CM 13 before launch! It also happens to have a metal back, 16MP shooter with OIS, and everybody's favorite 'Dark Mode'. I don't mean to advertise, but for $399, I'd say that's a great bargain. Don't get me wrong, the Z1 still works beautifully when all is OK, but it's really starting to show it's age: your device's rear camera module stopped focusing until you replaced it, several user's battery in the Z1 (not just on XDA) is going bad, and my Z1's touch digitizer has issues on tap (probably from abuse, but people reported self-cracking screens with their touchscreens completely broken). Not too many people want to go through the trouble of sending it in (to China?!) or fixing it themselves.
I don't care about M or N. From my point of view, Google changes SDK, so that prior features won't work, and in exchange gives us a few different icons and slightly different interface.
...
Normal users don't care about versions either.
Click to expand...
Click to collapse
Um, what? According to many tech sources, that's the highlight issue with Android: fragmentation. If you wanted to know Android's biggest problem, this is it. In fact, people (including some casuals) blast Android because of this. Maybe you don't care about Android versions, but if you stick with LP or an older platform, you're contributing to the problem.
Security updates are coming and lp will be supported for a long while. They want a stable device and they get it in LP...
Click to expand...
Click to collapse
As you can probably tell, I've already switched to a different device: a OnePlus 3. Oxygen OS 3.1.3 (6.0.1 Marshmallow), from experience, is quite stable and is developed by the team behind Paranoid Android. Sure, LP's code is more stable because it's been out longer and has more revisions, but it really depends of how you interpret the term (because I've experienced no crashes or FCs so far on MM). I'm fine if you continue holding the torch for Z1's AOSP/CM ROM community and keep LP more secure/stable for them, but I find it a bit redundant as most users have already moved away from this device and transitioned to MM (and even N DP4).

kentexcitebot said:
The OnePlus 3 is the next best developer-friendly platform after the Nexus devices. Warranty doesn't go bad if you root or unlock bootloader. It even got CM 13 before launch! It also happens to have a metal back, 16MP shooter with OIS, and everybody's favorite 'Dark Mode'. I don't mean to advertise, but for $399, I'd say that's a great bargain. Don't get me wrong, the Z1 still works beautifully when all is OK, but it's really starting to show it's age: your device's rear camera module stopped focusing until you replaced it, several user's battery in the Z1 (not just on XDA) is going bad, and my Z1's touch digitizer has issues on tap (probably from abuse, but people reported self-cracking screens with their touchscreens completely broken). Not too many people want to go through the trouble of sending it in (to China?!) or fixing it themselves.
Um, what? According to many tech sources, that's the highlight issue with Android: fragmentation. If you wanted to know Android's biggest problem, this is it. In fact, people (including some casuals) blast Android because of this. Maybe you don't care about Android versions, but if you stick with LP or an older platform, you're contributing to the problem.
As you can probably tell, I've already switched to a different device: a OnePlus 3. Oxygen OS 3.1.3 (6.0.1 Marshmallow), from experience, is quite stable and is developed by the team behind Paranoid Android. Sure, LP's code is more stable because it's been out longer and has more revisions, but it really depends of how you interpret the term (because I've experienced no crashes or FCs so far on MM). I'm fine if you continue holding the torch for Z1's AOSP/CM ROM community and keep LP more secure/stable for them, but I find it a bit redundant as most users have already moved away from this device and transitioned to MM (and even N DP4).
Click to expand...
Click to collapse
Fragmentation has nothing to do with Android versions. Neither Android version has done anything to reduce fragmentation as compared to the previous one. It is the fact that there are hundreds of different devices with varieties of hardware. However, different hardware does not create fragmentation. Unlike Apple, Windows and Linux work on many devices. The problem for Android is that manufacturers don't want to provide hardware addresses (to make open source drivers) or blobs to work with hardware. The question is: why manufacturers provide the necessary info for Windows and Linux, but refuse the same with Android and mobile devices. And I am yet to hear an answer to this...

optimumpro said:
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
Click to expand...
Click to collapse
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.

olokos said:
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
Click to expand...
Click to collapse
Would you have any test build that could be tried out? I'd love to test it out...

olokos said:
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
Click to expand...
Click to collapse
Doing "a lot of work" and having stable releases, which they have never had on any android version, are 2 different things. Aren't they? Camera aside, how about random reboots, blank screen issues, failure to wake up, battery drain, slow charging, overheating: what more do you need? And by the way, you think camera focus is the only issue? I bet a lot of users would disagree.
We are almost in August. Last year this time LP 5.1.1 was pretty stable. No chance for MM and N is already here...
Edit: My opinions about MM and Sony shouldn't be taken as criticism of Sony open source developers (who work their butts off) or any other devs (myself included) who contribute to the code, but rather Sony Corporation itself. Sony doesn't want you to have custom roms.
If I am to blame community developers, then it would be for abandoning stable releases like LP 5.1.1 in favor of undercooked new ones like MM. That's double stupidity, because in addition to starting from ZERO, they are following (instead of leading) teenage users who would rather have a slightly changed "cool" user interface, as opposed to a rock solid stable release...

optimumpro said:
Doing "a lot of work" and having stable releases, which they have never had on any android version, are 2 different things. Aren't they? Camera aside, how about random reboots, blank screen issues, failure to wake up, battery drain, slow charging, overheating: what more do you need? And by the way, you think camera focus is the only issue? I bet a lot of users would disagree.
We are almost in August. Last year this time LP 5.1.1 was pretty stable. No chance for MM and N is already here...
Edit: My opinions about MM and Sony shouldn't be taken as criticism of Sony open source developers (who work their butts off) or any other devs (myself included) who contribute to the code, but rather Sony Corporation itself. Sony doesn't want you to have custom roms.
If I am to blame community developers, then it would be for abandoning stable releases like LP 5.1.1 in favor of undercooked new ones like MM. That's double stupidity, because in addition to starting from ZERO, they are following (instead of leading) teenage users who would rather have a slightly changed "cool" user interface, as opposed to a rock solid stable release...
Click to expand...
Click to collapse
but, like you said, lollipop are stable, why still develop for it?

brickhayabusa said:
but, like you said, lollipop are stable, why still develop for it?
Click to expand...
Click to collapse
Because stable and maintained are different things. Stable becomes outdated if not further developed. For example, all abandoned LPs are now outdated and shouldn't be used...

optimumpro said:
Because stable and maintained are different things. Stable becomes outdated if not further developed. For example, all abandoned LPs are now outdated and shouldn't be used...
Click to expand...
Click to collapse
Then why xperia M is really awesome, they have a official cm13 nightly still updte every day, n now they're will building for awaken the Nougat, already tested n booted with Alpha release now,
it all by they devs is superior or factor xperia M devices are supported?
Will realy glad if Honami can like them..

Snp Mania2 said:
Then why xperia M is really awesome, they have a official cm13 nightly still updte every day, n now they're will building for awaken the Nougat, already tested n booted with Alpha release now,
it all by they devs is superior or factor xperia M devices are supported?
Will realy glad if Honami can like them..
Click to expand...
Click to collapse
Because they are probably using 3.4 kernel together with older camera blobs. In case of honami, they have decided to move to 3.10 kernel and the newer good blobs are drm protected. And they are waiting for Sony aosp to improve 3.10 blobs, which should happen in the next 50-100 years. Because of this, CM is not working on honami. That's why there is not even one nightly MM for Z1. And since other "big" guys can only cut and paste from CM, there is nothing for Z1.

optimumpro said:
Because they are probably using 3.4 kernel together with older camera blobs. In case of honami, they have decided to move to 3.10 kernel and the newer good blobs are drm protected. And they are waiting for Sony aosp to improve 3.10 blobs, which should happen in the next 50-100 years. Because of this, CM is not working on honami. That's why there is not even one nightly MM for Z1. And since other "big" guys can only cut and paste from CM, there is nothing for Z1.
Click to expand...
Click to collapse
Sorry for this one sir,
This screenshoot i take from xda fecebook via someone of member z1 indonesia FB group, but i dont OP like u so i not understanding it, pls help for read that post at this link...
http://developer.sonymobile.com/build-aosp-nougat-7-0/
EDIT: looks like z1 never to be the Nougat :crying:
from here: http://www.xda-developers.com/sony-...g-aosp-7-0-nougat-for-its-xperia-smartphones/

looki looki!!!!
http://uploaded.net/f/ikvebh

santeria27 said:
looki looki!!!!
http://uploaded.net/f/ikvebh
Click to expand...
Click to collapse
U have try that rom?

No tested!!!
Sent from my Xperia Z1 using XDA-Developers mobile app

santeria27 said:
No tested!!!
Click to expand...
Click to collapse
Haha . Even i cant download that .

Spent 2 hours for downloading this.
Mirror: https://drive.google.com/open?id=0B5NqkvihftQXSDI5Vl9Na2h6ak0

Android "N" as in "No nougat for the Z3 line"...

http://blogs.sonymobile.com/2016/08...ndroid-7-0-nougat/?k=1471977631#comment-65567
I'm disappointed. I really hoped that it would get it with the Xperia Z3 N Preview program. What was the point of that ??

DannyBiker said:
http://blogs.sonymobile.com/2016/08...ndroid-7-0-nougat/?k=1471977631#comment-65567
I'm disappointed. I really hoped that it would get it with the Xperia Z3 N Preview program. What was the point of that ??
Click to expand...
Click to collapse
I am both surprised and disappointed. The Z3C is a great device, and the failure by Sony to update it to Nougat is anticlimactic, to say the least. I was planning to buy the tablet; I guess I'll have to look elsewhere now

It's actually a bit more complicated than that. I've read from a few sources that actually Google is to blame for removing msm8974 code from AOSP and so Sony has no option but to deny an official Nougat update to these devices. As for the fact that the z3 phone got some N preview builds, well, they stopped at build 3, it didn't recieve builds 4 and 5. It is assumed that it's cause it's actually in build 4 that Google removed code for our SoC. We'll see how things turn out.
EDIT: It turns out it might even be on Qualcomm as it is the chipset manufacturer to decide whether it will support and make drivers for their chipset that work with the new OS version. Although I doubt such decisions are made without consulting Google.

Tipkaros said:
It's actually a bit more complicated than that. I've read from a few sources that actually Google is to blame for removing msm8974 code from AOSP and so Sony has no option but to deny an official Nougat update to these devices. As for the fact that the z3 phone got some N preview builds, well, they stopped at build 3, it didn't recieve builds 4 and 5. It is assumed that it's cause it's actually in build 4 that Google removed code for our SoC. We'll see how things turn out.
EDIT: It turns out it might even be on Qualcomm as it is the chipset manufacturer to decide whether it will support and make drivers for their chipset that work with the new OS version. Although I doubt such decisions are made without consulting Google.
Click to expand...
Click to collapse
Interesting. I had no idea it went that deep to google and Qualcomm even.
Oh well it's a shame as as the z3 compact is a great device. The best tablet I've ever owned for sure. And I've had a few. Would have been nice to have true android multitasking windows.

That's really all I wanted for the Z3T : native multi-window.
If only they were developers working on the Z3 line... :/

I realize our device is old, but what we need is a little push in our dev scene. I remember for the Xperia Z Ultra some users got together and paid a dev to develop a kernel. Maybe something similar has been done here?
Either way, we aren't that many here which means there are even less devs. Could we manage to scrape together an amount any good dev would consider to build us a working, updated build of Nougat or Cyanogen?

But ...
developer.sonymobile.com/build-aosp-nougat-7-0
or don't work for this tablet?

I'm fairly sure that if there was more interest for the Z3 Tablet, we'd get decent Nougat custom roms in the end. But the devs are just not there. We could always make a bounty but these things don't work out so well most of the time...

N
AOSP N works on scorpion sgp621.
Works fine without camera (not works yet).

koron393 said:
AOSP N works on scorpion sgp621.
Works fine without camera (not works yet).
Click to expand...
Click to collapse
Where is the download link?
Skickat från min MI 5

Tyerlo said:
Where is the download link?
Skickat från min MI 5
Click to expand...
Click to collapse
Built it yourselves.

there are builds from fxp-blog (https://www.androidfilehost.com/?w=files&flid=109243) but i didn't test them yet. i don't need the camera on my tablet.

M!tch said:
there are builds from fxp-blog (https://www.androidfilehost.com/?w=files&flid=109243) but i didn't test them yet. i don't need the camera on my tablet.
Click to expand...
Click to collapse
I suppose scorpion_windy is for our devices? And will it work with the sgp 611?

sgp611 is the wifi-only model and codenamed scorpion_windy.
i've got the lte version -> scorpion.

new builds are up at https://www.androidfilehost.com/?w=files&flid=109243
edit: after some testings this is not ready as a daily driver because on reboot i get sometimes a bootloop and without fastboot and reflash it often won`t boot.
hopefully cm14 will come along quicker with this as base.

I didn't think there was an unlock for the 621?

AICP N
AICP 12 (Nougat) build.
Sorry no zip file for now.

what about major bugs/nonfunctional basic-hardware?

koron393 said:
AICP 12 (Nougat) build.
Sorry no zip file for now.
Click to expand...
Click to collapse
I've AICP on all my devices except the scorpion_windy so I very much look forward to trying out your first release

dudes at least we have the option to choose between 3 OS'S.I tested both KK and LP (except MM) and both run GREAT.
Στάλθηκε από το SGP611 μου χρησιμοποιώντας Tapatalk

Carbon Rom coming soon for Taimen?

https://github.com/CarbonROM/android_device_google_taimen/tree/cr-6.1
Looks like some work on the carbon roms github for taimen!?

Oh please let there be roms. Stock is so boring

Not soon enough from my standpoint...

This is not meant towards the amazing developers here, I am very grateful for thier hard work. But is there an issue with this particular phone ?
Im in shock after 2 plus months of this phone being out there is not one single ROM out yet. A next generation Nexus type phone should be chock-full of ROMs and kernels by now. I'm really at a loss for words.
I've owned 6 of the 8 Nexus / Pixel phones over the years, starting with the Nexus-One. And typically within one month there's several good ROM's out already.

Zorachus said:
I'm still in shock after 2 plus months of this phone being out there is not one single ROM out yet. A next generation Nexus type phone should be chock-full of ROMs and kernels by now. I'm really at a loss for words.
I've owned 6 of the 8 Nexus / Pixel phones over the years, starting with the Nexus-One. And typically within one month there's several good ROM's out already.
Click to expand...
Click to collapse
We've only just got stable twrp ...calm down
The pixels are more complicated. Don't like it. Get a OnePlus

Be nice to see some roms. Thanks.

Isn't Project Treble supposed to help make ROM'ing faster and easier ?
http://www.androidpolice.com/2017/11/25/googles-project-treble-start-custom-rom-revolution/

Zorachus said:
Isn't Project Treble supposed to help make ROM'ing faster and easier ?
http://www.androidpolice.com/2017/11/25/googles-project-treble-start-custom-rom-revolution/
Click to expand...
Click to collapse
ys but that doesn't change the fact that Oreo changed A LOT about the system that the devs have to go through...
It's not because of the phone that we don't have ROMs, it's because Oreoooooooooooo

Roms are going to take time because of the new Android security add-ons. Just look how different encryption is. The last I heard about twrp is that it may not work after each update

Ericarthurc said:
https://github.com/CarbonROM/android_device_google_taimen/tree/cr-6.1
Looks like some work on the carbon roms github for taimen!?
Click to expand...
Click to collapse
To actually answer your question, yes it is coming. Dev's are hard at work on it and I know some people who have been working to build it. Long story short, Oreo sucks nuts for developers. The system is vastly different from years past and many things have to be rewritten from scratch.
Be patient people. Rom's are on the way. These guys do this in their free time for fun.

Alright so I guess I'll update people. Yeah Carbon is working on it, one of theirs devs and I have been the only two I know of working on it besides lineage, so I think we're all still in the process of getting it stable before adding stuff.
We had to fight through a lot of hurdles to get to where we're at, I haven't really seen many rom teams trying to bring up the taimen because of odd device tree, the a/b requirement, and the oddness of the proprietary blobs. But yeah I'd say you're at least a good 3 weeks away from any team dropping any roms.
I have no idea when carbon will be out BTW.
I don't even rom, I just need a rom for the other dev stuff I'm doing lol, so hopefully some fellow devs will get involved.

Thanks for the update. So it seems true that Oreo is much more difficult to develop for ? As well as the Pixel phone's having the a/b partions.
Why didn't Google just leave the Pixel phones like the Nexus and OnePlus phones ? I guess for security reasons ?
And how bout Project Treble ? Does that help down the road ? Once a AOSP ROM is out does Treble make it easier or faster to update it or add stuff quicker?

I'm working on slim ?

gmillz said:
I'm working on slim ?
Click to expand...
Click to collapse
Hahaha nice I just fixed a huge issue I was having with lte. I'm trying to convince beans to get pure stable, I already have a base going.
You using the payload.bin method?

Surge1223 said:
Hahaha nice I just fixed a huge issue I was having with lte. I'm trying to convince beans to get pure stable, I already have a base going.
You using the payload.bin method?
Click to expand...
Click to collapse
Did Beans retire?

I saw ROM on the main page of the google pixel 2 xl and got so excited!!!!

Surge1223 said:
Alright so I guess I'll update people. Yeah Carbon is working on it, one of theirs devs and I have been the only two I know of working on it besides lineage, so I think we're all still in the process of getting it stable before adding stuff.
We had to fight through a lot of hurdles to get to where we're at, I haven't really seen many rom teams trying to bring up the taimen because of odd device tree, the a/b requirement, and the oddness of the proprietary blobs. But yeah I'd say you're at least a good 3 weeks away from any team dropping any roms.
I have no idea when carbon will be out BTW.
I don't even rom, I just need a rom for the other dev stuff I'm doing lol, so hopefully some fellow devs will get involved.
Click to expand...
Click to collapse
Any plans to publish your work? I desperately want to do some low-level modem diags.

So the Pixel XL oreo rom started showing up, so we hope to see ours soon too

LLStarks said:
Any plans to publish your work? I desperately want to do some low-level modem diags.
Click to expand...
Click to collapse
Most of my stuff is on git, subs Gerrit or pure git. So it's already out there but as far as rom wise, im part of team pure so it would be in pure nexus. I think the base is solid right now, I just started helping add mods yesterday, specifically OMS related like fonts etc.
As far as modem debugging I'm assuming you're saying that since I'm on a userdebug build, yeah I don't know if I'll post that up or not but it's pretty simple to build.
Just a note for folks out there building, lineage blobs aren't complete, and don't make otapackage, make dist because you need those images signed brillo payload style
---------- Post added at 09:43 PM ---------- Previous post was at 09:43 PM ----------
lucky_strike33 said:
Did Beans retire?
Click to expand...
Click to collapse
Not as of yet.

Surge1223 said:
Most of my stuff is on git, subs Gerrit or pure git. So it's already out there but as far as rom wise, im part of team pure so it would be in pure nexus. I think the base is solid right now, I just started helping add mods yesterday, specifically OMS related like fonts etc.
As far as modem debugging I'm assuming you're saying that since I'm on a userdebug build, yeah I don't know if I'll post that up or not but it's pretty simple to build.
Just a note for folks out there building, lineage blobs aren't complete, and don't make otapackage, make dist because you need those images signed brillo payload style
---------- Post added at 09:43 PM ---------- Previous post was at 09:43 PM ----------
Not as of yet.
Click to expand...
Click to collapse
Pure Nexus OMS for Taimen?!?!
My happy cells are in overload!
Used to run PN when I had the Bullhead
God speed to the PN team!