OpenWebOS Beta released - TouchPad General

http://blog.openwebosproject.org/post/30593510898/open-webos-august-edition
What does this mean for us?

I don't believe the TouchPad is a supported platform. Which is pretty amazing, if I am correct.
Sent from my cm_tenderloin using xda app-developers app

Has no effect on us because the TouchPad won't be supported because the drivers won't be released to open source
A quick Google search and you can read all about it
Sent from my AOKP M6 TouchPad using TapaTalk 2

Here's this: https://github.com/openwebos/build-webos
Posted by Mr. Z's Galaxy S3.

What's the OpenWebOS Beta is good for if it does not support any device currently on the market ???

Meaningless to Touchpad
leftovermagic said:
http://blog.openwebosproject.org/post/30593510898/open-webos-august-edition
What does this mean for us?
Click to expand...
Click to collapse
HP Touchpad, HP Pre, HP Veer... All the pre-existing devices are not supported. Short answer: meaningless. This is of no help on GB, ICS, JB platforms as well, even if the Touchpad was supported, it would not provided hardware drivers.

Related

ICS hardware acceleration?

First off, I apologize if this has been discussed before. I'm posting from my phone and search is kinda funky on mobile but I didn't see this same question in the results. My question is does the Atrix and Xoom share the same generation Tegra 2? With the new aosp code pushed today I read that a Xoom build was published. In theory, and if it has hardware acceleration, wouldn't our Atrix also have hardware acceleration if you used the Xoom driver? Or are drivers not supplied in the aosp? Never really dealt with source code besides a couple Linux x86 applications.
Sent from my MB860 using XDA App
jiggabyte said:
First off, I apologize if this has been discussed before. I'm posting from my phone and search is kinda funky on mobile but I didn't see this same question in the results. My question is does the Atrix and Xoom share the same generation Tegra 2? With the new aosp code pushed today I read that a Xoom build was published. In theory, and if it has hardware acceleration, wouldn't our Atrix also have hardware acceleration if you used the Xoom driver? Or are drivers not supplied in the aosp? Never really dealt with source code besides a couple Linux x86 applications.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah of course, that's why I'm running it right now with hardware acceleration working and it's running so smoothly.
Really?
BravoMotorola said:
Yeah of course, that's why I'm running it right now with hardware acceleration working and it's running so smoothly.
Click to expand...
Click to collapse
So bravo are you saying that you are working on an ICS Atrix port from the Xoom AOSP ICS?
That would be sweet because I haven't seen any ICS ports for the Atrix only mods.
jiggabyte said:
My question is does the Atrix and Xoom share the same generation Tegra 2?
Click to expand...
Click to collapse
No. The xoom uses a NVIDIA Tegra 2 T20 processor while the atrix uses the NVIDIA Tegra 2 AP20H processor.
Oh that sucks
Sent from my MB860 using XDA App
Rough :-( I was hoping our Atrix would have a better chance of hardware acceleration. Thank you for answering my question.
Sent from my MB860 using XDA App
The g2x has the same hardware...but no ICS yet
Sent from my MB860 using xda premium

Onskreen. Multile Windows on android! (Like a desktop os)

Today, onskreen's cornerstone was opened sourced. Onskreen's Cornerstone allows for a desktop windows management style, unfortunately it has to be baked into roms. Would it be possible for someone to bake it into cm9?
http://www.onskreen.com/cornerstone/
Lulz, I literally just posted this 1 minute here before you did. Fellow redditor I presume?
Its open source so it could easily become part of CM or other ROM.
Look nice
Sent from my Optimus 2X using XDA App
Looks good!
Dalingrin is already working on it, and has it running on his Touchpad.
Sent from my HP Touchpad using Tapatalk.
Krunk_Kracker said:
Dalingrin is already working on it, and has it running on his Touchpad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
amazing
so we will get it in next update

Updated Adreno 220 ICS GPU Driver

Noticed on the homepage this article
http://www.xda-developers.com/android/updated-adreno-220-ics-gpu-driver-speeds-up-2d-rendering/
Hoping to gain some interest to get this update brought to our device. I've messaged gjcamp and await a reply. Also tried flashing the file for other devices on my note without success LOL
here's link to source if any dev wants to take a look
https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources
In the meantime....try out chains3D....Marvelous!
Sent from my SAMSUNG-SGH-I717 using xda premium
Chain 3d??
Sent from my SAMSUNG-SGH-I717 using XDA
Eric-1987 said:
Chain 3d??
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I would say he is probably referring to Chainfire 3D.
I used it on the HP Touchpad on ICS. Allowed me to play Tegra 3 games on my Touchpad. Don't know much more about what it does.
I really would have liked to use chanfire 3d...but the app answer its instructions were so convoluted. Does it affect regular phone performance? Is the emulated performance ok?

Cyanogenmod 10 (Jellybean 4.1) News

CyanogenMod plans a quick leap to Jelly Bean for version 10, existing devices likely to tag along
The crew's early looks suggest that there will only be a few minor tweaks needed to merge Google's latest with the custom Android code, making CyanogenMod 10 a relative snap to produce. The update's release is still very much up in the air without the Android Open Source Project code available to modify; that said, device compatibility also isn't expected to be an obstacle. Any device that can run CyanogenMod 9 should run version 10 when it's released. As long as we're willing to wait for a stable 9.0 to emerge first, there are few barriers to making Jelly Bean that much sweeter.
Click to expand...
Click to collapse
http://www.engadget.com/2012/07/05/cyanogenmod-plans-a-quick-leap-to-jelly-bean-for-version-10/
while our cm9 is not stable yet, when we grab official ics drivers, it should be easy to jump jellybean wagon
Is it really gonna be cm10? Figured they would do like 9.x
Sent from my MB855 using xda app-developers app
DWake014 said:
Is it really gonna be cm10? Figured they would do like 9.x
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
yep.
Many have asked whether JB will be CM9.1 or CM10. Keeping with the pattern thus far, every newly named AOSP update results in a bump to the CM major version. This has the added benefit of fitting into the pattern of [insert codename position in the english alphabet] = CM version. Examples being: G is the 7th letter thus CM7, I is the 9th letter thus CM9 and J = 10.
Click to expand...
Click to collapse
https://plus.google.com/117962666888533781522/posts/PNJutPNhixo
DWake014 said:
Is it really gonna be cm10? Figured they would do like 9.x
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Because CyanogenMod's Eclair, Froyo, and Gingerbread were CM 4.1, 4.2, and 4.3? Wait a minute, my Gingerbread CM ROM is 7? Confusing?
They didn't do point releases for Android's 2.0 point releases; no reason they'll do it for 4.0's point releases.
The number is the numerical placement of the code word in this instance j is the tenth letter so cm10 just as I is the 9th. They plan to keep using this naming structure from what I read.
Sent from my MB855 using Tapatalk 2
I vote for it to be called CMX
U know u want it.
But I am looking forward to a stable version of Google now. And that camera. Seems legit. Estimated time before alpha release around Aug/Sept maybe? But that's just my guess. I personally have no idea.
Sent from my CND'd MoPho
Jellybean source has dropped!! http://www.zdnet.com/google-open-so...-4-1-for-third-party-modification-7000000570/
When will the roms be released?
Sent from my MB855 using xda app-developers app
apidroid said:
When will the roms be released?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Really? an eta on something that just dropped? Psh.
meeok2 said:
Jellybean source has dropped!! http://www.zdnet.com/google-open-so...-4-1-for-third-party-modification-7000000570/
Click to expand...
Click to collapse
But still no Photon drivers, so nothing terribly exciting IMHO...............
willysp said:
But still no Photon drivers, so nothing terribly exciting IMHO...............
Click to expand...
Click to collapse
Same here. Still waiting on those drivers Motorola, Hello!!!
lroy said:
Same here. Still waiting on those drivers Motorola, Hello!!!
Click to expand...
Click to collapse
What does drivers do?
Sent from my MB855 using xda premium
LexLuger82 said:
What does drivers do?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Drivers are directions that tells your hardware how to interact with the software. At this point, we are frankenstein. We use different parts of other phones in order to make ours work. We need directions explicitly for our phone.
Sent from my CM9ed MoPho!
Acvice said:
Drivers are directions that tells your hardware how to interact with the software. At this point, we are frankenstein. We use different parts of other phones in order to make ours work. We need directions explicitly for our phone.
Sent from my CM9ed MoPho!
Click to expand...
Click to collapse
Oh ok
Sent from my MB855 using xda premium
Acvice said:
Drivers are directions that tells your hardware how to interact with the software. At this point, we are frankenstein. We use different parts of other phones in order to make ours work. We need directions explicitly for our phone.
Sent from my CM9ed MoPho!
Click to expand...
Click to collapse
Well with that in mind, I would imagine we'll be able to use most of the Atrix drivers when that's released, since that's 99% the same phone, and is scheduled for a Q3 ICS release, as opposed to the Photon's Q4.
bray424 said:
Well with that in mind, I would imagine we'll be able to use most of the Atrix drivers when that's released, since that's 99% the same phone, and is scheduled for a Q3 ICS release, as opposed to the Photon's Q4.
Click to expand...
Click to collapse
I was just thinking this the other day. Then it dawned on me... What do I know? Hope that statement is true.
Sent from my MB855 using xda app-developers app
It has a snapdragon processor, we have tegra.
Sent from my CM9ed MoPho!
Acvice said:
It has a snapdragon processor, we have tegra.
Sent from my CM9ed MoPho!
Click to expand...
Click to collapse
AFAIK, the Atrix has the Nvidia Tegra 2 and the Atrix 2 uses a TI Omap CPU.
hirent said:
AFAIK, the Atrix has the Nvidia Tegra 2 and the Atrix 2 uses a TI Omap CPU.
Click to expand...
Click to collapse
He was referring to the atrix 2.. And i could have sworn i read it had a snapdragon. Guess i was mistaken.
Sent from my CM9ed MoPho!
Acvice said:
He was referring to the atrix 2.. And i could have sworn i read it had a snapdragon. Guess i was mistaken.
Sent from my CM9ed MoPho!
Click to expand...
Click to collapse
I'm pretty sure he just said atrix, in reference to the original atrix, which is on motorola's update schedule for a Q3 ICS update.
And yes, my thought's exactly, I'd expect heavy driver reuse from that update.

CyanogenMod no longer delivers support for devices with snapdragons 1

Hey guys!
Yesterday I read an article about "CyanogenMod no longer delivers support for devices with snapdragons 1"
And as our device is a "cooper one", it seems we are not gonna make it..
Source 1: "CyanogenMod ya no entregará soporte para equipos con Snapdragon S1" - bitly.com/MCS7bU
Source 2: "CyanogenMod formally confirms ceased support for Snapdragon S1 devices past Gingerbread" - bitly.com/MCSGT5
And here is the official post of Cyanogenmod's Team (from Google+):
CyanogenMod 01/08/2012
CM 9+, N1 (and other S1 SoC)
The Nexus One, along with the other first generation Snapdragon devices (devices with the QSD8x50, MSM7x25, MSM7x27 and MSM7x27T SoCs), will not be supported beyond the CM 7.x (Gingerbread) branch.
We’ve been holding off on finalizing this, looking for ways that we could make this work and be happy with the release. Sadly, it never panned out, and we’ve decided that it’s time to stop our efforts.
The Nexus One in particular would have required a custom hboot to repartition the internal memory (which itself was limited to 512 MB, like most devices of that generation) and the proprietary libs available (from 2.3) would have required compromises in the CyanogenMod code that we are not willing to make. The wide variety of MSM7x2x(T) devices, on top of these problems, also have a complete lack of media libraries that are compatible with the new APIs introduced in ICS (video decoding and encoding, specifically). The pieces just aren’t there.
Does the capability to run ICS or Jellybean exist on these devices? Yes, with enough time, effort, and hacks it can be made to work. Do we feel the experience is worth all of that? No.
To measure our releases, we use the same subjective criteria as users do: “speed”, “jank”, “butter”, but also factor in user experience (UX) and other intangibles. However, beyond this is something that we can (and do) use as a ‘pass or fail’ mechanism, the Android Compatibility Test Suite. The CTS is used by device manufacturers to ensure that their changes to Android source do not break Android API, platform and other standards. This, in turn, brings stability to the Play Store for app developers. Breaking CTS would lead to a bad and inconsistent experience for app devs, which in turn would lead to a bad experience for you guys as users. If CyanogenMod was perceived to be blatantly violating CTS, developers could eventually blacklist CyanogenMod users from using their apps (or worse, Google could blacklist CyanogenMod from the Play Store altogether). No one would win by going down that path.
If, in the future, a solution is found that passes CTS, we will revisit the topic.
For users that are adamant about trying to run ICS and beyond, options exist. We are not going to recommend other builds however, as they are more than likely breaking CTS, and therefore our quality assurance standards as well. You can find them if you look in the usual places.
-The CyanogenMod Team
Edit The list of affected devices are as follows: blade, bravo, bravoc, buzz, c660, click, cooper, desirec, e510, e720, es209ra, espresso, hero, heroc, inc, legend, liberty, morrisson, motus, one, p500, passion, robym, s5670, supersonic, tass, u8150, u8220, z71, zero
Click to expand...
Click to collapse
Source: bitly.com/MCSZxf
So... What do you think ?...
Damnit...
Sent from my GT-S5830 using Tapatalk 2
How bout this? That is ICS
Shadow xD said:
How bout this? That is ICS
Click to expand...
Click to collapse
He means future support, that means future updates will take longer because now porting is needed to make it work.
The title is wrong.
You should say we won't get future support from Cyanogenmod.
AOSP still can be compile from source I guess.
Sent from my GT-S5830 using Tapatalk 2
galaxyace152 said:
The title is wrong.
You should say we won't get future support from Cyanogenmod.
AOSP still can be compile from source I guess.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
How can I edit it ?....
EDIT>Go Advanced. Be more careful next time.
eagleeyetom said:
EDIT>Go Advanced. Be more careful next time.
Click to expand...
Click to collapse
ok, understood =/..
¬¬
We never had and never will have OFFICIAL CM9+ support. UNOFFICIAL builds are what we'll have to live on..
Is this just saying that we wont have official CM9/CM10 support (which we all knew)?
Or is it saying that we will no longer get support from them for CM7?
Sent from the cracked screen of my GALAXY Ace.
tomb20 said:
Is this just saying that we wont have official CM9/CM10 support (which we all knew)?
Or is it saying that we will no longer get support from them for CM7?
Sent from the cracked screen of my GALAXY Ace.
Click to expand...
Click to collapse
I think CM 7.2 cooper is the last rom they do for Gingerbread.....
I mean... No more Official Roms for Galaxy Ace
JuampyXnaker said:
I think CM 7.2 cooper is the last rom they do for Gingerbread.....
I mean... No more Official Roms for Galaxy Ace
Click to expand...
Click to collapse
We will get GB roms.
We just won't get official CM9/10 and support from them for the above.
Sent from my GT-S5830 using Tapatalk 2
Yup.. CM7.x is after which the support ends.
Cm7.3 ?
Sent from my GT-S5830 using xda premium
CoolCatGetHome said:
Cm7.3 ?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
They've moved on from CM7, lol
King ACE said:
They've moved on from CM7, lol
Click to expand...
Click to collapse
Nope they are further developing cm7 for the devices wich dont get official cm9/cm10 support
Sent from my GT-S5830 using xda premium
CoolCatGetHome said:
Nope they are further developing cm7 for the devices wich dont get official cm9/cm10 support
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
That will be awesome as Gingerbread is best for the Ace.
ICS slows it down like hell!
galaxyace152 said:
That will be awesome as Gingerbread is best for the Ace.
ICS slows it down like hell!
Click to expand...
Click to collapse
agree, ICS+ was made for better devices than the ace.
Gingerbread works better for the ace.
tomb20 said:
Gingerbread works better for the ace.
Click to expand...
Click to collapse
and aosp GB works hell smoother.. even at this moment cm7 lags in front of aosp :silly::laugh:
cm7 may not see cm7.3 but it is alive for patches to existing system not further features
madman said:
and aosp GB works hell smoother.. even at this moment cm7 lags in front of aosp :silly::laugh:
cm7 may not see cm7.3 but it is alive for patches to existing system not further features
Click to expand...
Click to collapse
Yeah! I saw the quadrant for AOSP in Ace! It was some 2100 or something!

Categories

Resources