Related
I'm quite confused about the flash support on the Desire. I have the HTC and a Nokia N900.
My Nokia is capable of playing every kind if flash on the internet and does it quite well for instance BBC Iplayer.
Now from what I know the Desire has better hardware on all levels so why can the lesser device perform better with flash than the Desire?
Any ideas?
Prob cause linux has full flash support? I dunno...
It's because the N900 has full flash support (I think it is 9.4), whereas until the 10.1 update, the Desire only has Flash Lite, which is designed for low-powered phones, and so it can only play lots of flash badly until then.
ipodtouch1001 said:
It's because the N900 has full flash support (I think it is 9.4), whereas until the 10.1 update, the Desire only has Flash Lite, which is designed for low-powered phones, and so it can only play lots of flash badly until then.
Click to expand...
Click to collapse
Thats not true if you go to google.com and type in what flash version do I have and hit the top link this say my HTC has 10.1.
On Nokia N900 I have,
Version LNX 9,0,246,0
Operating system Linus 2.6.28-omap1
Video capable yes
Audio capable yes
Local file i/o enabled yes
On HTC Desire I have,
Version FL 10,1,123,391
Operating system Linus 2.6.29-
Video capable yes
Audio capable yes
Local file i/o enabled no
So not to sure about it
Actually this Version FL 10,1,123,391 ... is not full flash.
It is the same as FlashLite 4.
The "real" 10.1 with hardware accelerator for Android has NOT been released yet.
Adobe promised 2nd half 2010.
So, wait till then
mklass said:
Thats not true if you go to google.com and type in what flash version do I have and hit the top link this say my HTC has 10.1.
Click to expand...
Click to collapse
I remember reading somewhere that the '10.1' that you see when you do your query is not the same as the 'desktop Flash 10'; it is apparently only version 4.x. There was also a video on YouTube explaining this. Can't remember the links off the top of my head.
@Gogol: you just beat me to it. But yeah basically the same thing.
Many thanks for the info guys
gogol said:
Actually this Version FL 10,1,123,391 ... is not full flash.
It is the same as FlashLite 4.
The "real" 10.1 with hardware accelerator for Android has NOT been released yet.
Adobe promised 2nd half 2010.
So, wait till then
Click to expand...
Click to collapse
Sorry, that's what I meant, didn't want to cause confusion
They should really be more clear regarding Flash on the Desire. I have seen many reviews where they say 'even though the Desire has flash support, it is not working very well'...
Then I always get of my but and email then, saying this is Flash LITE. Full flash expected in a few months.
But I understand why so many people are confused.. HTC off course just says 'flash', so more people will buy it. How bad people can be when there is money involved
XDA mark said:
...Then I always get of my but and email then, saying this is Flash LITE. Full flash expected in a few months.
But I understand why so many people are confused.. HTC off course just says 'flash', so more people will buy it. How bad people can be when there is money involved
Click to expand...
Click to collapse
lol, but true
at next monday (12. april) adobe introduces the new creative suite. i've read somewhere, that the creative suite will be released on 17. of april! i think at this point, they will spread out the new flash player 10.1 release candidate (wich is allready available for desktops!).
for me it's not a difference, if the flash is full flash when you buy your device. it's more important to know, that they will release the update soon! let's wait, you will not regret it!!
I'm getting pretty good desktop flash here
Some really heavy flash 9 sites do load and show.
But I do think its not the 10.1 version with acceleration.
I hope it comes soon, because being a actionscript 3 developer myself, I can't wait to make full multiplatform solutions for my clients. Including mobile versions of the full software that can work on multiple mobile devices. But that needs full mobile 10.1 distribution!
It's the same **** we had when the Hero came out promising flash. Never got past flash lite. I have a feeling we are being strung along....
It's not flash lite, but certainly not 10.1.
The flash lite (which was/is very very limited) cannot show normal Flash 9 content (at least it can't on my Hero and on my WM mobiles).
The version that comes with the Desire can show full FlashPlayer 9 content. Perhaps will give it a try tomorrow to find out which version is the max.
But I can check out insanely complex FlashPlayer 9 (fully AS3 programmed using extended functionalities) sites. Runs like crap, but it works.
Edit: Ah, checked it via the Adobe site (this link).
Seems to be FlashLite 10(.1.123.391).
But it is able to show web application that are made in AS3 and/or with the Flex framework. that would require full flashplayer 9 support.
But very crappy... Even the simplest things seem to be heavy on the system. Stuff that should run flawlessly, no matter what speed the cpu should be (simple AS3 only programmed animation).
firedup said:
It's the same **** we had when the Hero came out promising flash. Never got past flash lite. I have a feeling we are being strung along....
Click to expand...
Click to collapse
Once Adobe releases the official flash for Android we should be good. The only question remains, can it be installed seperately or do we have to wait for HTC to put it in an update? (I'm afraid it will be the second option... :/ )
Yes, that (waiting HTC update) would be a really bad news.
We could hope that "complete" root would be possible when that happen, for possibility to install our self (with help from XDA gurus).
Right now, Paul from MoDaCo.com is able to have root access on his T-Mobile Desire, but still no write access to the system partition.
RaptorRVL said:
Once Adobe releases the official flash for Android we should be good. The only question remains, can it be installed seperately or do we have to wait for HTC to put it in an update? (I'm afraid it will be the second option... :/ )
Click to expand...
Click to collapse
http://www.wpcentral.com/team-dft-gets-their-hands-rtm-mango-build-7720
Running on HD7
awesome news, hopefully we may even get mango in the next few weeks, if these guys can get it onto the web. Also when we downgrade from mango do we lose all the apps/data we have put on since we updated?
Want to get my hands on it =)
i really wanna like to see what has improved or changed in the mango rtm build since 7712 beta hope the speed of fps handling gpu has been set to 50 fps.
sambaman009 said:
awesome news, hopefully we may even get mango in the next few weeks, if these guys can get it onto the web. Also when we downgrade from mango do we lose all the apps/data we have put on since we updated?
Click to expand...
Click to collapse
According to MS's official statement, yes. You have to restore from the back-up you created when you upgraded to the Beta in order to Upgrade to the official release. So, anything installed/done after upgrading to the beta will be lost. You can reinstall those apps from the marketplace on your device though.
They will be releasing it to the public over the next few months and I cannot wait as it means that everyone will be able to make use of the power and the new feature set of the Mango update.
Has anyone found the rom on the DFT site?
drkfngthdragnlrd said:
According to MS's official statement, yes. You have to restore from the back-up you created when you upgraded to the Beta in order to Upgrade to the official release. So, anything installed/done after upgrading to the beta will be lost. You can reinstall those apps from the marketplace on your device though.
Click to expand...
Click to collapse
Cant we just copy app data to computer and replace in the official mango build. This is what I'm gonna try for my game saves. Not that it really matter's I'll just beat the games again. Give me something to do on my down time.
Sent from my HD7 using XDA Windows Phone 7 App
Hopefully we can get our hands on this build.
XDA Windows Phone 7 App
qsr786 said:
i really wanna like to see what has improved or changed in the mango rtm build since 7712 beta hope the speed of fps handling gpu has been set to 50 fps.
Click to expand...
Click to collapse
If you're referring to XNA/Games, the fixed 30 fps frame rate has been removed. Any game to run in a higher frame rate would have to be updated and optimized accordingly though.
yeah you´re right but i didn´t mean that did you see the video where they compare ios, blackberry android and wp7 they showed that the ie9 can handle 50 fps in the fish test... hope you know what i mean..
yeah well im hoping the wizards here on xda will find a way for us to get the RTm version without going back to our backups. since I have alot of data- texts etc hahaha that i would like to keep
Mango
The DFT has a RTM build of mango hopefully we become a 7720 ROM to flash
tessut said:
The DFT has a RTM build of mango hopefully we become a 7720 ROM to flash
Click to expand...
Click to collapse
see http://forum.xda-developers.com/showthread.php?t=1205369
sambaman009 said:
yeah well im hoping the wizards here on xda will find a way for us to get the RTm version without going back to our backups. since I have alot of data- texts etc hahaha that i would like to keep
Click to expand...
Click to collapse
I wouldn't do that. I'm looking forward to rolling back to NoDo and flashing the RTM. As we saw with the Twitter usernames in the People Hub, somethings are broken when updating from test build to test build. The only way to get Twitter fully working is to roll back to NoDo and upgrade, if not, it won't allow you to link your contacts to Twitter names. Who knows what else is off.
HoHo
Muito Legal mesmo
Since my post count is so low I have to start a new thread for this, sorry about that.
I just installed the ICS Beta III
http://forum.xda-developers.com/showthread.php?t=1343361
A half hour later or so I get an email from Google 'Welcoming me to my Galaxy Nexus'.
Has this happened to anyone else???
Did you happen to wander into the about section and click on system updates?
Sully6789 said:
Did you happen to wander into the about section and click on system updates?
Click to expand...
Click to collapse
Nope, I flashed the ROM then downloaded a couple of apps from the Market as I was doing that I got the email.
All the links go to Google. I am just wondering is it something buried in the ICS code. Once you log on with your Google account it sends out a standard email to the account.
I don't really want to bother any of the dev's with it. They have enough to worry about right now without someone hassling them about something that is not that important in the grander sceme of things.
It's because the galaxy nexus is the only ICS Device with release codes for market so far. That will disappear once a more similar HTC device is released with ICS and we have a broader selection of release codes to choose from. Earlier beta's ran on test codes. They can be changed in build.prop.
Cheers man. I just could not understand it since it did not happen when I flashed the 1st and 2nd beta roms.
Thanks for posting this MrBC I also got this email and was curious about it.
I got this email as well MrBC...
Of course they can track what ROM use are using to browse android market. For example, I have recently update to Android revolution 2.3.5 and now not able to install few app which I used to have earlier on stock ROM 2.3.4.
I also got this
just ignore it lol
what i wondered was if it thinks we have a nexus why can we still not see some android apps lol
It's still beta so there are plenty of bugs. Its possible that there is a framework bug, or some component is missing. Then there is still the fact the a lot of apps on market are listed as not compatible with ICS. I'd expect it to take until 2012 before we have a fully functioning ROM and a fully working market.
Sent from my HTC Desire HD using Tapatalk
GrapheneOSThe private and secure mobile operating system with Android app compatibility. Developed as a non-profit open source project.
website : https://grapheneos.org/
WebUSB-based Installation : https://grapheneos.org/install/web
CMD Line Installation : https://grapheneos.org/install/cli
Releases : https://grapheneos.org/releases#raven-stable
This is listed as "Experimental"...
Not to sound like a broken record but with no play services do Google Photos and app updates work with that "sandboxed Play services compatibility layer" mentioned on they site?
Android-Desire said:
Not to sound like a broken record but with no play services do Google Photos and app updates work with that "sandboxed Play services compatibility layer" mentioned on they site?
Click to expand...
Click to collapse
yes. works very well (as long as you install all 3 parts of sandboxed play services). I would maybe wait a few days before installing it on the Pixel 6. but using A12 on my 3xl and everything works, photos, gboard, official gcam (all running with network access disabled).
Also, GrapheneOS for Pixel 6 still says Experimental on their download page (it might just need to be updated). But if you're okay with maybe experiencing some bugs, it should work fine (but as stated above, most should wait a few days, they're very good on updating - especially the first few weeks after release)
Good to hear about... will be watching! cheers
I basically bought my P6P for this, so I'm extremely happy development is moving forward! Really hoping that, when a stable version is out, it will be possible to use the phone "normally" with it. Keep it up, Graphene team!
I'm with @Alex-Absolute I purchased my P6 just for GrapheneOS support, coming from a string of OnePlus devices. Though I am going to wait until it's listed as stable to switch, I'm excited they have a working build going!
I've got the release page in Windows' Aignes Website-Watcher, set to look for changes after "Pixel 6 Pro" and before "Version", so I should know when it changes to Stable.
roirraW edor ehT said:
I've got the release page in Windows' Aignes Website-Watcher, set to look for changes after "Pixel 6 Pro" and before "Version", so I should know when it changes to Stable.
Click to expand...
Click to collapse
Amazing, thanks for the tip!
Alekos said:
yes. works very well (as long as you install all 3 parts of sandboxed play services). I would maybe wait a few days before installing it on the Pixel 6. but using A12 on my 3xl and everything works, photos, gboard, official gcam (all running with network access disabled).
Also, GrapheneOS for Pixel 6 still says Experimental on their download page (it might just need to be updated). But if you're okay with maybe experiencing some bugs, it should work fine (but as stated above, most should wait a few days, they're very good on updating - especially the first few weeks after release)
Click to expand...
Click to collapse
I used GrapheneOS on my 4a during most of the Experimental days, and i did not experience 1 hicup. I would compare their Experimental Builds to Android 12 Beta. So it's nothing to be afraid of. It's definitely ready for daily use in my own opinion....
Are there any screenshots of this OS? I always like trying new things but I'm thinking there isn't much to look at that would be different from a standard Android OS
Alex-Absolute said:
Amazing, thanks for the tip!
Click to expand...
Click to collapse
You're welcome, I'm using the free version - it's been around for a very long time on Windows, and I'm using the Android app which appears to more or less sync with the Windows version through Dropbox, if you have or create an account with Dropbox. It doesn't work perfectly for me, but I at least get notifications on my phone about the same changes in websites that the Windows program lets me know about - so I at least know that I should get on the computer and look to see what's new.
Sorry to anyone for the OT - I have lots of Android-related sites set to give me notifications of changes through this program.
The non-free version is a little pricey for my needs.
RetroTech07 said:
Are there any screenshots of this OS? I always like trying new things but I'm thinking there isn't much to look at that would be different from a standard Android OS
Click to expand...
Click to collapse
I will post some screens later this evening...
I've wanted to switch to this for a long time (It's actually a huge reason I switched back to the Pixel series) but I'm not sure if I can commit to losing Android Auto
AndroidAddict420 said:
I used GrapheneOS on my 4a during most of the Experimental days, and i did not experience 1 hicup. I would compare their Experimental Builds to Android 12 Beta. So it's nothing to be afraid of. It's definitely ready for daily use in my own opinion....
Click to expand...
Click to collapse
I agree. I've been using it off and on for 18 months on different pixels. but just good to be cautious, as always...
GrapheneOS just tweeted a few hours ago, the next release will be Stable for the 6 series (most likely this week)
Alekos said:
Also, GrapheneOS for Pixel 6 still says Experimental on their download page
Click to expand...
Click to collapse
What I read about that is that its not experimental in the "unstable" sense, its that they haven't fully implemented the security enhancements.
Flippy125 said:
I've wanted to switch to this for a long time (It's actually a huge reason I switched back to the Pixel series) but I'm not sure if I can commit to losing Android Auto
Click to expand...
Click to collapse
Given the sandboxed mode for play services, do you really have to lose auto?
The.Jericho.Initiative said:
Given the sandboxed mode for play services, do you really have to lose auto?
Click to expand...
Click to collapse
Good question. Last time I looked into it, AA was a no-go. Guess there's only one way to find out. I'll report back later if it works or not
UPDATE: Still a no-go. I just receive an error that the AA protocol isn't supported. Guess I'll go back to compromising my privacy for the sake of convenience while driving.
Other than that+call screeening, this build is solid for an "experimental" build (Tbh they could have put the stable flag on this, but I assume they are waiting for bug reports before doing so). If anyone is looking for a good de-Googling solution, this is it.
Flippy125 said:
Good question. Last time I looked into it, AA was a no-go. Guess there's only one way to find out. I'll report back later if it works or not
UPDATE: Still a no-go. I just receive an error that the AA protocol isn't supported. Guess I'll go back to compromising my privacy for the sake of convenience while driving.
Other than that+call screeening, this build is solid for an "experimental" build (Tbh they could have put the stable flag on this, but I assume they are waiting for bug reports before doing so). If anyone is looking for a good de-Googling solution, this is it.
Click to expand...
Click to collapse
Despite the hassle and increased expense, perhaps one of those Carplay AI boxes like Apple Pi might be the necessary workaround?
I'm very interested in this OS, but I too rely on carplay/auto as a general rule while driving. If I have to outsource my maps and music to an external box in order to have more comprehensive device security, that might just be the way it has to be.
Flippy125 said:
UPDATE: Still a no-go. I just receive an error that the AA protocol isn't supported. Guess I'll go back to compromising my privacy for the sake of convenience while driving.
Click to expand...
Click to collapse
Thank you for reporting. As curious as I am about this OS, this rules this out for me too. Been using AA for almost four years now and I'm hooked.
I want privacy, but I cannot live without syncing all my stuff together. Is this OS for me?
https://www.xda-developers.com/android-13-tap-to-transfer/
January 10, 2022 3:59pm Corbin Davenport
Google reportedly working on tap-to-transfer feature for media in Android 13Android 12L hasn’t been officially released yet, but that isn’t stopping Google from working on the next major release, Android 13 (which is internally codenamed “Tiramisu”). We’ve already covered some of the features currently in the works for Android 13, but now details are public about another possible change — a “tap to transfer” feature for media playback.
Android Police has shared a supposed Google UI demo mockup for a new feature in Android 13, labelled as a “Media TTT” workflow — the “TTT” part is for “tap to transfer.” The screenshots show off a small message at the top of the display, which reads “Move closer to play on DEMO” in one image, and “Playing on DEMO” on the other. The latter popup also has an Undo button, presumably in case you accidentally walk close to a speaker and don’t want your music to start playing on it.
There aren’t any other details available besides what you see in the above screenshots. The functionality might work similarly to the ‘Hand off audio’ feature on Apple’s HomePod smart speakers, which allows you to hold an iPhone or iPod Touch close to a HomePod to set the speaker as the output. That feature uses a combination of Wi-Fi and Bluetooth, but it’s not clear what mechanism Google will use if this functionality actually makes it into Android 13. Google could add this to the Chromecast functionality in Android, or bring it to standard Bluetooth wireless audio, or both. It’s unclear what technology this feature will use to share files.
Assuming a similar schedule as previous years, Android 13 will likely start rolling out in the fall of this year, with developer previews and beta releases in the coming months. Android 12L is supposed to arrive sometime before the end of Q1 2022, which can be anytime from now until March 31. Android 12 is still slowly rolling out to phones and tablets — Sony just started updating its devices, for example.
Click to expand...
Click to collapse
roirraW edor ehT said:
https://www.xda-developers.com/android-13-tap-to-transfer/
Click to expand...
Click to collapse
The wording is awkward. Gives the impression of something similar to Bluetooth file transfer. I suppose it could be some kind of selective playback over Bluetooth (as opposed to routing *all* audio over Bluetooth), but since google is really into reinventing the wheel and making things only compatible with their own crap, its probably just (chrome)cast.
Google needs to fix their current software first before working on their next chapter.
RetroTech07 said:
Google needs to fix their current software first before working on their next chapter.
Click to expand...
Click to collapse
It is never going to happen that any company is going to drop everything they're doing and only work on one thing.
RetroTech07 said:
Google needs to fix their current software first before working on their next chapter.
Click to expand...
Click to collapse
Software is perfect for me...
roirraW edor ehT said:
It is never going to happen that any company is going to drop everything they're doing and only work on one thing.
Click to expand...
Click to collapse
I completely understand, and I don't expect that. I was being heavily sarcastic given the many issues users have experienced with the last software update that had to be pulled because of a radio issue. Google just has weird priorities at times.
P6P said:
Software is perfect for me...
Click to expand...
Click to collapse
It's been fine for me but I wouldn't say perfect. I've had some random reboots / glitches appear, and battery drain issues I can't explain.
Le Googs be like, 12 is a hot mess! Time to focus on 13 instead!
RetroTech07 said:
I completely understand, and I don't expect that. I was being heavily sarcastic given the many issues users have experienced with the last software update that had to be pulled because of a radio issue. Google just has weird priorities at times.
Click to expand...
Click to collapse
The radio issues are probably the responsibility of Samdung to deal with. I doubt that ANYONE at google is working on that at any depth greater than testing the updates received from samduck.
But even if google was doing actual work on the radio, do you really think that the same people have the knowledge and skills to work on radio firmware as those who work on UI or those who work on things like this feature? So you would do what? Lay off the UI and new features workers while waiting for the radio firmware people to fix their glitches?
Yup this is confusing because Google needs to fix stable 12 first but then they still developing 12L and now 13 lol I know they have different teams but I wonder if they will just merged 12L to 13 or just leave 12L for fold / flip devices.