Database Develop

[KERNEL] Generic Android 3.0 kernel source

I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.

Ezekeel said:
I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.
Click to expand...
Click to collapse
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.

Lol Ezekeel, I've seen you praying Jean-Baptiste Queru for the Crespo-tree sources! I Think we have to wait one or two weeks...

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
Pretty much all the device-specific stuff is missing, but maybe we are lucky and no changes have to be made in the device-specific source for the Nexus S and we can simply keep these parts from our current code.

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?

Luxferro said:
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?
Click to expand...
Click to collapse
JBQ said that even if gpu is the same (omap4430) in galaxy nexus and in pandaboard he wasn't able to run the gnexus driver on the pandaboard and vice-versa because of some library-dependencies. So I think the drivers will not work out of the box...

awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.

Nice to know

simms22 said:
awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.
Click to expand...
Click to collapse
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App

matt2053 said:
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.

Maximilian Mary said:
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.
Click to expand...
Click to collapse
In one of the google groups replies JBQ said that they will always focus on the flagship phone.
Up until recently that was Nexus S.
Now the torch was passed and it's Galaxy Nexus first.
They will not dull the luster of their flagship phone by making libs and drivers for released phones available before the flagship phone has had time to shine.

I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
That will be a huge effort to fix, and it would probably cause more harm than good if you managed to fix the conflicts. I'm sure we'll have our sources in one/two weeks tops, so that's not worth the hassle in my opinion.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?

dvgrhl said:
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?
Click to expand...
Click to collapse
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.

Ezekeel said:
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.
Click to expand...
Click to collapse
First thanks for opening this thread, is a good idea.
At this moment I will wait some days to see if the crespo kernel 3.0 goes into public git, otherwise I will join the project to move the kenel since it will have multiple benefits.
Kalim

[HOWTO] Build KitKat for Nexus 5

Hi all,
I typed my notes on building KitKat AOSP/Kernel for the Nexus 5 (hammerhead) here: http://nosemaj.org/howto-build-android-kitkat-nexus-5 . It's the cumulative result of a lot of hours of hacking! Hope it is helpful.
Best wishes,
Jameson

jhwilliams said:
Hi all,
I typed my notes on building KitKat AOSP/Kernel for the Nexus 5 (hammerhead) here: http://nosemaj.org/howto-build-android-kitkat-nexus-5 . It's the cumulative result of a lot of hours of hacking! Hope it is helpful.
Best wishes,
Jameson
Click to expand...
Click to collapse
Good work, where is your ROM?

jhwilliams said:
Hi all,
I typed my notes on building KitKat AOSP/Kernel for the Nexus 5 (hammerhead) here: http://nosemaj.org/howto-build-android-kitkat-nexus-5 . It's the cumulative result of a lot of hours of hacking! Hope it is helpful.
Best wishes,
Jameson
Click to expand...
Click to collapse
Thank you very much
I have my Ubuntu all set up and ready to go!
Sent from my Nexus 5 using Tapatalk

neobuddy89 said:
Good work, where is your ROM?
Click to expand...
Click to collapse
Hey @neobuddy89 -- I primarily typed that up to help enable other developers, but it could be fun to post a fastboot-compatible update package. Any tips on a good filehost so I don't slam my personal box?
Also I think I personally will stick with Stock on my personal device, but maybe someone will use this as a jumping-off point for an improved ROM.
It's straight AOSP, but with enough proprietary junk to have things like connectivity, location, play store, gmail etc.

In short, just grab the working tree
Click to expand...
Click to collapse
I know this will result in many gigs of data, do you know about how many? I've been downloading for about 24 hours.
Sent from my Nexus 5 using XDA Premium 4 mobile app

koe1974 said:
I know this will result in many gigs of data, do you know about how many? I've been downloading for about 24 hours.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
According to the Android documentation, source is about 8.5GB, then goes up to 30GB for a single build.

Thanks for this OP. Currently learning how to build from source. I was going to start with pure AOSP, but I got too excited for Paranoid Android 4.0. I set everything up and the build is compiling right now as I type this, but your guide is a lot more informative than the one I used. It would be good to build AOSP just because it's base android, but I really wanted PA haha. Anyways it's really in-depth and I'm sure I'll learn a thing or seven from it. Thanks

jhwilliams said:
According to the Android documentation, source is about 8.5GB, then goes up to 30GB for a single build.
Click to expand...
Click to collapse
Your repo builds without a hitch. Great stuff! It was too easy and helped confirm my system is configured correctly.
Now to try using your notes and do it manually. I am going to try to use them on 4.4.1.
Nice winter weekend project.
Sent from my Nexus 5 using XDA Premium 4 mobile app

RoyJ said:
Thanks for this OP. Currently learning how to build from source. I was going to start with pure AOSP, but I got too excited for Paranoid Android 4.0. I set everything up and the build is compiling right now as I type this, but your guide is a lot more informative than the one I used. It would be good to build AOSP just because it's base android, but I really wanted PA haha. Anyways it's really in-depth and I'm sure I'll learn a thing or seven from it. Thanks
Click to expand...
Click to collapse
Building from source isn't hard, it's mostly following directions. Cherry picking and fixing merge conflicts is where the real fun begins! :beer::beer::beer:

du bist krank said:
Building from source isn't hard, it's mostly following directions. Cherry picking is where the fun and fixing merge conflicts is where the real fun begins! :beer::beer::beer:
Click to expand...
Click to collapse
Eager to learn, my friend! Once I get familiar with the build process I plan to learn how to cherry pick commits / fix errors arising from cherry picking said commits. The PA build failed last night, but EvanA told me that would happen. They merged 4.4.1 and updated blobs so the build should work now. I just synced their source again and it is building now. Once I get a few successful builds I'll dive into all that. I really dig threads like this. We had a developer support thread in the gnex forum. I did a lot of reading over there, but hadn't got into building yet. That has to be one of my favorite things about the nexus. Community support. I mean I had a PA team member help teach me how to build their unreleased ROM. Awesome.
Sent from my Nexus 5 using Tapatalk

koe1974 said:
I am going to try to use them on 4.4.1.
Click to expand...
Click to collapse
Cool! Yea, I'm just waiting for the factory images and binary packages to get posted. It may work with the 4.4 binaries, but I'm keen to wait a few days in case it's a waste of time for now.

Wow, never realised such a powerful pc was required.. I don't think my 2GB AMD machine will cut it

jhwilliams said:
Cool! Yea, I'm just waiting for the factory images and binary packages to get posted. It may work with the 4.4 binaries, but I'm keen to wait a few days in case it's a waste of time for now.
Click to expand...
Click to collapse
They are available now.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Thanks for this. I just started upgrading my Ubuntu yesterday. Going from 12.04 to 12.10 to 13.04 to 13.10 lol.
Once I get that going I'm gonna come back and check this out.
Sent from my Hammerhead

EDIT: replacing libmmcamera_interface.so from stock does fix the problem.
Anyone getting a thin green line artifact along the left or bottom edge (depending on orientation) of videos recorded with the rear camera and a wider artifact on the right with front facing camera?
Perhaps a solution. Post 85. http:// forum.xda-developers.com/showpost.php?p=47283918&postcount=85
Sent from AOSP koeMod 4.4.2 w/ Franco kernel

koe1974 said:
They are available now.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah, just remembered to update the thread. My blog post is the same, but I have a new tree available:
repo init -u git://github.com/jamesonwilliams/platform_manifest.git -b android-4.4.2_r1

thanks for this man

I need to add a few files to the ramdisk. Any idea how to do this before the final make?
I would prefer not to have to repack to boot.img.
Sent from AOSP koeMod 4.4.2 w/ Franco kernel

this is really helpful,thanks a lot man. Maybe I'll learn it

Development Progress?

When is development for the device going to pick up? There's not much out there! I know it just came out but I expected more. I installed the Sky high Kernel after I rooted and I really like it. I have my A15 cores overclocked to 2.1GHz and have all cores undervolted, as well as overclocked the GPU and the device is totally stable!! My only issue with root/SkyHigh kernel (not sure which is the issue) is that my screen mirroring does not work. It will try to connect and say hardware issue. Anyways, everyone just post your thoughts, opinions and such about the device and development. I'd love to hear ideas and info out there. This device is AmAzInG!

Yep the 8.4 got a kernel but nary a peep on any rom activity. I think the problem is that most developers that wanted a high res tab like this already bought the Pro model and are not upgrading to the S.
I'm waiting on someone to port CM over so I can go pure Android and get rid of this excessive Touchwiz javascript lag on pageloads. For that I'd happily give up the gimmicky stuff like split screen that I rarely use anyway.

mitchellvii said:
Yep the 8.4 got a kernel but nary a peep on any rom activity. I think the problem is that most developers that wanted a high res tab like this already bought the Pro model and are not upgrading to the S.
I'm waiting on someone to port CM over so I can go pure Android and get rid of this excessive Touchwiz javascript lag on pageloads. For that I'd happily give up the gimmicky stuff like split screen that I rarely use anyway.
Click to expand...
Click to collapse
Cm??? Good luck.

mitchellvii said:
Yep the 8.4 got a kernel but nary a peep on any rom activity. I think the problem is that most developers that wanted a high res tab like this already bought the Pro model and are not upgrading to the S.
I'm waiting on someone to port CM over so I can go pure Android and get rid of this excessive Touchwiz javascript lag on pageloads. For that I'd happily give up the gimmicky stuff like split screen that I rarely use anyway.
Click to expand...
Click to collapse
I personally have been a fan of the Touchwiz UI. And actually like and use a lot of its features. This is a very capable tablet and I think devs will arise soon.

suzook said:
Cm??? Good luck.
Click to expand...
Click to collapse
Why not? The Tab Pro line has CM.

There will be more development when we have a working recovery. No one really wants to drop mods if there's no way to flash them. Hopefully Team Win will read my email.

mitchellvii said:
Why not? The Tab Pro line has CM.
Click to expand...
Click to collapse
All the devs just laid out good $ for the pro....its gonna be a while we get any good devs. Just enjoy touchwiz and root.

12MaNy said:
There will be more development when we have a working recovery. No one really wants to drop mods if there's no way to flash them. Hopefully Team Win will read my email.
Click to expand...
Click to collapse
Philz recovery please.

suzook said:
All the devs just laid out good $ for the pro....its gonna be a while we get any good devs. Just enjoy touchwiz and root.
Click to expand...
Click to collapse
The S line is better than the Pro, right?

Stupid1337deer said:
The S line is better than the Pro, right?
Click to expand...
Click to collapse
Other than the screen? Same. Unless a Dev is really wanting amoled screen, we might be Sol for a while. Sammy needs to stop making new tabs every few months.

suzook said:
Other than the screen? Same. Unless a Dev is really wanting amoled screen, we might be Sol for a while. Sammy needs to stop making new tabs every few months.
Click to expand...
Click to collapse
Well I love the screen lol.

mitchellvii said:
Why not? The Tab Pro line has CM.
Click to expand...
Click to collapse
No, only the Qualcomm based Snapdragons, not Exynos based models like the Tab S.

Freakstyler said:
No, only the Qualcomm based Snapdragons, not Exynos based models like the Tab S.
Click to expand...
Click to collapse
Ur right. Forgot about the Exynos thing.

I'll tell you this,if we get anxious about a new device and the possible abilities. so will the devs
Recovery works well so it won't be long
Nexus 5 via Tapatalk

Beans is looking to bring his super fine Alliance rom to our tab. First he looking for donations to help him buy one. He's a stand up guy so any money you give him, will go towards product purchase and development.
Sent from my Alliance Galaxy S5.

suzook said:
Other than the screen? Same. Unless a Dev is really wanting amoled screen, we might be Sol for a while. Sammy needs to stop making new tabs every few months.
Click to expand...
Click to collapse
I would disagree. It's better looking, lighter. Software and hardware perform much better
Sent from my SM-T800 using XDA Premium 4 mobile app
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
Rooting and recovery can be done in minutes that's got to be a good sign
Sent from my SM-T800 using XDA Premium 4 mobile app

I'm just waiting on a deodexed ROM for T700. Then I'll start theming.

Cyanogenmod on the note 4 snapdragon

Hi Guys ! Is somebody already trying to boot Cyanogenmod ? I'm a reverse engineer, have done quite a bit of development work on CM11 for the S4 I9500 and just ordered my Note 4 snapdragon and planning to run and optimize CM12 on our Snapdragon Note 4

gekkehenkie11 said:
Hi Guys ! Is somebody already trying to boot Cyanogenmod ? I'm a reverse engineer, have done quite a bit of development work on CM11 for the S4 I9500 and just ordered my Note 4 snapdragon and planning to run and optimize CM12 on our Snapdragon Note 4
Click to expand...
Click to collapse
this is xda my man , and someone everytime is trying their best for us..... like what u said just gave me hopes.... bang cm12 soon bro

Er. Aditya said:
this is xda my man , and someone everytime is trying their best for us..... like what u said just gave me hopes.... bang cm12 soon bro
Click to expand...
Click to collapse
Yes, I'm hoping more developers will switch to this device and will start working on booting and running CM as smooth as possible. I just ordered my note 4 yesterday, I still have to wait 2 weeks to receive my device (I don't live in a snapdragon country), hoping to work together with some other devs but if not, going to give booting CM myself a try and will update and report here for sure !

I'm new to the Note line so I have a question. Does the S-Pen work (just work, non of the fancy features) with custom Roms or do devs need to optimize it?

I would love to see it running Lollipop.
Patience... is the key. It will happen.

Narekrocks said:
I'm new to the Note line so I have a question. Does the S-Pen work (just work, non of the fancy features) with custom Roms or do devs need to optimize it?
Click to expand...
Click to collapse
The spen will work on any rom but samsung specific apps like snote will only work on samsung based roms. On cm based roms there are alternative apps like papyrus and on the note 2 there were specific spen apps made for cm roms so guess the same thing will probably happen on the n4

Wrong forum my man. Please take your thread to the right place. Facepalm

Droideatsappleforlunch said:
Wrong forum my man. Please take your thread to the right place. Facepalm
Click to expand...
Click to collapse
"This forum is intended for XDA members to find or discuss development on the Galaxy Note 4, including ROMs, kernels, rooting, mods and much more, specifically for the Qualcomm Snapdragon variant of the Note 4."
Sounds like the right place to me.
Anyway on topic: here's the general porting method: http://wiki.cyanogenmod.org/w/Doc:_porting_intro and here the samsung code: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=910f
Unfortunately going by what Samsung released previously, we'll need code directly from Qualcomm, did anybody find chipset code for the 805 already ?

And here's the Lollipop Nexus 6 (of course also running snapdragon 805) code:
http://www.xda-developers.com/android/android-lollipop-source-pushed-to-aosp/

Oh and also found this thread, should be helpful to get a start: http://forum.xda-developers.com/showthread.php?t=2532873

Anyway, getting my device in 2 weeks, hopefully around that time CM12 will be released too, mabye we should wait for that anyway, but I wanted to start this thread already to function as a knowledge sharing thread regarding getting cyanogenmod running on the Note 4. Going to do some digging in the sources codes already and see what's there and what's missing.

https://plus.google.com/u/0/+TonyLayher/posts/ABurAWxbk4V

slayher said:
https://plus.google.com/u/0/+TonyLayher/posts/ABurAWxbk4V
Click to expand...
Click to collapse
Is Tony the official cm maintainer for note series d3vices?
Texted from Note 4

Droideatsappleforlunch said:
Love it how you edit rule number 15 for your own benefit.
http://forum.xda-developers.com/announcement.php?f=263
Click to expand...
Click to collapse
Sorry but I really miss your point man. This is development and most importantly, this is Snapdragon: this thread has really not much to do with Exynos (which most likely will never even run CM12, at least not in the next year), so I really don't see in which forum it would be more ontopic than this one. If you disagree, let me know in which forum you feel it should be posted in and why and if it makes sense, I'll ask the mod, but again, I really don't see it.

slayher said:
https://plus.google.com/u/0/+TonyLayher/posts/ABurAWxbk4V
Click to expand...
Click to collapse
Wow, that's really wonderful news, you made my day man, thanks !!! :good: :fingers-crossed: Can't wait to flash it (need to wait 2 weeks to get my hands on the device though, damn, hehe). I've done quite a bit of work on the i9500, Ironing out bugs by reverse engineering stock ROM and my goal is to make CM12 on our Note 4 the best Cyanogenmod experience so far ! Man, really cant wait !

I just got mine yeaterday im super excited. I'm really surprised how steady it feels in hands. It doesn't feel like a Samsung device at all. My babe is already rooted and unlocked just waiting on lollipop

TheUndertaker21 said:
I just got mine yeaterday im super excited. I'm really surprised how steady it feels in hands. It doesn't feel like a Samsung device at all. My babe is already rooted and unlocked just waiting on lollipop
Click to expand...
Click to collapse
What I never understoodbis why DPI is so freaking high. Looks incredibly ugly. Set mine to 480.

Narekrocks said:
What I never understoodbis why DPI is so freaking high. Looks incredibly ugly. Set mine to 480.
Click to expand...
Click to collapse
Picture was taken as soon i took it out of the box. So i didn't have time to do anything

Narekrocks said:
What I never understoodbis why DPI is so freaking high. Looks incredibly ugly. Set mine to 480.
Click to expand...
Click to collapse
440 here [emoji6]
Texted from Note 4

Pointless thread in developer forum. Can't wait to see this closed. What is become of xda that anyone can post what he likes and where he wants.

Developer Support

Just wondering what other developers have decided or shown interest in grabbing a OnePlus 3. I am thinking of getting one, but the cost is a bit steep to just support a device that I may not even use as a daily device. If there is a small amount of developers, I will be more likely to get one because I believe that users deserve to use their phone how they want, not how the OEM wants them to. This is more or less a roll call to see who will be supporting the device from a dev standpoint.

read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)

Dinjesk said:
read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)
Click to expand...
Click to collapse
Anyone kernel side?

DespairFactor said:
Anyone kernel side?
Click to expand...
Click to collapse
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.

Dinjesk said:
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.
Click to expand...
Click to collapse
I am considering it, I have plans to bring kexec hardboot to the device if I get it

DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday

_PrEzi_ said:
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday
Click to expand...
Click to collapse
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.

DespairFactor said:
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.
Click to expand...
Click to collapse
I can perfectly understand that. You - like me - do like to do things either perfectly or at least v. good or better leave them be if they are only 'ok'.
Nevertheless - please do consider. I am not promising anything but my guts tell me OP3 will have a larger userbase than the OP2.
And again - no promises - but I like beer and also like to send 'virtual beer/pizzas' to the devs I feel are putting big efforts to keep the users happy. Probably other humble users too :highfive:

Would be killer to have you onboard.

Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk

DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app

To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.

gururoop said:
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
derdjango said:
To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.
Click to expand...
Click to collapse
inzaghi75 said:
Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
For right now I will blind build a kernel and try to get kexec working. If I somehow get the budget to grab one, I will. I hear there is a BrokenOS coming, but do not ask anyone about it, just wait for a release. I will not bring UBER ROMs to this device because we do not run CAF based sources.

OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker

Taker18 said:
OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker
Click to expand...
Click to collapse
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs

Naman Bhalla said:
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
I agree, it is hard to maintain several projects at once for one device, let alone a few. IIRC, a lot of you come across from other OP devices too, not sure if you are dropping support on previous devices.

Well, I'm too working on a kernel for this phone (albeit don't have device)
Sent from my Moto X using Tapatalk

##W4TCH0UT## said:
Well, I'm too working on a kernel for this phone (albeit don't have device)
Click to expand...
Click to collapse
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs

Naman Bhalla said:
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.

DespairFactor said:
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.
Click to expand...
Click to collapse
I think you know me. Remember me from one group we created ? I think of you can get a device, do support it. Infact, in one way, people support of you support them. So, get a device, support the device and a lot chances are that people will support you and you might be able to overcome all expenditures on the device. And believe me, many devs told me this too. And I know your kernel from 6P. Will be great if you can support, and prolly you *might* have a surprise too (I am not saying anything, but, well) . We do need your support, but it will be best if you can support when you have a device too. It will generate people's trust upon you and also you won't need to get with wrong bug reports.
Sent from my OnePlus2 using XDA Labs