It has come to my attention that no more custom roms and or similar such development are available for our device. I can understand the frustration of previous developers due to the camera issue and other such bugs when developing for this device. Is there any hope for such a good phone?Any developers willing get this device to its maximum potential?... I would hate to see this go to waste. Thoughts?
I agree , I have one with a cracked screen but it works fine. If not having one is the issue hit me up, you can have it, but we want lineage or something that works good. I would even thow some BTC when it's done.
Development
I know a little bit about stuff works, and I've been thinking about possibly doing some development for this device. I'll just need to download the AOSP source, and I already have the MIUI source sitting by. I could possibly try cooking up some ROMs in my spare time. It'll take time though, if that's not too high of a price to pay.
SoulDJ673 said:
I know a little bit about stuff works, and I've been thinking about possibly doing some development for this device. I'll just need to download the AOSP source, and I already have the MIUI source sitting by. I could possibly try cooking up some ROMs in my spare time. It'll take time though, if that's not too high of a price to pay.
Click to expand...
Click to collapse
That would be great! I would definitely be willing to test any builds you could cook up. I may not know to much but I can certainly help in anyway necessary.
SoulDJ673 said:
I know a little bit about stuff works, and I've been thinking about possibly doing some development for this device. I'll just need to download the AOSP source, and I already have the MIUI source sitting by. I could possibly try cooking up some ROMs in my spare time. It'll take time though, if that's not too high of a price to pay.
Click to expand...
Click to collapse
Good my friend...!!!
null
Related
The intent of this thread was to provide a consolidated answer to all of those waiting patiently (some, not so patient) for a complete Android ROM for the SE Xperia X1.
Many perceive Android as "a hacker's OS" because it is both open source, and supported on so many other HTC devices. Because of this, I suspect many of the "spectators" here (like me) incorrectly assumed that Android on Kovsky (or, any HTC smartphone) would be a straight forward affair, considering some of the amazing work done here with the Windows Mobile ROMs.
It seems, however, that creating a usable Android ROM for Xperia is far more difficult than creating WM6 ROMs? Android has been out for quite some time and there's still no widely available Android ROM for Xperia X1. It is for this reason that I've started this thread.
I'd like to hear from those that have/are working on Android about the challenges in putting together an Android ROM for Xperia X1. What has contributed to this being a difficult OS to port to Kovsky?
Is it driver support? Perhaps Kovsky has a unique selection of hardware that complicates the process? Or, has much of the effort been directed towards Haret vs. a native ROM? If so, why? Can the Haret work be merged into an effort to create an Android ROM or are these different approaches completely exclusive to one another?
Perhaps there are IP/DRM/license issues that are complicating the effort? I'd very much like to hear from ROM chef and devs working on this port.
While it may seem like a idealist perspective, I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones. I'm certain that interest in Android on Kovsky is very high. Are there areas where the community might be able to assist with direct hardware, financial or other contributions?
So please, sound off. I'm very interested to hear about chefs/devs experiences with Android and I'm certain there are many here that would like to hear more about this port.
I just didnt know how to tell all you told here... I really want to know because I love my x1 and I love Android.. but i can"t help
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
wphoenix said:
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
Click to expand...
Click to collapse
would like that too, i've only been reading for some good time about the advances, and would like very much to take part in the development of the kernel, but don't really know where to start from
Also, what Viper says its very true... the work is probably a long way from done, depending on how much help the dev's get, which is, from what i've seen, not much.
about Toe_Cutter's comment "I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones" ... well, yeah, i think it could... at least i hope so.
xD
cool down all your heads and lets just help in every way we can
...as (ilgreco112) does xD... cheering up isn always bad hahaha
ps: first post!! ... Hi!
Viper89 said:
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
Click to expand...
Click to collapse
As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM.
But what do you expect when spectators ask about the issues, and receive nothing in response?
In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how.
Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM).
Anyone care to break the cycle and help the community understand the issues?
Well, the problem is that you can never guess what's required and how to achieve it. First of all, developers really know nothing about the hardware before they begin hacking it. Until you finish the job, you can't estimate the time it takes to complete. The major problem is that most of us devote just a tiny bit of our time to the porting, because there are lots of interesting things to learn and to do except it, but mostly because everyone's either studying or working (or even both).
But if you really want to know what's needed.. well
1. Fix the LCD panel (add the initialisation code)
2. Fix the power saving (that's the greatest PITA right now) and 3D (the latter should be easy and is not really critical)
3. Implement Bluetooth, FM Radio, Camera (Should not be really hard on the driver side, but rather on the RPC protocol side)
4. Fix USB (should be easy.. actually, everything's done on the device driver side, the problem seems to be with the msm usb driver itself.. just needs real debugging)
5.Make a version of rom that boots from NAND (well, once you get the LCD to work correctly it's not a problem. It actually boots very well off nand, but without LCD and USB working it's not much fun, to tell the truth)
6.Clean up the code, drop the ****ty-droid and head forwards to SHR/Maemo MER/Meego or some other real linux distro with X11 and other things
7.Write up misc stuff (like optical joystick, illumination, new keypad driver and others)
But really, it you want to help, just begin researching everything yourself and exploring wince drivers. You know, Theo de Raadt once said: "shut up and hack", and that's the only way to get things done.
full ack
@sp3dev
full ack your post. the main problems ar not at android 2.x this source we have. but the kernel an its's modules (for kovsky) are the problem.
regards
Toe_Cutter said:
As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM.
But what do you expect when spectators ask about the issues, and receive nothing in response?
In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how.
Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM).
Anyone care to break the cycle and help the community understand the issues?
Click to expand...
Click to collapse
The ROM question has been answered time and again throughout various threads on xda-dev.
There is no real issue "porting" Android to kovsky. Android is a virtualized environment running on a linux
kernel and it is that kernel that has to be ported. "Android" runs 100% on kovsky with minimal modification.
So. There is only one issue with the linux kernel - that issue is when the linux kernel for kovsky
is good enough for someone to make the effort to pack up a ROM with that kernel,
a bootloader and the android system.
Now, the consensus is the kernel isn't as yet good enough for daily use -
if someone with the skills decides it is and makes a ROM, then they will
obviously do so.
The list of kernel stuff to be fixed is broadcast all over this board and asking kernel devs
to repeat themselves ad nauseum won't get it done any faster
Ok, I successfully rooted and installed other apps on my NC tonight. Thanks for the great directions! This really makes it a great option at $249 over something like the Galaxy Tab. It still of course has all the remnants of Barnes & Noble everywhere. What are the chances that we will eventually get a custom ROM or perhaps Cyanogenmod so we can truly have a generic Android tablet? I just don't know how much something like that would entail and wonder if anyone can provide a little more info.
Thanks!
I think we'll see some custom goodies, but with everything so early on, I expect it'll take a few weeks before we see the big stuff.
I'm willing to be patient, I'm rooted, and don't mind where I am now, considering the NC hasn't even been on shelves for 3 weeks yet.
graymulligan said:
I think we'll see some custom goodies, but with everything so early on, I expect it'll take a few weeks before we see the big stuff.
I'm willing to be patient, I'm rooted, and don't mind where I am now, considering the NC hasn't even been on shelves for 3 weeks yet.
Click to expand...
Click to collapse
lol not even 2 weeks..it came out the 19th
Oh I know it will take some time. It's pretty good like it is after rooting. I just wanted to know more about how feasible it is. Could there potentially be huge roadblocks?
nlowhor said:
Oh I know it will take some time. It's pretty good like it is after rooting. I just wanted to know more about how feasible it is. Could there potentially be huge roadblocks?
Click to expand...
Click to collapse
The only roadblock I can potentially forsee is B&N holding out on releasing the source for the NC.
I think it's hard to say without someone actually working on it. Also, we don't have many options for a factory reset now, so development can be kind of risky.
ZeroSX said:
The only roadblock I can potentially forsee is B&N holding out on releasing the source for the NC.
Click to expand...
Click to collapse
yes, because the drivers and kernel are needed
bg
The drivers are out there, and look to be the same ones in use by other Cyanogen targets (the TI WAN chip is in the AOSP tree already, the PowerVR SGX chip is pretty common).
In fact the nook color looks a lot like a motorola droid, from a HW point of view, IIRC.
Thanks for the info. This all sounds like good news. Really looking forward to CM or some other AOSP-style ROM.
B&N has released the source and the developers kit. Start hacking!
Okay, I wanted to take a moment to talk about the development for our device.
Recently CM decided to no longer support Tegra 2 devices as they are starting to get dated. So basically that boils down to the fact that the CM10.1 will be the last one for our device that I do.
Currently I'm trying to jump start the process of putting out our updated kernel from 2.6.36.4 -> 3.1. This will hopefully put our device at a point where everything should work.
DerArtem is the lead developer on the kernel, but has been busy because he just got married and works a full time job, which puts a damper on his time (which is understandable).
I am putting in an 1-2 hours every morning on this, trying to fix those bugs and was just tipped on a possible way to minimize the overload of the log with the USB error. This will be a hold off till we get the kernel done as these issues should go away after the update.
I am sad to see this tablet come to an end (though not yet). We all have to admit that its time we all start moving on. I am going to push to get these last bit done and call it quits. This can take anywhere from 2-5 months to finish up, maybe a bit longer and then our device will be done.
I have had an amazing time learning about Android under DJ_Steve and DerArtem, and thank them for taking the time to teach me.
I thank you what you done so far and in the future. Can blame you one bit for your decisions.
I think setting an "end game" is respectable, and is a good goal. The kernel work is the key to smoothing things over on what has been wonderful development thus far.
The fact you've taken us this far sir is very commendable and you and the crew deserve many thanks. For your time and efforts, you have my gratitude, and my tablet serves as a hobby rather than a shelved device.
4.2.x has been flawed since release by Google, and with the way android has evolved, future versions will undoubtedly require more current hardware and OEM support. The latest tablet releases have as much computing power as a 2 year old laptop! Thanks to you, we've managed to play with JB, and I look forward to what comes before a final release.:thumbup:
Sent from my Galaxy Nexus using xda premium
Wow, I hate doing this, but I may have to close up shop on all this. Severe lack of any real work is getting done as I am looking for jobs and trying to have some game time as well.
The time to do this isn't worth it. I may ask for payments for my next ROM ($1 per download). Seriously, I hate doing it but this just isn't worth it anymore. Currently working on a AOKP release, to see if this may resolve any bugs I am having.
Hi giveen,
first of all thank you for all the time you spent on our old device. I already donated you some time ago and always had an eye on your progesses. I really understand your decision to ask for some payment for all the work and that is absolutely ok for me.
I use my DS7 (wifi only) on a daily base to check my mails, surf the net and stream some TV and video from my HTPC. Until now I use a HC 3.2 mod (514 mod by dreamer) together with V6 Supercharger script and am so far quite ok with that. So far I see no need to buy me a new tablet as long as the DS7 fits my few needs
But before I collect all my courage and update my DS7 in the near future to your CM10 build I want to ask a few things:
1. Is your build already stable and usable enough for the things I do with my device?
2. Any news from DerArtem about the kernel work? Will there be a new kernel for our device in the future?
THX,
Michael
Montezuma10 said:
Hi giveen,
first of all thank you for all the time you spent on our old device. I already donated you some time ago and always had an eye on your progesses. I really understand your decision to ask for some payment for all the work and that is absolutely ok for me.
I use my DS7 (wifi only) on a daily base to check my mails, surf the net and stream some TV and video from my HTPC. Until now I use a HC 3.2 mod (514 mod by dreamer) together with V6 Supercharger script and am so far quite ok with that. So far I see no need to buy me a new tablet as long as the DS7 fits my few needs
But before I collect all my courage and update my DS7 in the near future to your CM10 build I want to ask a few things:
1. Is your build already stable and usable enough for the things I do with my device?
2. Any news from DerArtem about the kernel work? Will there be a new kernel for our device in the future?
THX,
Michael
Click to expand...
Click to collapse
If its from your HTPC, I honestly don't know as I have never tried it before. This latest build is much more stable, though it still has the gmail keyboard crash that I am tracking down. If you are happy with what you have, don't do anything. I would hate for you to make a purchase and not be happy.
I haven't heard from DerArtem in several weeks because he is in another country (Russia) doing a job. (He lives in Germany). To be honest, I don't think a new kernel is going to happen and I'm really upset by it.
giveen said:
If its from your HTPC, I honestly don't know as I have never tried it before. This latest build is much more stable, though it still has the gmail keyboard crash that I am tracking down. If you are happy with what you have, don't do anything. I would hate for you to make a purchase and not be happy.
I haven't heard from DerArtem in several weeks because he is in another country (Russia) doing a job. (He lives in Germany). To be honest, I don't think a new kernel is going to happen and I'm really upset by it.
Click to expand...
Click to collapse
One issue I see here is that when you start charging, a person paying for it like a app from the Play Store, they expect things to work. This "might" cause you to spend more time than you have been on it. Just my $0.02!
Didn't somebody donate an unused DS7 for DerArtem for this kernel project?
wptski said:
One issue I see here is that when you start charging, a person paying for it like a app from the Play Store, they expect things to work. This "might" cause you to spend more time than you have been on it. Just my $0.02!
Didn't somebody donate an unused DS7 for DerArtem for this kernel project?
Click to expand...
Click to collapse
They can contact me if they are having an issue. I appreciate the concern though.
Yes, someone did give their DS7 to him.
giveen said:
They can contact me if they are having an issue. I appreciate the concern though.
Yes, someone did give their DS7 to him.
Click to expand...
Click to collapse
I'll be downloading it later after some usage and a charge.
I'm working on sensors now. The old sensor drivers we used were for something we dont even have. I found the correct Android drivers but they are for qualcomm devices, so I need to modify them to work.
giveen said:
I'm working on sensors now. The old sensor drivers we used were for something we dont even have. I found the correct Android drivers but they are for qualcomm devices, so I need to modify them to work.
Click to expand...
Click to collapse
after several attempts and research I was still not the sound from my headphones with android android 2 and 3 sound going normally but not with 4.2.1 and 4.2.2.
Was wondering how hard it would be to port it to our device if there are not much differences
I really hope some wonderful devs port Lollipop G3 ROM to our Device.
Sent from my LG-D955 using XDA Free mobile app
same here we definitely have a lack of support for our device
We can all become devs if our time allows.. I myself almost complie a cm11 til i find out there is some coding myself to make it work because is unofficial, but little by little im getting to the point that i feel i can contribute to the community, like i said is can be hard if you let it be.. There is alot info, forums and help from google and even cm itself... To start with i mean you have to have some knowledge and never giving up, at least is working for me
Sent from my LG-D959
i hear you i tried a bunch of guides but i cant seem to pinpoint where im going wrong plus with the g3 leak of android 5 i wouldn't know where to start there are significant differences such as hardware and key components that need to be striped and customized to work with our device. for that we need the experience of a of senior lvl dev
ryuken11221 said:
i hear you i tried a bunch of guides but i cant seem to pinpoint where im going wrong plus with the g3 leak of android 5 i wouldn't know where to start there are significant differences such as hardware and key components that need to be striped and customized to work with our device. for that we need the experience of a of senior lvl dev
Click to expand...
Click to collapse
I'm gonna help everyone out here. The G3 leak will not make it to our device. All the apps are made to work on that 2k even (i.e all the apps have huge images) every app would have to be decompiled individually and resized to fit our screen. Then they would have to be modded (depends on what needed done) to work on our phone. Way to much work and possibly not even possible with kernel, etc that would need done.
As for support unfortunately we dont have many devs due to just not being a popular device and the locked down boot loader. We lost D-FUSE and justinwidebody to the G3, we do have playfulgod who's okay (definitely joking) and i know mattwheat is working on some stuff. When i get time I'm going to get back to working on my g3 themed ROM (some apps already ported by another user just need tweaked), but sadly I'm far from a dev so I won't be much help with big problems like cm11.
I do recommend everyone just jumping in and doing what they can. I started with small theme changes moved to small mods following guides and eventually released my first ROM in the note 2. You really can learn and we'll need all the help we can plus most people here are pretty helpful if you get stuck.
kintwofan said:
I'm gonna help everyone out here. The G3 leak will not make it to our device. All the apps are made to work on that 2k even (i.e all the apps have huge images) every app would have to be decompiled individually and resized to fit our screen. Then they would have to be modded (depends on what needed done) to work on our phone. Way to much work and possibly not even possible with kernel, etc that would need done.
As for support unfortunately we dont have many devs due to just not being a popular device and the locked down boot loader. We lost D-FUSE and justinwidebody to the G3, we do have playfulgod who's okay (definitely joking) and i know mattwheat is working on some stuff. When i get time I'm going to get back to working on my g3 themed ROM (some apps already ported by another user just need tweaked), but sadly I'm far from a dev so I won't be much help with big problems like cm11.
I do recommend everyone just jumping in and doing what they can. I started with small theme changes moved to small mods following guides and eventually released my first ROM in the note 2. You really can learn and we'll need all the help we can plus most people here are pretty helpful if you get stuck.
Click to expand...
Click to collapse
Definitely hear you loud and clear that's was my first assumption but how would it be possible for the g2 to receive a complete port of the ROM from the G3 that cloudfy came out with the g2 has Noway near a the same specs as the g3. That's something that I thought about but even with that said wouldn't it still be possible to exclude the lg apps and just push out everything that is non compatible for our device. But I am still doing some research and learning along the way don't want to release anything until I have a full understanding of what I'm actually doing.
ryuken11221 said:
Definitely hear you loud and clear that's was my first assumption but how would it be possible for the g2 to receive a complete port of the ROM from the G3 that cloudfy came out with the g2 has Noway near a the same specs as the g3. That's something that I thought about but even with that said wouldn't it still be possible to exclude the lg apps and just push out everything that is non compatible for our device. But I am still doing some research and learning along the way don't want to release anything until I have a full understanding of what I'm actually doing.
Click to expand...
Click to collapse
Looking at Cloudys threads i think it's their stock g2 ROM with the g3 apps ported. I'm saying that because all his ports use the same kernel. If it was really 3 different base ROMs that wouldn't work. I could be confused though and completely wrong. If that's the case then that's what I'm working in for us (or will if i ever get time. It won't be to the level of perfection his it's though. One thing to keep mind if that it's the case is its really hard to port apps from a higher version of android. I never said a full port was impossible, just that i highly doubt it happens. I'm pretty sure playfulgod isn't going to do it. I know I'm not even going to try. Not sure about matt or if there's adev hiding in the wings who may give it a go.
kintwofan said:
Looking at Cloudys threads i think it's their stock g2 ROM with the g3 apps ported. I'm saying that because all his ports use the same kernel. If it was really 3 different base ROMs that wouldn't work. I could be confused though and completely wrong. If that's the case then that's what I'm working in for us (or will if i ever get time. It won't be to the level of perfection his it's though. One thing to keep mind if that it's the case is its really hard to port apps from a higher version of android. I never said a full port was impossible, just that i highly doubt it happens. I'm pretty sure playfulgod isn't going to do it. I know I'm not even going to try. Not sure about matt or if there's adev hiding in the wings who may give it a go.
Click to expand...
Click to collapse
Hear you on that end but it does kinda suck that we don't have many devs tho but like you said if everyone can try and contribute something g it may help bring us the help we may need
ryuken11221 said:
Hear you on that end but it does kinda suck that we don't have many devs tho but like you said if everyone can try and contribute something g it may help bring us the help we may need
Click to expand...
Click to collapse
Is anybody here who can port G3 rom to G Flex?? anybody help us.
Kintwofan is right. If you're gonna port it needs to be a like brand, like resolution, like CPU / GPU. Makes it so much easier. Decompiling then recompiling and not finding out till its to late that something had an error when recompiling or when signing can be a ***** to find and or recover from late in the game. Or to find out all together that your hours on hours of hard work was for nothing. The g2 is more on our "like" side.
---------- Post added at 12:36 PM ---------- Previous post was at 12:19 PM ----------
Plus if you're just wanting lollipop apks on your phone. Most google apks have already updated and if not you can always download the 5.0 gapps extract and replace some don't work but most do. I've done it and use the google launcher. Almost has an aosp feel.
mapa2014 said:
Is anybody here who can port G3 rom to G Flex?? anybody help us.
Click to expand...
Click to collapse
not really to sure the only person i have seen port G3 roms over to other LG devices was and is cloudyfa
ryuken11221 said:
not really to sure the only person i have seen port G3 roms over to other LG devices was and is cloudyfa
Click to expand...
Click to collapse
Its easier to port g3 Roms to g2 due to all the the screen size (res folders). Going to our device with lower resolution and bigger screen seems like a lot of work. It would be much easier I think to get the android 5.0 SDK images and build aosp from source or wait on cm-12
mattwheat said:
Its easier to port g3 Roms to g2 due to all the the screen size (res folders). Going to our device with lower resolution and bigger screen seems like a lot of work. It would be much easier I think to get the android 5.0 SDK images and build aosp from source or wait on cm-12
Click to expand...
Click to collapse
Cool sounds like a good place to start but even if we do build a asop ROM wouldn't we need a base to get everything working
I'm not sure if it's just a D415/410/405 thing or if it's a KitKat to Lollipop thing. I'm not new to rooting, flashing, and customizing, but I'm in no way a dev either, so I was wondering why so many ROMs for our phone need a KK baseband? Alternatively, if I'm already on a debloated but otherwise stock LP ROM do I need to downgrade to the KK baseband first or can I flash over?
Note: the last time I was playing around with flashing ROMs was on a Galaxy Exhibit II 4G and I bumped it up from 2.3.6 to 4.4.2 without having to play with basebands. This is why the confusion.
Thanks in advance for any advice and answers.
I guess because no one really is maintaining LG L90 device sources.
For a log time there was Quarx but his device got broken so he's not really developing it anymore. He's only compiling CM12.1 from sources but I'm pretty sure it's all done by computer, fully automatically. After Quarx there was BigMajster who if I'm not wrong was the first one to introduced L90 owners to Lollipop. He was a great bug-hunter and he published a lot of great fixes for different L90 variants. If I'm not mistaken he was the one who fixed Double-tap-to-wake feature and storage 190MB bug for D415. He was a great developer until he disappeared somewhere in January I think. One day he was gone without saying anything. For some time I thought that something happened to him but after a little research I found out his real name and that he's pretty much alive and well. I didn't contact him though. I thought that if he left the way he did there was no point.
Other developers (I will not mention any names) are no really maintaining device sources. Most of them are just busy with their ROMs they are developing. The same bugs are present in all customROMs and no one is working to fix them. After months there is still no stable kernel for custom Lollipop, even though almost all of the current developing projects are based on Lollipop. Getting developers to work together, also didn't worked out. I probably forgot about some others important developers that are not with us anymore so sorry if I skipped anyone.
To be exactly clear. I don't make any accusations nor complaining. I just share my opinion with you, saying how I see things around here. I tried to state only facts, without my personal opinions but you should consider this whole statement as one.
A well thought out and thorough answer. Thank you for that. Any input on if I can flash from a stock LP base band or would I have to downgrade? That's about the only thing that makes me nervous and preventing me from trying 5.1.1 despite the random FCs
If you're on stock Lollipop and want to try CustomROM. Then you will have to downgrade to KitKat using KDZ or install bootstack.
Sent from my LG-D405 using XDA Free mobile app
@Xemidra
Keep in mind that NOONE of you pays us. You have no idea what we're doing on the source.
Quarx started with the device tree, kernel and vendor, so we don't know all what he did and how he did. We are working all or going to school(?), so we don't have so much time to rebase everything.
Also porting a Lollipop kernel from LGE source needs plenty much time.
In addition there is no "General source" to work on and maintain. All in all it's pretty cheeky to say something like we're doing nothing.
GrinningFerret said:
@Xemidra
Keep in mind that NOONE of you pays us. You have no idea what we're doing on the source.
Quarx started with the device tree, kernel and vendor, so we don't know all what he did and how he did. We are working all or going to school(?), so we don't have so much time to rebase everything.
Also porting a Lollipop kernel from LGE source needs plenty much time.
In addition there is no "General source" to work on and maintain. All in all it's pretty cheeky to say something like we're doing nothing.
Click to expand...
Click to collapse
Well, like I said it's was my opinion. That's how I see things around here.
I didn't mean any disrespect. I know that you don't get paid for your work so I don't have any right demanding anything from you and I don't but you also can't say that the current situation is a result of devs not getting paid.
I also put some work time into L90. I did made available all KDZ for Lollipop and some for KitKat. I made different versions of BOOTSTACKs and I made FlashableSTOCK. All that take a lot of my time, energy and also my internet connection, power supply etc. No one paid me for it. I basically paid for it from my own pocket. I'm not complaining. It's just how it is.
You can't get mad because someone did something not the way you wanted him to do while he did it for free.
At the same time you can't be mad at the current situation and say it's because someone didn't pay you to make it better.
That's my opinion.
@Xemidra
The problem isn't that we don't get paid for it - its' our hobby. But the point is that you're telling around that we do nothing on the device source, which is just wrong.
GrinningFerret said:
@Xemidra
The problem isn't that we don't get paid for it - its' our hobby. But the point is that you're telling around that we do nothing on the device source, which is just wrong.
Click to expand...
Click to collapse
I might have been wrong about the input in device sources.
Good you've stepped up and corrected me.
Sorry for the misunderstanding.
@Xemidra
Nevermind.
Sorry if this ruffled any feathers, guys. This was meant more to be an end user wanting to understand the dev and background process to be able to contribute and help more than a spirited discussion about who does what.
In any case, I thank you both for the information and the input. In the end I do understand a bit more.