Related
My own Project was already in the works for another TEAM:
http://www.aedesign.cn/bbs/forumdisplay.php?fid=6
DOWNLOAD of THEIR work:
http://u.115.com/file/bh5z76gp#AED_Legend_5.0.0.RC3_exp.zip
good to see
Good to see someone else to make something new for the legend comunity. Keep going!
By the way, what is your ROM base? The video is too blury...
ogo2 said:
Good to see someone else to make something new for the legend comunity. Keep going!
By the way, what is your ROM base? The video is too blury...
Click to expand...
Click to collapse
I would say this rom:
http://www.aedesign.cn/bbs/viewthread.php?tid=316&extra=page=1
Looks cool, looking forward to this rom. Gj so far
Sent from my Legend using XDA App
I am glad as well to see someone else step up to the plate. I think this will give the CyanogenMod developers some more motivation to make a stable release.
LiViD said:
I am glad as well to see someone else step up to the place. I think this will give the CyanogenMod developers some more motivation to make a stable release.
Click to expand...
Click to collapse
Yeah, I know we are idiots. All of our releases have been unstable, full of bugs and missing nearly every feature one could wish for. Please excuse us, but we really can't do any better. The fact that all ROMs that are not based off RUUs are CyanogenMod rip-offs should clearly tell you that we just can't get anything right at all.
Very MIUI like.. Looks pretty much like my new Desire... Great job seeing similar running on the Legend..
Sent from my HTC Desire using XDA Premium App
great job!
LiViD said:
I am glad as well to see someone else step up to the plate. I think this will give the CyanogenMod developers some more motivation to make a stable release.
Click to expand...
Click to collapse
i suggust u say sorry for your arrogance to the CyanogenMod tea
btw awsome work!
dilip007 said:
i suggust u say sorry for your arrogance to the CyanogenMod tea
btw awsome work!
Click to expand...
Click to collapse
You guys don't pay attention to the experimental thread do you? Seriously, over 160 attempts at a nightly build and still nothing that performs up to par with ogo2's 2.3.3 Sense UI ROM. Sure his is lacking WiFi AP functionality, but I can live with that.
I love how you call everyone elses' ROM a rip-off of a CM ROM. Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
LiViD said:
You guys don't pay attention to the experimental thread do you? Seriously, over 160 attempts at a nightly build and still nothing that performs up to par with ogo2's 2.3.3 Sense UI ROM. Sure his is lacking WiFi AP functionality, but I can live with that.
I love how you call everyone elses' ROM a rip-off of a CM ROM. Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
Click to expand...
Click to collapse
Damn.. Where have you lived your life? 2 versions of stable ROMS is what we have.. original from HTC is 1 - CM is 2.. All roms worth mention is variations of one of those.. (for Legend that is)
Sent from my HTC Desire using XDA Premium App
LiViD said:
I love how you call everyone elses' ROM a rip-off of a CM ROM.
Click to expand...
Click to collapse
I know I'm wasting my time here and I really don't care anyway.
Still I think I have to clarify that I'm not talking about people using some "builds". I'm talking about the source code.
If you want to build a ROM for the Legend (and nearly every other device out there) you've got two choices: Push some files from official releases (RUUs) around and zip them, or compile from source.
As a matter of fact there's no project out there that releases working source code (for anything but Google's official devices) except for CyanogenMod.
Video encoding or decoding? msm* support? Backported code for ancient libcamera, libril and framework support for said ancient libraries? GPS backport or implementation? Kernel backports for Gingerbread? Yeah, good luck finding that somewhere else (no, I don't mean the CAF repositories where we are copying from and giving credit of course).
LiViD said:
Get a life guys, no one would attempt to use your builds unless said person was extremely lazy.
Click to expand...
Click to collapse
"Get a life"? Come on, don't be ridiculous.
MD5-sums can be quite revealing by the way. Or boot messages (like "Welcome to CyanogeMod" in MIUI). Some people were even charging for shady rip-offs – that's why the CM team ultimately decided to close down development and switch to "release when it's done".
LiViD said:
Seriously, over 160 attempts at a nightly build...
Click to expand...
Click to collapse
Sorry, but you didn't understand the concept of a nightly build? There are no "attempts at a nightly build" and they are not even meant for users. Nightly builds are there to see if current code in the repositories still compiles. Nothing else.
whitetigerdk said:
All roms worth mention is variations of one of those.. (for Legend that is)
Click to expand...
Click to collapse
Unfortunately not only for the Legend but for most other devices too.
Android was said to be open but in fact it's just proprietary crap again. No developer wants to spend months doing the work of forty CM devs, so they either join CM – or sometimes steal their work declaring it as their own – or use (or combine) binaries from official releases.
If you didn't care, you would be in other developers threads attacking their attempts at making something that just may work better than what you're pushing out.
Face the facts; People want more choices other than CM. I am willing to admit that CM 6.1 was a damn good ROM when it came out, but I can't for life of me figure out why you guys can't live up to the same expectations with CM7.
I have been testing the NewSense 1.0 RC's (HTC Salsa ROM) for some time, and I as I said; Without the lack of AP support, it works well and does not have the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
ali ba said:
Unfortunately not only for the Legend but for most other devices too.
Android was said to be open but in fact it's just proprietary crap again. No developer wants to spend months doing the work of forty CM devs, so they either join CM – or sometimes steal their work declaring it as their own – or use (or combine) binaries from official releases.
Click to expand...
Click to collapse
Oh Sorry.. Didn't know much of other devices.. Recently bought the Desire and currently using MIUI. Must admit that I believed the MIUI to be a completely rewrite of the Android framework..
Sent from my HTC Desire using XDA Premium App
LiViD said:
I have been testing the NewSense 1.0 RC's (HTC Salsa ROM) for some time, and I as I said; Without the lack of AP support, it works well and does not have the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
Click to expand...
Click to collapse
You can thanks for that to HTC, because i haven't written a single line of code in NewSense. Only some crappy hacks.
Really, our community is too small and we have a lack of devs, but that's not all. HTC provide to us just ****ty sources. It just sucks!
Btw: this rom here is based on cm7...
Edit: I commented on the wrong ROM. My bad.
I still think Blayo's rom's are the best for Legend!
Been using them for quite a while and I never have had any complain!
whitetigerdk said:
Must admit that I believed the MIUI to be a completely rewrite of the Android framework..
Click to expand...
Click to collapse
Their earlier releases certainly used CM sources with modified framework and apps. I don't know what they are doing now – but as they don't release their sources I can accuse them of using modified CM source code as much as I want without ever being able to prove it so I refrain from doing that.
If you are interested, the UltimateDroid soap opera is a good read by the way.
ogo2 said:
You can thanks for that to HTC, because i haven't written a single line of code in NewSense. Only some crappy hacks.
Click to expand...
Click to collapse
That doesn't make your work worth less than anyone else's and certainly not "crappy".
ogo2 said:
HTC provide to us just ****ty sources.
Click to expand...
Click to collapse
I'd be happy if they provided the real sources for the binaries they are releasing but as a matter of fact HTC continuously violates the GPL and we can't do anything about that.
LiViD said:
If you didn't care, you would be in other developers threads attacking their attempts at making something that just may work better than what you're pushing out.
Click to expand...
Click to collapse
Where exactly did I attack emiliano7's work? I'm actually very glad that someone is developing for the Legend and I never stated anything else.
You obviously on the other hand couldn't resist showing your arrogant attitude by addressing the CM team in this thread making false accusations. You can't take a discussion off-topic and then blame others for taking the same train.
LiViD said:
...the crash prone problems that I have seen with 7.0.3, and 7.1 RC1.
Click to expand...
Click to collapse
Instead of making vague accusations you could have filed bug reports a long time ago. CM is a community project and nothing without its community.
It sometimes still makes me sad that for some people whining doesn't seem to be a problem but as soon as it comes to writing a good bug report they come up with various excuses.
Galaxy s2 and s3 have all put their hands on the new 4.1.2 beta, waiting anxiously now for my i9305 international version. anyone has update on this? :fingers-crossed:
Doubt this will happen, they are just too different from what I remember in prior discussions.
We should have something pretty soon for our phones tbh.
On another note, I have been using it on my 9300 for a few days and it seems a great improvent, it is good on battery, there are lots of little improvements including the Samsung Keyboard where the word appears automatically as you type. Multi WIndow is great although not sure how much I will use it, still it is there if I want it!
Really looking forward to 4.1.2 coming over to the 9305.
I have played around with it. The only issue I am having is with the baseband and imei not being detected. Have tried a few things to fix it but am stuck at the moment with what else to try. Other than that it boots, has root and everything else works.
Sent from my GT-I9305 using XDA Premium HD app
txr33 said:
I have played around with it. The only issue I am having is with the baseband and imei not being detected. Have tried a few things to fix it but am stuck at the moment with what else to try. Other than that it boots, has root and everything else works.
Sent from my GT-I9305 using XDA Premium HD app
Click to expand...
Click to collapse
Chiming in here to say that I have been working on this too. But you knew that from our discussions via PM.
I am wondering if we might be able to get the ball rolling further on this for our devices. There are considerable differences between these devices but that shouldn't stop us.:fingers-crossed:
On another note I am thinking the AOSP is the secret to bringing more popularity to this device seems alot of people are waiting for this and keep asking for this,,, So i am thinking of porting an AOSP rom for fun and chucking it in for a variety
mmm not sure about that, I think the new 4.1.2 features outweigh a AOSP release; MultiWindow probably beign the biggest so as soon as 4.1.2 hits here I think there will be some very happy people.
Personally, I use lots of the other features like Allshare Cast, Dual View etc... which I believe (not positive though) would be lost with an AOSP build.
Still happy to try it out is you manage to port it over!
yes i would not use the AOSP but CM has a MASSIVE fan base and so does AOSP... But I agree with you 4.1.2 is much better but even this version has now been merged with AOSP in the i9300 forum lool we need more devs here its too hard to keep up with little help
Devs or no Devs i am still very happy with this device and would not swap it back with the one i had before, which i gave to my mother as a gift But yehh If i really wanted too i can swap it .. But no thanks
In the fall of year 2012. LG has finally released long awaited Ice Cream Sandwich update for it's former flagship, Optimus 2x. Short after, young warrior named wkpark cracked the new, locked ICS bootloader for this device. That is the day when Bootloader Wars begun. Lot of Optimus 2x users were eager to see that if LG made a proper job with it's official ICS. First custom stock ICS roms begun to emerging, and more and more users were converting on new, unlocked bootloader.
In meanwhile, developers on the old, GB bootloader didn't fell asleep. Official CM10 came out, there were even few attempts to bring stock ICS to old bootloader. But all ICS and JB roms on old bootloader had a critical flaw named 'call bug'. Because of that bug, even more users started using new instead old bootloader. But all of those who wanted to taste Jelly Bean on O2x were forced to stay on old bootloader. O2x community was separated in two fractions: ones that uses new bootloader, and the other that uses old one.
After some time in stalemate position, things have started to develop further. One member from notorious group The Penguins of Madagascar, pengus77 succeeded to boot up CM10 on the new bootloader. With it's brilliance, he brought the advantage on the new bootloader side. That impact cause a massive troops crossing towards new bootloader.
Another inversion occurred when marsgod fixed the infamous call bug on the old bootloader. It gave the new light for old bootloader users and developers. So, one can say that we're again in stalemate position. Which side will be victorious? No one can and won't predict... only time will tell.
DISCLAIMER: All characters appearing in this work are fictitious. Any resemblance to real persons, living or dead, is purely coincidental.
I hope no one will bi offended with little war story I wrote above. If someone find it offending, or wants that I remove his nickname from it, feel free to PM me.
Point of this thread would be to see how much users are on new bootloader, and how much of them uses old one. I'll make poll about that. Also, I would like to hear why someone choose the one bootloader or the other? What are advantages over the other in your opinion? And are you ready to change bootloader again if the community will choose one way...
Also, since this is bootloader thread, I hope that people will stop spamming threads in developers subforum with posts such as: my bootloader is stronger than yours etc.
Let the battles begin! And please, don't start to offend other users because of their bootloader choice. Let's keep it nice and cosy.
And sorry if my english is not good enough, and some sentences sounds funny.
I am currently on new bootloader, but as soon as cm10 without wifi drain is available, I'll switch back to good ol' bootloader
Sent from my LG-P990 using xda app-developers app
I'm on the new bootloader since stefan's v28E stock ICS. I'm happy with it, especially after pengus77 managed to get CM10 working on new BL. Currently using tonyP's PA with penguses kernel. I think it's nice combo.
About old bootloader... there isn't any stock ICS which is a minus. Official CM10.1 is still to buggy for me to use it as daily driver. CM7 (for stability and speed) is the only thing that would make me go back to old bootloader, and somehow I don't want to go back to GB. And CM10 on new BL seems to be enough stable and fast.
But if (when) one day CM10.1 become stable, and if whole community starts to roll back, I wouldn't mind another BL change.
I prefer to be with the new bootloader, because there are many ROMS that are becoming the new BL.
Greetings.
I dont even understand why people ***** about not have old bootloader version, why bother fixing all the issues with the old one when the new one works, its just they are too lazy to flash the new bootloader. The new bootloader is there for a reason.
Base on the same source new bootloader i don't have slow charge issue at least in mine case. Old bootloader the charging are endless hall for me.
orbital_71 said:
Base on the same source new bootloader i don't have slow charge issue at least in mine case. Old bootloader the charging are endless hall for me.
Click to expand...
Click to collapse
I have been on the old bootloader and charging is absolutely fine since over a month. I will stick with RC and official CM, who else can give us daily bug fixes besides cyanogenmod. As for device apecific bugs, I am sure we will have kernel fkx by pengus.
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
kestrelv2 said:
I dont even understand why people ***** about not have old bootloader version, why bother fixing all the issues with the old one when the new one works, its just they are too lazy to flash the new bootloader. The new bootloader is there for a reason.
Click to expand...
Click to collapse
Exactly my point, why move to a new BL when I am going to run CM 10 only which is only officially supported on the old BL.
Another thread about that?
This will lead into an android vs apple fight, where the loudest people are the ones with the lowest knowledge about what they're talking about.
Fact is: Both bootloaders don't suffer from the callbug and can be considered totally stable for a daily use.
Some people have a slow charging bug with the old one - I for myself never suffered from that with my Nexus 7 charging cable - so try not to use a cheap usb cable.
So choose whatever you want for whatever reason you like and stop telling others what they should do.
AW: Bootloader Wars
I am on new bootloader because of penugs. But actually who really cares? Changing bl is thanks to the AIO really easy. So my decision is not about the bl but the roms. I will choose the roms I am interested in and if I have to change the bl again it doesn't matter. I think this discussion about bl is nonsense.
Gesendet von meinem Transformer TF101 mit Tapatalk 2
Great write up, well done :thumbup:
Sent from my LG-P990 using Tapatalk 2
I don't see point to move to new bootloader.
I am on tonyp's PA, pengus Kernel, and everything is working, no slow charging etc.
Also on CM10 everything was ok.
im on new BL:fingers-crossed:
Pascalwb said:
I don't see point to move to new bootloader.
I am on tonyp's PA, pengus Kernel, and everything is working, no slow charging etc.
Also on CM10 everything was ok.
Click to expand...
Click to collapse
Really? I shall try that one then! Because official CM10.1 is buggy as hell lately... I've been getting SoD's, which I never had, gTalk video is dead (even though apparently there's a flashable zip to correct that), I've had the charge bug (with an original blackberry charger... so I don't think it qualifies as cheap crap usb cable), the phone feels laggier than normal, voice recognition fails miserably... the list goes on...
those reporting about "slow charging" bug, need to know if you charging with screen ON or OFF. i am on old bl and with screen on via usb connected to the pc, slow charging (15%hour) but maybe cause screen is on with autobrightness. with screen off i can get 25%hor, so i do not think it can be considered "slow charging"....could any more confirm this "slow charging" bug or just "screen on with charging" bug?
LarsPT said:
Really? I shall try that one then! Because official CM10.1 is buggy as hell lately... I've been getting SoD's, which I never had, gTalk video is dead (even though apparently there's a flashable zip to correct that), I've had the charge bug (with an original blackberry charger... so I don't think it qualifies as cheap crap usb cable), the phone feels laggier than normal, voice recognition fails miserably... the list goes on...
Click to expand...
Click to collapse
Yop, I tried CM10.1 too before PA, it wasn't smooth like CM10 or PA and other roms, I think it's too soon.
I had slow charging with earlier CM10 builds with SU660 source codes, but it was only on one build.
Pascalwb said:
I don't see point to move to new bootloader.
I am on tonyp's PA, pengus Kernel, and everything is working, no slow charging etc.
Also on CM10 everything was ok.
Click to expand...
Click to collapse
I remember seeing a post from pengus77 with an interesting point:
http://forum.xda-developers.com/showthread.php?p=36824970#post36824970
The work of rc / the whole group behind CM is beyond great... but I cannot help but wonder the future is somewhere else than old bl...
I'm on a new bootloader, but I prefer, cm roms, but cm10 and cm10.1 is fine with new bl.
I belive, old bl, is OK for thistime, I just want a newer cmw, and newer bl
tygryss said:
I just want a newer cmw, and newer bl
Click to expand...
Click to collapse
just because "new" automatically means "better"... am i right?
Most of the time it is better but also restrictive
Sent from my LG-P990 using xda app-developers app
I'm running cm10 on boot loader with WiFi conserving kernel. Not totally as stable as cm.2 but its getting there.
Since Lg updated the o4x to 4.1.2, wouldn't it be great to have this modded Into cm and make a final release with everything working, I've been trying so many roms but non exceed stock reliability, I think that a port from stock to cm based with everything working would be great for all users, truth I don't care about android version, but cm experience is great. Maybe instead of working on forever bugged ROMs with no official android release, try using the base of what lg has released and make a rock solid ROM featuring cm experience.
Just my thoughts,
Sent from my LG-P880 using xda app-developers app
leortez said:
Since Lg updated the o4x to 4.1.2, wouldn't it be great to have this modded Into cm and make a final release with everything working, I've been trying so many roms but non exceed stock reliability, I think that a port from stock to cm based with everything working would be great for all users, truth I don't care about android version, but cm experience is great. Maybe instead of working on forever bugged ROMs with no official android release, try using the base of what lg has released and make a rock solid ROM featuring cm experience.
Just my thoughts,
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
In My opinion roms are not "forever bugged"; what one dev, or a team of devs do with a custom rom is... customising.
What you are asking for is steadyness, immobility, what devs do is pushing the limit of knowledge a step further and develop something new that did not exist before under the form in which it is now.
In addition, custom roms are made also to compensate the lacking of development from the original manufacturer. LG supoorted the development of their firmware up to ver 1.2, custom roms are 4.2.2, o 4.3 already and take advantage of many powerful feature in our device that could be better used if the device would not be abandoned by the manufacturer.
Mind that i am not against the fact that phones are forgotten by their manufacturer one o two years after they have been presented, it is a market law... still, with custom roms we can enjoy our highly priced toys for many, many years and, yes, have a lot of fun with them. Sometimes roms are buggy, it is true, but i believe that if one is here, in this forum, it should be to contribute to make things better, and not for complaining about (free) buggy roms.
In addition, CM needs very few contribution from LG base, as it is AOSP based, that is, pure Android, with no fancy UI and bloatware, and current official stable version 10.1.3 (corresponding to Android 4.2.2) is rock solid, or at least, not more buggy than LG 4.1.2.
I dont question development, im a cm and custom kernels fan myself, but what I mean is that there are no significant differences between the jellybean versions, 4.1.2 is quite good in my opinion, and I'm not complaining either, but I have not seen a cm implementation based on 4.1.2. Thing is that for this phone there is a critical bug that many people can't stand independent from performance or how beautiful, etc. Which is present in both 4.2.2 and 4.3 And that is baseband being very unstable. I keep rebooting my phone 2-3 times a day to get back signal and data.Tested with all kernels. Which I believe this is not a kernel related problem. So I think that if we use cm 4.1.2 this issue could be solved.
By no means I discard the efforts that Devs. Have put into this phone, I'm just giving an idea that could be worth taking in consideration.
Sent from my LG-P880 using xda app-developers app
Try SlimBean latest demetris build.Or zaiben rom.I get great battery life with both of them and almoust none baseband wakelock.Even if it is there it doesnt reflect on battery life that much anymore.
Sent from my big and white LG refrigerator
Ottonet said:
In My opinion roms are not "forever bugged"; what one dev, or a team of devs do with a custom rom is... customising.
What you are asking for is steadyness, immobility, what devs do is pushing the limit of knowledge a step further and develop something new that did not exist before under the form in which it is now.
In addition, custom roms are made also to compensate the lacking of development from the original manufacturer. LG supoorted the development of their firmware up to ver 1.2, custom roms are 4.2.2, o 4.3 already and take advantage of many powerful feature in our device that could be better used if the device would not be abandoned by the manufacturer.
Mind that i am not against the fact that phones are forgotten by their manufacturer one o two years after they have been presented, it is a market law... still, with custom roms we can enjoy our highly priced toys for many, many years and, yes, have a lot of fun with them. Sometimes roms are buggy, it is true, but i believe that if one is here, in this forum, it should be to contribute to make things better, and not for complaining about (free) buggy roms.
In addition, CM needs very few contribution from LG base, as it is AOSP based, that is, pure Android, with no fancy UI and bloatware, and current official stable version 10.1.3 (corresponding to Android 4.2.2) is rock solid, or at least, not more buggy than LG 4.1.2.
Click to expand...
Click to collapse
Nothing is ever as stable as Stock. And with Root, you can remove bloatware, with xposed you can change the ui etc. etc.
leortez said:
I dont question development, im a cm and custom kernels fan myself, but what I mean is that there are no significant differences between the jellybean versions, 4.1.2 is quite good in my opinion, and I'm not complaining either, but I have not seen a cm implementation based on 4.1.2. Thing is that for this phone there is a critical bug that many people can't stand independent from performance or how beautiful, etc. Which is present in both 4.2.2 and 4.3 And that is baseband being very unstable. I keep rebooting my phone 2-3 times a day to get back signal and data.Tested with all kernels. Which I believe this is not a kernel related problem. So I think that if we use cm 4.1.2 this issue could be solved.
By no means I discard the efforts that Devs. Have put into this phone, I'm just giving an idea that could be worth taking in consideration.
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
You are right, if we built CM9 (ICS) or CM10 (JB4.1.2) these would probably be better on the battery, and with official drivers etc, it would be stable. (in theory)
dimi89 said:
Try SlimBean latest demetris build.Or zaiben rom.I get great battery life with both of them and almoust none baseband wakelock.Even if it is there it doesnt reflect on battery life that much anymore.
Sent from my big and white LG refrigerator
Click to expand...
Click to collapse
He is asking about CM10, in all honesty, CM10.1 is just an improved CM10, there are not many differences in all honesty.. It is obsolete now anyways, so 4.4 is going to be prioritized, CM10.1 and above have more to offer, i don't think CM10 will ever be developed for our device, it is too old now.
penguin449 said:
Nothing is ever as stable as Stock. And with Root, you can remove bloatware, with xposed you can change the ui etc. etc.
Well, CM10.1 is rock stable. Never had a random reboot, and trust me, I was tetsing my kernel on it pretty heavily
You are right, if we built CM9 (ICS) or CM10 (JB4.1.2) these would probably be better on the battery, and with official drivers etc, it would be stable. (in theory)
You can't just take official drivers on CM. You might be able to do so on AOSP, but I'm pretty sure it won't have an effect. Actually I think it would make it even unstable
He is asking about CM10, in all honesty, CM10.1 is just an improved CM10, there are not many differences in all honesty.. It is obsolete now anyways, so 4.4 is going to be prioritized, CM10.1 and above have more to offer, i don't think CM10 will ever be developed for our device, it is too old now.
Click to expand...
Click to collapse
Well, If i happen to have some spare time (pretty unlikely though ATM), I might try to compile CM10, but you better do not expect it TBH
Not sure what TBH means but It would be great to give it a shot, hoping it will work better than the newer versions.
Sent from my LG-P880 using xda app-developers app
leortez said:
I dont question development, im a cm and custom kernels fan myself, but what I mean is that there are no significant differences between the jellybean versions, 4.1.2 is quite good in my opinion, and I'm not complaining either, but I have not seen a cm implementation based on 4.1.2. Thing is that for this phone there is a critical bug that many people can't stand independent from performance or how beautiful, etc. Which is present in both 4.2.2 and 4.3 And that is baseband being very unstable. I keep rebooting my phone 2-3 times a day to get back signal and data.Tested with all kernels. Which I believe this is not a kernel related problem. So I think that if we use cm 4.1.2 this issue could be solved.
By no means I discard the efforts that Devs. Have put into this phone, I'm just giving an idea that could be worth taking in consideration.
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
How do I reproduce these bugs?I dont seem to notice them.
leortez said:
I dont question development, im a cm and custom kernels fan myself, but what I mean is that there are no significant differences between the jellybean versions, 4.1.2 is quite good in my opinion, and I'm not complaining either, but I have not seen a cm implementation based on 4.1.2. Thing is that for this phone there is a critical bug that many people can't stand independent from performance or how beautiful, etc. Which is present in both 4.2.2 and 4.3 And that is baseband being very unstable. I keep rebooting my phone 2-3 times a day to get back signal and data.Tested with all kernels. Which I believe this is not a kernel related problem. So I think that if we use cm 4.1.2 this issue could be solved.
By no means I discard the efforts that Devs. Have put into this phone, I'm just giving an idea that could be worth taking in consideration.
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I had all those signal bugs, but in the latest nightly of 4.3.1 that bug is near to be solved, it still happens but less often than before, in the past since CM10 RC5 I suffered that annoying bug, and i stoped using CM based ROMS, the problem is not the kernel, the problem is the RIL programmed by CM developer team, and for lucky for us they have been worked on our problem, I passed of reboot my phone every 20 or 30 min to reboot once or none per day when the phone can't get signal again
Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off
MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know
Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot
{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD