Root Why oh why?

[bfldworker]

Before I start I must say I am NOT trying to be a dick.
Besides the fact that the people doing this are not getting paid.
And besides the fact that it isn't easy.
And besides the fact that this isn't a top of the line phone. I do have a question.

With the exception of the one JB ROM being made for this phone why are the only custom ROMs bring made for this phone all GB based?

While IMHO GB is a damn good release of Android when compared to the previous versions (DUH!),
would it not make sense to put the collective energies behind releasing a JB (4.1 or 4.2) ROM? More app availability, up to date security and features and while it isn't uber important, less fragmentation. I know I am not the only one thinking this. And before anyone flames it. I know it isn't easy, but it sure as hell isn't impossible. Just asking.

 

[Phrant1c]

Before I start I must say I am NOT trying to be a dick.
Besides the fact that the people doing this are not getting paid.
And besides the fact that it isn't easy.
And besides the fact that this isn't a top of the line phone. I do have a question.

With the exception of the one JB ROM being made for this phone why are the only custom ROMs bring made for this phone all GB based?

While IMHO GB is a damn good release of Android when compared to the previous versions (DUH!),
would it not make sense to put the collective energies behind releasing a JB (4.1 or 4.2) ROM? More app availability, up to date security and features and while it isn't uber important, less fragmentation. I know I am not the only one thinking this. And before anyone flames it. I know it isn't easy, but it sure as hell isn't impossible. Just asking.

There has been a large collective working on jb and ics based roms. The roms, as you can see by aokp and the cm variants, is not the problem. The giant hurdle holding us back is the 3.0.8 kernel. In building for the marquee some serious usb issues were discovered. This is the main thing holding us back since with no usb it is near impossible to compile and test since there is no adb or log pulling to see what issues remain or where the code is faulting.

Tdm recently finished up some things he was working on and made a rather significant accomplishment and advised he would be taking another look at the newer kernel in the coming days.

The current builds are based on the gb kernel. This works, but is rather limiting as many of the new features and smoothness stem from the kernel. If you look at the kernel repository, 2.x.x and 3.x.x are two entirely different animals.

Hopefully this shed some light on your question. In time, I'm almost positive we will see this kernel fixed and solid cm/aokp build in all its glory.

Sent from my LG-LG855 using Tapatalk 2

 

[Bloodawn]

because LG never released ICS or JB for this phone to use as a base, thats why. all the GB roms we have are stock based which means the prebuilt rom that comes on the phone was pulled off of it and modified, and that is a lot easier to do than build a JB rom from source that actually works. and tdm's rom's would probably be fully working right now if someone could of got USB working on the 3.0.8 kernel, but that didn't go well last time we tried.

 

[bfldworker]

because LG never released ICS or JB for this phone to use as a base, thats why. all the GB roms we have are stock based which means the prebuilt rom that comes on the phone was pulled off of it and modified, and that is a lot easier to do than build a JB rom from source that actually works. and tdm's rom's would probably be fully working right now if someone could of got USB working on the 3.0.8 kernel, but that didn't go well last time we tried.

What about the LG Optimus black? I know the kernel isn't 100% compatible, owning to the fact it is GSM and the partitioning is different. Would looking at that for inspiration and clues help?

 

[The~Skater~187]

What about the LG Optimus black? I know the kernel isn't 100% compatible, owning to the fact it is GSM and the partitioning is different. Would looking at that for inspiration and clues help?

I'm pretty sure that was the one that the USB didn't work on. I could be wrong though.

 

[Phrant1c]

I'm pretty sure that was the one that the USB didn't work on. I could be wrong though.

At this point I believe Tdm has gathered all the sources he can. This kernel was never officially released for the marquee so there is no clean source. The only way to break through this is either LG releases an official update to ics and the 3.0.8 kernel, or Tdm and co. keep hacking away at it and try to get lucky with some debugging code to see if they can see what's causing the fault. Beyond that, I'm pretty sure all outside sources have been tapped. With blood and Tdm both working on this I find it hard to believe they overlooked something as simple as an Optimus black repository

If I'm not mistaken, I think we even had some guys try to reach out to LG. Without official release, it's up to guys with serious coding knowledge to hack up their own lines of code. Like a mensa version of fill in the blank.

I still have faith in the project. The man just got accepted to the aokp team, and they don't just let everyone on the team. It's not gym class. I think the guy has proven if anyone can get this working, he can. Let's let the man work and show some patience

Sent from my LG-LG855 using Tapatalk 2

 

[bfldworker]

At this point I believe Tdm has gathered all the sources he can. This kernel was never officially released for the marquee so there is no clean source. The only way to break through this is either LG releases an official update to ics and the 3.0.8 kernel, or Tdm and co. keep hacking away at it and try to get lucky with some debugging code to see if they can see what's causing the fault. Beyond that, I'm pretty sure all outside sources have been tapped. With blood and Tdm both working on this I find it hard to believe they overlooked something as simple as an Optimus black repository

If I'm not mistaken, I think we even had some guys try to reach out to LG. Without official release, it's up to guys with serious coding knowledge to hack up their own lines of code. Like a mensa version of fill in the blank.

I still have faith in the project. The man just got accepted to the aokp team, and they don't just let everyone on the team. It's not gym class. I think the guy has proven if anyone can get this working, he can. Let's let the man work and show some patience

Sent from my LG-LG855 using Tapatalk 2

The one thing I wish Google took a cue from was Microsoft and Apple. At least with their phones everything is standardized. I can't help but to wonder (and correct me if I am wrong) if looking at other phones with same hardware if that would help, for example if a samsung phone had the same camera use that part of the kernel for the camera, if a Huawei phone has the same Radio's use that part of the kernel, and so on an so forth. I know it isn't that simple, but at this point I would try anything.

 

[dishe]

Not to veer off topic, but do you remember what the Marquee was like at release? Before custom roms "fixed" the laggy and frustrating performance and made it a solid offering?

I'm wondering what it is about the newer OS versions you are vying for? Is there anything GB didn't do well enough that made you say "gosh, if only I had ICS". I'm not asking to be a jerk, just wondering if I'm missing the motivation here.

To shed some light on my perspective, I've been mucking about with a cheap Tablet for a couple of years now (Viewsonic G-tablet) that shipped with a Froyo and a front facing camera. I originally wanted to run Skype on it, but Skype didn't support video calling on Android back then. Then it came out, but only using the new standardized camera API, which was released with Gingerbread. Thankfully, they had released a community-based GB rom, so I tried it out. But the performance was so laggy and awful due to display drivers that were incompatible with the newer Kernel, so after trying a few I went back to Froyo. Eventually, a device with nearly the identical hardware got an ICS update, and the community was able to port a smooth and fluid ICS for the G-tablet. Full hardware acceleration and everything, but it had to skip a generation or two of OSes. The problem? ICS wasn't compatible with the G-tablet camera, so the one thing I wanted to do (run skype with the camera) was out of the question.
By then, Skype had updated its app to use some cameras on Froyo devices. So I switched to a Froyo based rom that had full acceleration and 100% hardware support, and have left it on ever since. The point of this story is that I've been burned mucking about with unsupported OS updates. Sometimes we are asking for more trouble than it is worth. Unlike Froyo which brought JIT and Flash support, or GB which brought more standard hardware APIs, there isn't anything (at least to me personally) so compelling about ICS/JB that I'm willing to push my Marquee to invite new problems I didn't have before.

My 2 cents- I can't speak for anyone else and I may be the only one who feels this way. But since you asked "why oh why", I'm sharing my opinion.

 

[sniperruff]

there isn't anything (at least to me personally) so compelling about ICS/JB that I'm willing to push my Marquee to invite new problems I didn't have before.

Amen. I think with BD's CT Mod ROM (3.68 here) the Marquee is a significant improvement over stock, with the exception of camera button errors (just press the camera button again to fix) and the broken flashlight (just install a flashlight app). Other than that, everything works fine, and these drawbacks are not significant enough that I'd wipe + reinstall even if a new ROM will fix both of these shortcomings.