Question here...
I know that the N7 3G and the N4 are not yet supported by AOSP due to GSM stack licensing issues.
Yet over in the N4 forum they already have AOSP based ROMs and now there are CM10.1 nightly builds. How are they getting that to work if the N4 isn't in AOSP yet?
And whatever they're doing, can the same be done with our N73G in order to make AOSP and CM possible?
Bump... still curious about this.
I'm waiting for it too. I'm considering to get a N7 3G but won't buy it until it has AOSP because I want CM/AOKP rom.
Right, I'm just perplexed as to how it is that AOSP ROMs are hitting the Nexus 4 without it being in AOSP at all, and yet the same isn't happening for the N73G.
Related
What are the differences between AOSP and GPe ROMs (that are noticeable). I know that the GPe is based off of the TW framework, but they look very similar otherwise. I'm trying to decide if I want to switch over to the 4.3 AOSP ROM posted a few days ago.
Thanks guys :beer:
Cheater912 said:
What are the differences between AOSP and GPe ROMs (that are noticeable). I know that the GPe is based off of the TW framework, but they look very similar otherwise. I'm trying to decide if I want to switch over to the 4.3 AOSP ROM posted a few days ago.
Thanks guys :beer:
Click to expand...
Click to collapse
I saw this on the Verizon forum for the 4.3 AOSP ROM
@Elvis_Marmaduke -
For those who are still having trouble getting it. GE is made by Samsung and is a Samsung"ROM" if you will. It's like touchwiz without all the bloat and custom menus and features. AOSP is from Google. Not specialized per phone nor do they have the closed Qualcomm drivers so you may not get as high benchmarks and stuff. But most real world performance they will be pretty similar.
Click to expand...
Click to collapse
@Dubbsy -
I thought I said it elsewhere. But anyway GoogleEdition is not AOSP. And AOSP is not GoogleEdition. I was following Brood's progress on a REAL aosp project. When be posted works in progress and his source I decided to play with it.
This is not meant to replace Google Edition 4.3. I'm still working on my Google Edition 4.3 port. It hasn't been friendly at all. B-d from Sprint has been having the same issues I am. Every time I have a "clearly this is the problem" moment... It's not the problem. At least not the main problem.
Comparing GE's 4.2.2 to 4.3 update and the effects to real AOSP it's like comparing cacti and puppies. Besides that, GE's 4.3 is older than this 4.3. JSS builds I've been reading have wake lock issues but while running it I've gotten nothing but amazing battery life
Click to expand...
Click to collapse
@Cruiserdude -
This is NOT Google Play Edition, this is actual AOSP. But yes, 4.2.2 GPe is heavily TW based, while 4.3 GPe is AOSP based with some TW on top. Dubbsy will have to fill you in on the specifics.
My guess is that the decision to offer a "stock" experience S4 happened fairly late in the development process, possibly to silence those rumors of a Google/Samsung rift that were going around a few months ago. Samsung would have already had access to early 4.3 code, so they wouldn't have wanted to build a new 4.2.2 rom from the ground up. So they likely just used an engineering build they had, that had all of the lower level TW stuff but without any of the actual features or themeing built in. Which is presumably what they'd use to develop their TW builds, so they can test features individually with the base they need, but not have so many variables as they track down bugs. Either way, they probably already had something like this laying around, that only needed minor tweaking to become the GPe software. That way they didn't waste effort on software that they'd be replacing after only a month or so, anyway.
That way they could focus right in on developing the 4.3 GPe software so it'd be ready for a prompt release. Which would explain why it's much more heavily based on AOSP, though still with enough TW built in for a few things like the Smart Cover to work. Not to mention it'll likely take them awhile to have a solid 4.3 TW base.
Note that all the above is pure speculation on my part, with the exception of the actual distinctions between versions that I mentioned.
Click to expand...
Click to collapse
I hope that helps!
I'd hold off on the 4.3 aosp until I get all the framework edits done if you need it to be a complete ROM. You'll have data but voice is messed up. telephony isn't setup properly for CDMA handoffs. Didn't notice it until someone pointed it out.
It's one heck of a smooth build though :good: Brood's doing a great job
How many times has there been multiple official builds for the same Android version? The JWR build pushed ota to our phones is much more stable than the JSS Roms. However for some reason AOSP supports the JSS build which also means everyone building Roms is also using JSS as a base. Sorry but "occasional" deadlocks and freezes is something isn't stable. Cataclysm is a JWR based ROM that works really well. Just wanted to see what else is out there.
Anyone else mystified why AOSP would support some broken build of 4.3 when a stable build of the same version is available?
Anyway, sorry to rant. I'll be happy when stock and AOSP are on the same page again. Come on 4.3.1!
If you read the thread regarding information about it, this wouldn't be needed..
Sent from my Nexus 4 using Tapatalk 4
Misledz said:
If you read the thread regarding information about it, this wouldn't be needed..
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I have read the thread. I felt the need to rant despite that somewhat informational thread. Aside from that I ask legitimate and pertinent questions. Apparently you cant answer them. Nice bloated sig:good:
there are constantly different builds for aosp, while stock stays the same until an official ota update. aosp is constantly getting stuff added/fixed, since the very beginning, with differing build numbers. the difference being this time there is a big difference(change) in the kernel and graphics.
simms22 said:
there are constantly different builds for aosp, while stock stays the same until an official ota update. aosp is constantly getting stuff added/fixed, since the very beginning, with differing build numbers. the difference being thus time there is a big difference in the kernel and graphics.
Click to expand...
Click to collapse
Hey thanks for the info. But usually stock and AOSP share the same build if I'm not mistaken. I personally can't recall a time when they didn't. Aside from that I can't grasp why AOSP would officially support a build known to be broken. The best developer in the world can't somehow fix a broken source. Also not sure what you mean by aosp being constantly updated and fixed? As a n4 user how could I reap the benefits of all these changes aside from waiting for an OTA update?
RealiZms said:
Hey thanks for the info. But usually stock and AOSP share the same build if I'm not mistaken. I personally can't recall a time when they didn't. Aside from that I can't grasp why AOSP would officially support a build known to be broken. The best developer in the world can't somehow fix a broken source. Also not sure what you mean by aosp being constantly updated and fixed? As a n4 user how could I reap the benefits of all these changes aside from waiting for an OTA update?
Click to expand...
Click to collapse
as soon as there is new code available, it gets dropped into aosp immediately(usually). lets say the build number is rtt234(made up), aosp can add a rtt234a, rtt234b, rtt234c.. just like it happened for 4.2.2. aosp supports the latest build, they dont go backward. just because something might not work right, i can and will get fixed. but, just so you know, aosp can get updated 10+ times before stock sees 1 update. anyways, the issue that you are talking about, the freeze in the keyboard, affects everyone a bit differently. some people havent had one freeze yet, others get it constantly and are very annoyed. it happens to me one or twice every 2-3 days, so it doesnt bother me at all.
simms22 said:
as soon as there is new code available, it gets dropped into aosp immediately(usually). lets say the build number is rtt234(made up), aosp can add a rtt234a, rtt234b, rtt234c.. just like it happened for 4.2.2. aosp supports the latest build, they dont go backward. just because something might not work right, i can and will get fixed. but, just so you know, aosp can get updated 10+ times before stock sees 1 update. anyways, the issue that you are talking about, the freeze in the keyboard, affects everyone a bit differently. some people havent had one freeze yet, others get it constantly and are very annoyed. it happens to me one or twice every 2-3 days, so it doesnt bother me at all.
Click to expand...
Click to collapse
My point is even though AOSP is updated constantly how does the user reap the benefits or update to the latest build if its not official? I'm pretty sure they can't. Pretty sure developers can only build from an official source. So AOSP updating constantly really is a nice idea however if updated builds aren't published why should I care?
RealiZms said:
How many times has there been multiple official builds for the same Android version? The JWR build pushed ota to our phones is much more stable than the JSS Roms. However for some reason AOSP supports the JSS build which also means everyone building Roms is also using JSS as a base. Sorry but "occasional" deadlocks and freezes is something isn't stable. Cataclysm is a JWR based ROM that works really well. Just wanted to see what else is out there.
Anyone else mystified why AOSP would support some broken build of 4.3 when a stable build of the same version is available?
Anyway, sorry to rant. I'll be happy when stock and AOSP are on the same page again. Come on 4.3.1!
Click to expand...
Click to collapse
JSS is a development branch. The reason why AOSP has multiple branches is because JSS has last minute fixes for The new Nexus 7. Google knew these changes broke other devices but didn't have time to fix them so they just gave other Nexus JWR. Most custom ROMs just supports JSS because it's the latest.
Sent from my Nexus 7 using Tapatalk 4
RealiZms said:
My point is even though AOSP is updated constantly how does the user reap the benefits or update to the latest build if its not official? I'm pretty sure they can't. Pretty sure developers can only build from an official source. So AOSP updating constantly really is a nice idea however if updated builds aren't published why should I care?
Click to expand...
Click to collapse
builds are published constantly. look at the development threads. for example, Rasbean jelly, an aosp ROM, gets built that day or the next, after a code drop. that's the beauty of running aosp builds. stock ROM users get updates only after an ota, while anyone can build from aosp whenever they feel like it.
simms22 said:
builds are published constantly. look at the development threads. for example, Rasbean jelly, an aosp ROM, gets built that day or the next, after a code drop. that's the beauty of running aosp builds. stock ROM users get updates only after an ota, while anyone can build from aosp whenever they feel like it.
Click to expand...
Click to collapse
Hey thanks for clarifying. I have been following both development threads. And the smoothest ROM I've tried is Cataclysm which is a JWR based ROM.
Does anyone else prefer source-built AOSP over CM? CM is nice, the forum over at the OG proved that true stock AOSP is smooth, functional and in every way as good as CM, AOKP and the rest.
I can see roms getting ported from the N5 but if it would be awesome if this phone could get some source-built AOSP like this, just to name one of many such roms for the LGOG http://forum.xda-developers.com/showthread.php?t=2455871
Of course, no rush. A big thanks to devs like djkinetic scrosler IO and Wacomalt who are giving the G2 new life!
An AOSP source built rom shouldn't be too difficult. If no one else picks up the project and I have some spare time, I will see what I can do.
teach me, if you have time
I cant get 4.2.2 ported to cm10.1 then upgraded to 10.2 so I cant port it to Omnirom(withmultiwindow mod lol)
Hi all,
i was going to buy a g2 but as i always do i wanted to know first what roms are available and how they run. Have been reading through xda and how well are kitkat roms running on the g2 ? I read that slim has troubles, is this a general issue or just rom related ? what about PA or others ?
I ussually get a new phone every 2 / 3 years so that i want to make sure to have up to date os until then.
TIA !
there are some minor problems with PA roms. Nothing serious though.
LG will be releasing kitkat in some time (a month?), so there will be more roms based on KK.
For now You could choose between PA, CM11 (and roms based on), some slim kitkats, and there are a lot of stock based roms and roms ported from G Flex. I would say not bad at all. Go and check it out in Development sub forums.
Stock rom is also not bad - sure it is loaded with some bloatware but better than Glaxy's for sure
q123456 said:
there are some minor problems with PA roms. Nothing serious though.
LG will be releasing kitkat in some time (a month?), so there will be more roms based on KK.
For now You could choose between PA, CM11 (and roms based on), some slim kitkats, and there are a lot of stock based roms and roms ported from G Flex. I would say not bad at all. Go and check it out in Development sub forums.
Stock rom is also not bad - sure it is loaded with some bloatware but better than Glaxy's for sure
Click to expand...
Click to collapse
thanks for your reply !
i had only a brief look to the stock ui but im sure im going to hate it. I dont have anything against LGs ui, im just used to aosp roms and like their simplicity.
My concern isnt just about kk but beyond, i mean, this year google will release 4.5 ( or whatever they will call it) and my guess is that LG wont make it available for the g2.
Does anyone know LGs policy about os updates ? How have they handled previous updates for example ?
TIA
LG policy about updates is non existent LG G for e.g. . They were saying that they will change their approach to updates but...
I also like AOSP very much - was using nexus 4 for a year. For now i would say You could use PA on daily basis. There are some minor bugs. Battery life for me was worse form what i got on stock, that's why i'm switched back.
Other than that no crashes, reboots etc. Dunno about games though - they were some voices that some of them crashing
Personally I've bounced back and forth between stock and 4.4 Roms. Right now really happy running stock with xposed installed and using g2 exposed app in play store. Really able to do everything I personally want to be able to with that module.
Sent from my VS980 4G using XDA Premium 4 mobile app
Hey XDA, I've been looking for a pure AOSP rom for the Note 4 for a while because I'm not a fan of AOSP derivatives with all their extra customisations. Seeing as my warranty has ran out and I've still not seen anything in development, I figured I could probably give it a go myself. However, I've not done any developing since the days of the HP TouchPad having android ported across so it'd take a bit of work on my part (which I'm willing to commit).
All I wanted to know is if there is a glaringly obvious reason that I'm missing for why no one has developed a rom like this for the Note 4?
I have a Nexus 5 which will be good for getting back into practice compiling roms, and an LG GPad 8.3 running a pure AOSP rom which will be good for practicing too. Anyone else interested in this?
Cheers, Will.