ICS 4.0 Sources Out - All discussions here!
- Thread starter PG101
- Start date
nice let's hope it's true
I shall write this only once, feel free to paste it to the top of the thread:
There are 3 things that will not work, ever, without updated (true ICS, possibly honeycomb) components, either in source form, 2x-specific updates, or other compatible origin:
1 - OMX video (video decoders/encoders)
2 - UI Hardware Acceleration (libhwui, aka OpenGL renderer + hwcomposer. If it doesn't drag nor skip, congratulations, you simply got the same thing you already had with gingerbread; it doesn't mean it's using the new renderer, not to mention the composer)
3 - Cameras (which depend on both previous items)
Last edited:
There is no way that LG will release any update whatsoever before they first release their new devices, to make sure that they'll sell as much ICS devices as possible. So I guess the only way, is either by nvidia (which I doubt it) or with the help of the drivers of the O3x considering that it has similar hardware as the O2x.
I wish I am wrong tho
For a rom to be leaked, first of all LG needs to actually start making the rom. And i dont see that happening anytime soon. Personally dont really care about the camera. I almost always have my 7 year old nikon d200 in my car.
Since they are releasing the ICS rom for the O2X in Q2 2012, they must have already started working on it.
Lol are u serious mate?
Gingerbread was suppose to be released in Q2 of 2011 too?
Do u believe in Santa too?
Gingerbread was suppose to be released in Q2 of 2011 too?
Do u believe in Santa too?
Ofcourse Santa exists. He lives on the North Pole.
I heard that he moved to South Pole
Sent from my Tapatalk
http://xdaforums.com/showthread.php?t=1380051
Did they not actually get HW acceleration working here?
Same here f the camera or acceleration.
People just want to test roms all day long for a camera buy a proper one the camera on this phone is so bad that my grandma had to remove has glasses to see better
Sent from my LG-P990 using XDA App
No it's a hack. It's actually no real improvement to stock gb. The "HW accel" is more like disable everything related to the real hw accel and so add backward support. Arcee sure can give more informations on this, because he wrote it (and is way more into android than I am). But this is my understanding.
Without this the rom was unusable... really really laggy.
If my understanding is correct, there is a distinction between hardware acceleration, and hardware acceleration of the UI. Honeycomb introduced hardware acceleration of the UI, so clearly some layer of the GPU drivers will have changed significantly from Gingerbread. I'm guessing then, that regular hardware acceleration is what is being referred to by that thread, and also in the spreadsheet for our device.
Edit: I guess it's actually more related to the workaround to allow ICS to work without the updated drivers.
Last edited:
I dont understand too, HW acceleration isn't working? What do you mean about hack isn't real?(they put that information in the development doc) .
Sent from my Optimus 2X using Tapatalk
Sent from my Optimus 2X using Tapatalk
I have an ideaaaaaaaa
Could we possibly get camera working the same way we got sound working? By using CM7 system files for camera? We may be sacrificing some of the ICS camera improvements, but at least it will work (if it does work at all.)
Could we possibly get camera working the same way we got sound working? By using CM7 system files for camera? We may be sacrificing some of the ICS camera improvements, but at least it will work (if it does work at all.)
So this is where the reference code, which was kind of promised by nvidia, enters to save the day?
It's actually worse. Have you tried a GPU intensive app (angry birds will do nicely) yet?
It's a bit uglier than that. Reverting to a GB-compatible state is pretty much impossible, since the changes are big, and span a lot of subsystems (everything that deals with the display: surfaceflinger, stagefright, camera, and all their dependencies).
The 2 major (there are others) changes are:
1 - display buffer management now depends on the new unified "Android Native Window" buffers, managed by gralloc. (the old overlay system for video/camera was completely discontinued). Pre-HC grallocs do not support this in any way or fashion, and will fail in any attempt to do so.
2 - Most textures (think of them as bits of displayed stuff) are now of a specific type (external EGLimage), which are opaque to the GL implementation (i.e., it doesn't need to recognize the format to pass them along between layers). The renderers forward everything along as external images, and pre-HC GL implementations didn't support the image_external extension at all, so they reject any attempt to do this.
The simplest way I can explain this is... the hacks I placed in CM9 force everything to be plain old (and supported) 2D textures, and push them into gralloc as such for immediate render.
This is not how it's supposed to work, the GPU hates it, so a number of other hacks were necessary (like retrying unlocks every 1msec whenever a buffer operation fails), and the end result is a highly innefficient implementation (and completely incompatible with the actual accelerated stuff ICS wants to use). There's no acceleration at all, just a best-effort approach at getting things to actually render; And since it doesn't create true ANative buffers, things that depend on them (OMX and Camera, for instance) won't work either.
Now... this was never meant to go into distributable builds, and it's very unlikely you'll ever see "official" CM9 builds using this stuff. Its only purpose was to get the devices functional enough to work on more generic CM features outside an emulator.
Last edited:
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
93I got a free wifi pass at my hotel so I thought let's do a quick read through xda.
I read the 30 new pages in this thread as well, do you think I need psychological help?
Anyways, as someone else (mustangtim) wrote about it in the G2x section I can finally write it without some stupid hints here as well:
Ricardo has a fully working P990 CM10 version (yes, with hwa). He got an earlier su660 ics dev leak directly from LG, even before leaks were on their server.
The leak was a little different though, he was able to boot with the kernel.
Long story short: jb runs great. He can't release it as he can't damage his good relationship to LG, I think you can understand that - so don't bug him about it.
I'm just writing this to answer the people who have doubts.
We will get cm10 as soon as the su660 kernel source drops. And it does run great on our hardware.
Sent from my Nexus 7 using xda app-developers app61Hello everyone.
I have seen the tweets from LG Canada posted here and since then those tweets have propagated through out other web outlets but I think way too much has been made of the LG Canada ICS update statement. The OP either did not understand the context of the statement or just had a "I'm the first to get an official answer from someone at LG" moment and got a little excited posting the info. So I thought I would give some insight into the statement so people, particularly worldwide, can understand what is going on and why that statement came from LG Canada.
In Canada phones are sold through carriers. There are no companies that sell unbranded phones, well there are small shops that import phones but their sales are so small that they are not worth noting and they are almost considered grey market as they will not support the phones officially. Since there are no unbranded phones in Canada the carriers control the availability of a phone model which also means they control the updates to their branded model. If the carriers are not interested in supporting the phone it does not get any support period. There are Galaxy Nexus owners still on 4.0.1 when using carrier updates!
Now specifically to the Optimus 2x in Canada. The phone was not that popular and was really only picked up by carriers to use the "first dual core phone" LG marketing hype to make them look like they are cutting edge. From what I remember the phone was only picked up by three carriers. Two AWS carriers (which are small players) Mobilcity and Wind, and one major carrier Rogers which put it under their "budget" sub-brand Fido. Mobilicity dropped the phone quite awhile back so they are out of the picture. Wind has recently EOL the phone and they did not even bother with the GB update so they are out. That leaves Fido.
Fido did get the GB update but never shipped the devices with the GB update. I got my 2x in March and it still had Froyo on it. My guess is Fido had not reordered stock from LG since after the GB update so that is quite awhile ago. The only way to get the upgrade is if the customer does it themselves via LG tools. This should give you an indication of how many they are selling and how well they support the device. While Fido still offers the 2x they recently dropped the price which usually means they are trying to get rid of their stock before they discontinue the device so they are 2/3 out. Carriers are not interested in spending time/money updating devices they are either not selling or about to stop selling. They want to sell new phones hopefully with new/renewed plans. Updating a phone could cost them a sale. This is not LG's behavior but the carriers.
When a phone is banded by a carrier usually the carrier sends the specs (boot animations, artwork, network configs, apps to included, etc.) to LG and LG preps a ROM build which is put on the phone at shipping for the carrier. Since all the phones in Canada are branded and none of the carriers are requesting an update LG Canada does not need to consult LG HQ about the standing of ICS for the 2x. My feeling is When the LG rep on Twitter was asked the question they looked up the status of the 2x with the carriers. The status probably mentioned that there is "no future orders" and no request for ROM updates. That made it safe for the LG Canada rep to say on Twitter that there will be no ICS updates for the Canadian 2x. The rep did not contact LG HQ about the ICS update. Basically the LG Canada's statement is not based on technical reasoning but market reasoning.
What these means for us Canadians is that we are out of luck for an official carrier branded ICS update. We can now add carriers to the nVidia / LG list of people to ***** about for the lack of an ICS update. Our only option is to go with an unofficial ROM but quite frankly the carrier ROMs suck. The ROMs created by the XDA community are far superior and I would have gone with an unofficial ICS build anyways. From what I understand as long as one country gets an ICS build the drives can be used to build general ROMs that Canadians can use. From observation the 2x is still popular in other areas. I think if there is an update the first will probably be Korea. I would say look there for more accurate information.
TL;DR version:
1. LG Canada does not control updates in Canada, the carriers do.
2. The carriers have either dropped or are in the process of dropping the 2x thus the carriers are not interested in updates.
3. LG Canada was able to safely give an official statement about the 2x Canada at this time based the carriers not wanting an update, not based on technical information from LG HQ.
4. LG Canada statement should not be viewed as an early indicator of LG's general position on the ICS update for the 2x. This is not a leak.
I hope that explains the situation better and how to read the meaning behind the LG Canada tweets. For people who have been using the LG Canada statement as "ZOMG this is the beginning of the end, EVERYONE PANIC!!! LG SUCKS!" fodder, and that includes you tech bloggers reading this, please stop and understand the situation. LG may still not deliver an ICS update but this is not the sign that it is not coming. Look else where.
Also people stop assaulting the LG Canada feed with questions about your country or LG world wide. I know that LG Canada seems to be the only one responding to questions but LG Canada can only speak for the situation in Canada which as outlined is somewhat unique. Bug your own country LG reps as that might yield more interesting information for everyone.
I will also mention that I think people are being really impatient with LG. Many companies are still in the process of updating their own devices from the same generation to ICS and last I heard only around 10% of devices have ICS or JB. I agree people should be pissed with LG because of LG's failure to live up to their promises (which BTW if they don't deliver could be grounds for a class action suit) but LG is not unique in anyway with their lateness of ICS updates. If anything I think LG trying to be the first one with a dual core, LG likes to be the first at things to keep up appearance i.e. dual core, 3D, LTE, etc., and in that rush probably either pressured nVidia to pump out a rushed chipset or nVidia offered them a first gen chipset to beat everyone. As such to make the commitment technical details probably were not completely sorted out thus we have a unpopular first gen chipset that most manufactures skipped over and nVidia doesn't want to waste much time on.
That being said I do believe that an ICS update will eventually come from LG but this is my last LG device.
Good first post ?47ICS Camera HAL for P990/SU660
this is a ICS camera HAL for P990/SU660.
based on Raviprasad V Mummidi for Qcom camera
https://github.com/rapmv78/android_hardware_qcom_camerahal
tested on the SU660 (Optimus 2X model in Korea)
Please see also:
- [Dev] ICS Camera Driver Development by zivan56 @ xda: http://xdaforums.com/showthread.php?t=1379368
- http://xdaforums.com/showpost.php?p=20281617&postcount=17
- https://github.com/Andromadus/android_hardware_qcom_camera
----
It is needed to revert "MemoryHeapBase: Save and binderize the offset"
commit f24c4cd0f204068a17f61f1c195ccf140c6c1d67
It break binary compatibility of libbinder.so with CM7/GB.
https://github.com/CyanogenMod/andr...mmit/f24c4cd0f204068a17f61f1c195ccf140c6c1d67
and some simple wrapper functions are needed (please see libui.patch included in the attached tarball)
like as
Code:extern "C" status_t _ZN7android7Overlay13dequeueBufferEPPv(void* buffer) { return NO_ERROR; }
camcoder(video encoding) does not work now45
There are, Kostja_V's and Harsh's rebuilds.
I got some time over the weekend.
If arcee won't release CM10 I will play around with the Stock ROM.
I already repacked (read: decluttered) the ROM to fit it into the stock system partition, I'd only need to compile a new kernel which uses the old bootloader and have to check the partition stuff.
If it works as expected you won't have to use nvflash to change the partition layout anymore - a simple CM10 flash would be enough.
Sent from my Nexus 7 using xda app-developers app
New posts
-
-
[ROM][UNOFFICIAL] LineageOS 17.1 For SM-P600- Latest: SamsungGalaxySamsung
-
-
