Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.
m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse
timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Offer a bounty if you're that impatient.
sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.
bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol
m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.
and its outtt
m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then
Related
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
EDIT:
Id like to keep this a conversation between people who want this and people who know. Please dont add your 2cnts in to say the same things we have all heard (we need source, cant do it, no reverse engineering, blah blah)
If you are a dev and can give some REAL PROPER insight, we would love to hear it. even if its to tell us to stuff it LOL.
rawdikrik said:
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
Click to expand...
Click to collapse
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
k2buckley said:
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
Click to expand...
Click to collapse
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Edit: complete speculation, if it is in fact true i will modify post to reflect my all knowing powers
NewZJ said:
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Click to expand...
Click to collapse
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
rawdikrik said:
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
Click to expand...
Click to collapse
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
pinky059 said:
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
Click to expand...
Click to collapse
So in other words the reasons that they arent bothering is because they dont want to invest the time when it could become obsolete before it is even released?
mutant13 said:
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I dont see that happening any time soon.
Not only that, but i think i remember NET working on one before any source came out for 2.2 and 2.1, especially to fix the FPS cap.
I think that he didnt want to touch it because it is beta and can change between now and an official 2.3 release, like most devs have stated.
rawdikrik said:
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
Click to expand...
Click to collapse
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
k2buckley said:
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
Click to expand...
Click to collapse
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
rawdikrik said:
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
Click to expand...
Click to collapse
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
k2buckley said:
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
Click to expand...
Click to collapse
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
I heard that too. That wont be til June/July and then they have another 60days of waiting time they usually take to release source.
and that is IF They do the upgrade, since usually they only want a single upgrade in the life cycle of a product. They will most likely REALLY think about it, to not risk stealing sales from the newer phones coming out over the summer.
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
Correct. I predict the 3D to drop within 30-60 days from now though. Then shortly after that, the OTA will probably roll out. As rawdikrik said, source will probably come a month or two after the OTA. The good thing though, is that if/when an OTA is released, it will have a working kernel in it. So even without source being released, a working kernel will be in circulation at that point, which will most likely resolve the brightness issue.
Evo 3D is supposedly hitting June so I'm going to say July just to give it some breathing room. If OTA hits around August maybe September, then its another 30-45 days to release source. So were talking around September-October ish for complete source. This is all speculation but sprint/HTC operate that way. My guess is september for a fully working kernel for GB based on the source code. Stupid marketing scheme to get us to buy the evo 3D.
Sent from my PC36100 using XDA Premium App
I'm so going to buy the EVO 3d
not sure how i feel about the 3d gimmick...
Can we keep this on topic though? THanks guys... Im just waiting to hear something from the big dogs.
Keep in mind it's entirely possible that we will see another leaked kernal long before the OTA is out, this one fully functional. This is especially true if(as many of you seem to suspect) this "leak" was actually no leak at all but an intentional way to let the Chefs and Power Users test their new ROM for them and get feedback on it.
Not sure if you (the Op) have ever tried programming... But (in perspective of the difficulty), basically this would be like me writing a "Hello World" app in Java or C++, and it having an extra space in between the words that bothered you. You would have to cipher through hundreds of lines of code in a hexidecimal editor trying to find the "call" to the display API, and then find which variable or constant it was using for the text output, and change it.
Then you would have to re-compile, and hope it worked without breaking anything else already in place. If you broke something, it's INCREDIBLY hard to debug without real source code.
Hi all,
I am Samsung Galaxy Nexus owner and I would like to run Android 4.4 KitKat on my Galaxy Nexus. But I am not a developer. From my understanding if we want a GOOD 4.4 build we need to port a 3.4 kernel and fix a lot a bug/small issues. This is an hard work and we need some good developer(s) on it.
14,000+ guys signed the petition. This is not a very effective strategy to get what we want. We should pay someone to work on our device: hard work requires motivation and a lot of time.
We should start a fund-raising campaign in order to pay a skilled developer to work full time.
10$ * 10,000 = 100,000$
20$ * 5000 = 100,000$
If we raise even a fraction of this amount... we can afford some man/hours.
What do you think? Is the porting feasible if we pay the right person(s)? Are you in?
(I am not a developer AND I will not start a fund-raising campaign.)
Let me get this straight. You want to start a bounty on getting 3.4 kernel and 4.4 kitkat on the gnex, but you don't want to personally be the one to start it? That's lazy man, and sounds to me like you want 4.4 at other people's expense. If you want it so bad then you should be the one to start it.
R2DeeTard said:
That's lazy man, and sounds to me like you want 4.4 at other people's expense. If you want it so bad then you should be the one to start it.
Click to expand...
Click to collapse
I think you misunderstand my statement. I am no one in this forum: it is unsafe if people start to give money to to a possible fund raising campaign that i will start (IMAO). I will be happy to contribute ($$) if anyone that can be trusted start it. The right person should be e.g. a long-life xda user, maybe a well-known GNex rom builder. I will be happy (discuss all the details, etc) to help this person as much as I can.
New update on OMAP-Tuna platform from 3.4 thread, guess we may have a 3.4 / an updated kernel for 4.4
Something like this was done for the HTC One (one of the versions) to motivate the devs to find a way to unlock the bootloader... They did it in record time. Hope this gains momentum as did the HTC One case. Yeah, I know, this is WAY more difficult than that, but it can be done so I hope to see the 3.4 kernel soon
Let's start a kickstarter campaign! Would need to source devs who can and are willing to fix the gpu glitches and other bugs....
R2DeeTard said:
Let me get this straight. You want to start a bounty on getting 3.4 kernel and 4.4 kitkat on the gnex, but you don't want to personally be the one to start it? That's lazy man, and sounds to me like you want 4.4 at other people's expense. If you want it so bad then you should be the one to start it.
Click to expand...
Click to collapse
Some folks just like it like that, he could kill a cow, butcher it make a ground beef patty, make his own buns, grow his own tomatoes, make his own cheese.... But i bet he rather stop by Burger King.
WHATCHOO TALKING BOUT WILLIS?
for kernel 4.4
look at this kernel
http://forum.xda-developers.com/showthread.php?t=2423338
Uneducated here. What benefit does a 3.4 kernel serve for us? Are there new drivers for the OMAP that's needed for 4.4, or is it those 'man and mountain' situations?
alpha-niner64 said:
Uneducated here. What benefit does a 3.4 kernel serve for us? Are there new drivers for the OMAP that's needed for 4.4, or is it those 'man and mountain' situations?
Click to expand...
Click to collapse
I actually don't think it's gonna benefit our device much. Heck, all 4.3 kernels still work on 4.4 provided they don't come with their own ramdisk. Even cm11 kernel source is almost unchanged from cm10.2.
Graphical glitches? All solved by now?
Random reboots? Solved in cm11.
Sent from my Galaxy Nexus using Tapatalk
It would be useful...
akash3656 said:
I actually don't think it's gonna benefit our device much. Heck, all 4.3 kernels still work on 4.4 provided they don't come with their own ramdisk. Even cm11 kernel source is almost unchanged from cm10.2.
It would be useful. There are some major improvements in memory, filesystem, and block-layer (read: SSD TRIM) stuff in post-3.0 kernels. Your device will be faster and use less memory.
I would argue though, that if someone's gong to tear into the 3.0.x-OMAP code and try to engineer a 3.4 kernel to work on the Galaxy Nexus hardware, it probably makes more sense to go 'all the way' and port those changes up into 3.10 or 3.12 (if 3.12 looks like it will be a 'longterm' release). There's no reason that Android won't run on a newer kernel. Android-ia (Intel's Android-on-x86 project) has Android working against newer kernels than Google does.
Click to expand...
Click to collapse
mangeek said:
akash3656 said:
I actually don't think it's gonna benefit our device much. Heck, all 4.3 kernels still work on 4.4 provided they don't come with their own ramdisk. Even cm11 kernel source is almost unchanged from cm10.2.
It would be useful. There are some major improvements in memory, filesystem, and block-layer (read: SSD TRIM) stuff in post-3.0 kernels. Your device will be faster and use less memory.
I would argue though, that if someone's gong to tear into the 3.0.x-OMAP code and try to engineer a 3.4 kernel to work on the Galaxy Nexus hardware, it probably makes more sense to go 'all the way' and port those changes up into 3.10 or 3.12 (if 3.12 looks like it will be a 'longterm' release). There's no reason that Android won't run on a newer kernel. Android-ia (Intel's Android-on-x86 project) has Android working against newer kernels than Google does.
Click to expand...
Click to collapse
I don't know but some or most of the stuff you mention have been backported by current (or previous) kernel developers.
Well if anyone wants to do any >3.0 kernel, its up to them to see which newer version is the most viable version to jump to.
Having that said, I have no experience in making kernels or following the changes in Linux kernel religiously.
Click to expand...
Click to collapse
Since the paranoid android team sources their code from aosp, which got the lollipop push on the 3rd of November, when can we expect a final 4.x and work on lollipop to begin?
Furthermore, when's the earliest we can expect a beta push? (Note 2 user here)
Expect? Never.
We still don't have everything we need for fully supported aosp builds on nexus devices. It would be great if people would just be patient.
#stayparanoid
Pirateghost said:
Expect? Never.
We still don't have everything we need for fully supported aosp builds on nexus devices. It would be great if people would just be patient.
#stayparanoid
Click to expand...
Click to collapse
Well, CM12 it is then. Shame though. You guys have the best UI out there. Way to go Arz Bhatia. :good:
BigBallsac said:
Well, CM12 it is then. Shame though. You guys have the best UI out there. Way to go Arz Bhatia. :good:
Click to expand...
Click to collapse
You asked for an EtA, and I told you to never "expect" it. We don't even support your device... So how can we give anyone an EtA when we have no idea how long developing something will take?
I really wish people understood the process here and the fact that asking for etas is frowned upon and discouraged
#stayparanoid
i swear some people are raised by f$cking wolves.....
no manners and expect everything for free.
So will the next update to PA be based on 4.4.4 or 5.0?
mattgoldey said:
So will the next update to PA be based on 4.4.4 or 5.0?
Click to expand...
Click to collapse
Well, considering all work on 4.4.4 has been dropped, you can expect to NOT get a 4.4.4 build again
#stayparanoid
Any idea on the timeframe of the first 5.0 based release? I've got the 5.0 release on my N7, but it's so slow. I'm excited to give it a try on my OPO.
We have never given etas because we don't know....
#stayparanoid
Pirateghost said:
We have never given etas because we don't know....
#stayparanoid
Click to expand...
Click to collapse
Hi,
I know I'm annoying, and I'm sorry for that.
But we need an ETA. I understand you can't provide such. But you can provide approximate times where it will be done, for example:
"We're 50% sure it will be done in <month>, and we're absolutely sure it will be a rather stable beta by <month>. But don't think it will last so long, it will be probably available much, much earlier, those are just the worst scenarios."
Thanks for what you do for us,
Michael
P.S.: Nexus 4 owner here.
P.P.S.: Can you tell be if I have to wipe data to update to Lollipop? Because I would be able to test such things as CM12 meanwhile.
ArchieTor said:
Hi,
I know I'm annoying, and I'm sorry for that.
But we need an ETA. I understand you can't provide such. But you can provide approximate times where it will be done, for example:
"We're 50% sure it will be done in <month>, and we're absolutely sure it will be a rather stable beta by <month>. But don't think it will last so long, it will be probably available much, much earlier, those are just the worst scenarios."
Thanks for what you do for us,
Michael
Click to expand...
Click to collapse
No. We cannot provide any approximations at all. This shouldn't even be questionable.
A. We don't have time we can set aside for development. We fit stuff in when we can in between real life functions and responsibilities.
B. Everyone has a part of the development process. We all have to coordinate these efforts in order to produce something.
C. This is not our job. We try to do this for fun. A hobby. Would it be appropriate to ask when you will have something for me to play with from your hobby? Take RC cars for example. Let's say you like to build RC cars and some cool new gear was just released. Should I come to you and ask you, nay, tell you that you need to give me a date that I will be able to play with your new toy?
So, no, we cannot tell you a date or an approximate date for anything. It lands when it lands.
#stayparanoid
ArchieTor said:
Hi,
I know I'm annoying, and I'm sorry for that.
But we need an ETA. I understand you can't provide such. But you can provide approximate times where it will be done, for example:
"We're 50% sure it will be done in <month>, and we're absolutely sure it will be a rather stable beta by <month>. But don't think it will last so long, it will be probably available much, much earlier, those are just the worst scenarios."
Thanks for what you do for us,
Michael
P.S. Nexus 4 owner here.
Click to expand...
Click to collapse
ETA for when you stop asking for ETA? Sorry to be annoying, but I need an ETA.
Thanks.
#stayETAparanoid
ArchieTor said:
Hi,
I know I'm annoying, and I'm sorry for that.
But we need an ETA. I understand you can't provide such. But you can provide approximate times where it will be done, for example:
"We're 50% sure it will be done in <month>, and we're absolutely sure it will be a rather stable beta by <month>. But don't think it will last so long, it will be probably available much, much earlier, those are just the worst scenarios."
Thanks for what you do for us,
Michael
P.S.: Nexus 4 owner here.
P.P.S.: Can you tell be if I have to wipe data to update to Lollipop? Because I would be able to test such things as CM12 meanwhile.
Click to expand...
Click to collapse
franciscofranco said:
ETA for when you stop asking for ETA? Sorry to be annoying, but I need an ETA.
Thanks.
#stayETAparanoid
Click to expand...
Click to collapse
ArchieTor, can I get an ETA on when you will respond to franciscofranco? I need to know this ASAP.
Thx
Sent from my A0001 using XDA Free mobile app
franciscofranco said:
ETA for when you stop asking for ETA? Sorry to be annoying, but I need an ETA.
Thanks.
#stayETAparanoid
Click to expand...
Click to collapse
The past month on the G+ Community in a nutshell.
@NBruderman we are expecting 5.0 for S4 i9500 very soon. Have you made any progress so far, can't wait! You make the most stable builds till date.
ArchieTor said:
Hi,
I know I'm annoying, and I'm sorry for that.
But we need an ETA. I understand you can't provide such. But you can provide approximate times where it will be done, for example:
"We're 50% sure it will be done in <month>, and we're absolutely sure it will be a rather stable beta by <month>. But don't think it will last so long, it will be probably available much, much earlier, those are just the worst scenarios."
Thanks for what you do for us,
Michael
P.S.: Nexus 4 owner here.
P.P.S.: Can you tell be if I have to wipe data to update to Lollipop? Because I would be able to test such things as CM12 meanwhile.
Click to expand...
Click to collapse
The reason there's no ETAs given on things like this is because it's all superficial. For all you know, they found some drawbacks and you'll find a slightly disgruntled community that was expecting it then and didn't get it. It's best to just wait it off.
pa colors
Wil pa colors be able to use in 5.0?
I want to recolor my status bar (clock, battery etc.) but cannot in 4.4.4 version, would be so happy if we get back this option in lollipop???
Wow, as I sometimes read my posts, I'm gettin' even more motivated to prevent myself from getting in any contact with alcohol for a lifetime (Disclaimer: Never had it so far.)
Last time I had Internet access (I wasn't having it Dec 2—15), I wanted to write that I'm sorry, and I of course appreciate your work, and that I understand it's not your job, just hobby (I know there are people who think that all of the open-source software is created by companies employing programists for a cash and having profit from it in not-well-precised sources, and I ain't one of them), I wanted to highlight it with "Thank you for what you do for us", so you wouldn't think I expect an ETA in a way like a money-paying consumer would.
I was thinking about your response once again and now I understand you that you don't want to give an ETA, as it might become somehow disinformation, and some people involved would take it as inappropriate, as you can't just say for the whole team of volunteers how much work you're going to do during a certain period of time. When I tried to compare to compare the situation with my case (I'm creating simple Python programs (still just learning (the best way of learning to code is actually trying to create something new with just the very basic knowledge)) with just ~160 clones every month), in which if somebody asked me for an ETA, I might give one, but it would be inaccurate, and usually also be disinformation, and if I'd work with other people also considering it as a hobby, I wouldn't be sure whether to try to even very inaccurately estimate the time until next release or some fix.
So there, I know I'm being annoying, I'm sorry for that and I'm gonna try to stop it.
Cheers,
Michael
P.S.: Maybe you can't actually give a date, but can you provide a link to, for example, a stream of commit descriptions best to follow if I'd want to try to estimate when it'll be ready?
Follow +paranoid android on g+. Watch https://gerrit.paranoidandroid.co
#stayparanoid
But we need an ETA. I understand you can't provide such. But you can provide approximate times where it will be done, for example:
Click to expand...
Click to collapse
One or two years. OK?
Would Cyanogen Mod be interested in developing for this phone now that we have unlocked bootloader? Given the choice, I'd love Paranoid Android, but I went hold my breath.
CM is already in development . https://github.com/CM-zenfone2
BrokenROM https://github.com/BrokenROM/device_asus_moorefield
Seems that are only for ZE551ML I hope that will be compatible with ZE550ML
If someone can get pure AOSP or CM working, the ROMs will flow out like water... once a base is established building many ROMs is easy. If we get CM, then look for ROMs like Beanstalk, BlissPop, Carbon, , etc. to follow closely behind. Patience, it will happen...
MatteXperiaU said:
CM is already in development . https://github.com/CM-zenfone2
Click to expand...
Click to collapse
Yay! I really hope Paranoid Android follows suit. I LOVE Pa's Halo feature.
custom roms will help this phone.zenny 2 has one of the worst stock firmware optimization ever and seems like asus cant fix the problems.
Be patient guys, I just sent a couple developers phones this week.
Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
Cool! I see lots of potential ROM development for this phone!
Sent from my ASUS_Z00AD using XDA Free mobile app
Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
Good to see Asus is showing commitment to this phone. Also great to see you guys are embracing the aftermarket ROM community. More vendors need to be supportive like this.
We love the enthusiast community - you guys are the ones that like to tinker and have contributed to our growth over the years when we were just a motherboard vendor. I bet many of you still have fond memories of building PCs with our components before tinkering with phones .
Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
Awesome! Is there/will there be collaboration with the developers regarding the kernel and device tree from ASUS as well? That would be key to have a fully-working custom ROM in the nearer future (versus the developers having to learn from scratch and sort of fend for themselves, kludging their way along and delaying the end goal).
So exciting!
We post our kernel source, but that's all we can offer, unfortunately. Our software development is done at our Taiwan HQ. But if any devs need anything, just send me a PM and I'll ask our software team.
Tuanies said:
We love the enthusiast community - you guys are the ones that like to tinker and have contributed to our growth over the years when we were just a motherboard vendor. I bet many of you still have fond memories of building PCs with our components before tinkering with phones .
Click to expand...
Click to collapse
Tuanies said:
We post our kernel source, but that's all we can offer, unfortunately. Our software development is done at our Taiwan HQ. But if any devs need anything, just send me a PM and I'll ask our software team.
Click to expand...
Click to collapse
Just got one single request... Open an official outlet or distributer in Pakistan... I am buying your items off international vendors without warranties... Would love to see if I can get some support locally...
Tuanies said:
We post our kernel source, but that's all we can offer, unfortunately. Our software development is done at our Taiwan HQ. But if any devs need anything, just send me a PM and I'll ask our software team.
Click to expand...
Click to collapse
CC: @TheSSJ, @shakalaca, @jrior001, @crpalmer, @sorg, @Harfainx, @vampirefo and other zf2 developers.. :victory:
Tuanies said:
Be patient guys, I just sent a couple developers phones this week.
Click to expand...
Click to collapse
This makes not much sense to me honestly. Why locking a bootloader in the first place and then stating to push development hard by providing test phones to specified devs?
But still I want to thank you for your commitment in making this phone a huge success - we'll kick Galaxy and Xperia and the likes out once done
Good thing to see Asus sharing to make custom ROMs efficient.
Already on Harfainx's ROM, can't wait to see things going even further.
SBFarooq said:
Just got one single request... Open an official outlet or distributer in Pakistan... I am buying your items off international vendors without warranties... Would love to see if I can get some support locally...
Click to expand...
Click to collapse
Unfortunately in only responsible for North America and have no say for any other regions.
TheSSJ said:
This makes not much sense to me honestly. Why locking a bootloader in the first place and then stating to push development hard by providing test phones to specified devs?
But still I want to thank you for your commitment in making this phone a huge success - we'll kick Galaxy and Xperia and the likes out once done
Click to expand...
Click to collapse
This is my push from Technical Marketing for North America due to needs and wants for the US market. I place great emphasis on the community that has made many of the previous phones I've owned so great. I want that for the ZF2.
I'll probably start development for this phone once i get it. Never worked with an x86 android device before but it sounds like a fun challenge
Tuanies said:
This is my push from Technical Marketing for North America due to needs and wants for the US market. I place great emphasis on the community that has made many of the previous phones I've owned so great. I want that for the ZF2.
Click to expand...
Click to collapse
Hi,
I've got some sort of situation here concerning building the kernel for ZF2 on my own. I downloaded the kernel source from ASUS website and followed the instructions one by one (download the android source code, use the appropriate toolchain, issue the kernel build command using fhd_defconfig, etc.
The phone boots and works good, BUT:
The phone never gets to deep sleep mode because of hsic_s3_wlock (kernel wakelock from USB HSIC). Could you please ask someone from the technical department to check what is causing this or if any config entry is missing? I am really starting to doubt that this is something I can influence at all
i found this on huawei's website
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
would it aid in building AOSP for us? because i want to get started on oreo but i cant find a device tree.
Interesting. H1611 is in there (use search feature). Hoping beyond hope and wish I had more time to do something with it.
Yeah but I dont know how well it would work with Oreo. Same thing here, I don't exactly have enough time for it. Possibly sometime around Christmas I could look into it(also my computer can't compile very well, and I'm getting a new one)
im pretty sure thats the same kernel source code we have had for like i dunno 4 months or so
madvane20 said:
im pretty sure thats the same kernel source code we have had for like i dunno 4 months or so
Click to expand...
Click to collapse
so do you know if it would aid in building roms?
with building and marshmallow ya if we get a working device tree built. as for android n and above i think its gonna require a programmer thats been at this stuff for years. it might also need to be one too for device tree. ive been to busy with rl stuff havent had time to about much else
Madvane: Can you outline what you did to create a ROM based off stock? I want to shortcut it as much as possible and see if I can build a reference ROM from stock within a week. I am a Linux developer by trade (11+ years) but Android is foreign to me. I've written kernel modules before so I'm not afraid of modifying source code. The XT has great specs but it seems to slow down and lag due to bloat (Phone Manager perhaps?) How far did you get on the Lineage port? Thanks.