Major textfield bug AIR 3.7/3.8 on Android

Hey guys, I was wondering if anyone encountered this bug and managed to fix it. If not (or if this is not my fault somehow), I will open a bug report about it.
The bug does not happen on AIR 3.6 on any platform. It also does not happen on 3.7/3.8 for iOS. It only happens with 3.7/3.8 for Android.
There is a classic text input textfield on the screen. It is a singleline textfield. But somehow, it works like a multiline text. Whenever I press enter, I get a line break. Did anyone experienced this problem before?
Thanks everyone!

Could you please share the Android device(OS version) , AIR 3.x version you are using. I tried with classic text input textfield(Flash professional CS6) with Android OS versions 2.3.1, 3.1 and 4.1.2 but could not able to reproduce the issue. Please share a sample project at nimitja@adobedotcom (if possibe) to reproduce the issue. This will help us investigating the problem.
Regards,
Nimit

Similar Messages

Img Tag in textfield adobe air problem help :(

Hi there,
i ve got a textfield on the stage and wanted to give it a img
tag.
If i am using flash 9 in publishing, it is no problem.
if i change to adobe air. There is no img in the textfield.
Is this a bug???

I've had the same problem. Using an img tag in a dynamically
generated text field does not work the same published for AIR as it
does published for Flash Player. If I use a relative path for the
image or the class name of a symbol in the library in Flash it
works perfectly, but neither work if the same code is published for
AIR. Is there a solution to this that anyone knows of?
Here's an example:
var optionFont:Font = new UniversBold();
var optionFormat = new TextFormat();
optionFormat.color = 0x27318b;
optionFormat.bold = true;
optionFormat.size = 38;
optionFormat.font = optionFont.fontName;
var field:TextField = new TextField();
field.embedFonts = true;
field.autoSize = TextFieldAutoSize.LEFT;
field.defaultTextFormat = optionFormat;
field.selectable = false;
field.htmlText = "Hi There <img src='GTE38'> Hi There";
field.wordWrap = true;
field.width = 200;
addChild( field );
UniversBold and GTE38 are classes in the library. This works
when published for Flash, but if republished for AIR, the image
does not show up.

Crazy Textfield Bug on GPU with softkeyboardbehavior - Android only

Im am encountering a very weird bug on Android only (i think every android device, as I've tested, Droid Bionic, Galaxy S3, Nexus, Galaxy Tab)
In my -app.xml, i have .
<renderMode>gpu</renderMode>
<softKeyboardBehavior>pan</softKeyboardBehavior>
in my application, i have many textfields. When i give focus to a textfield, it does correctly and pans up as it should. Once the softkeyboard hides is when all the craziness starts happening....
Everywhere I now click inside my application, AIR thinks I'm clicking about 30-40 pixels below that. Every rollover/ textfield/ anything interactive, will only respond if I touch 30-40 pixels above the actual hit area.
It's like somehow, when the application did the "pan", the distance that it panned is now the distance I have to put my finger above each button to interact with it.
This does not happen if I change it to
<softKeyboardBehavior>none</softKeyboardBehavior>
but now I dont get the panning....
This only happens in GPU mode, in CPU mode, using none or pan works correctly as expected.
Now lets see watch the view count for this post rise with no replies ever!!! yay
I even made a video to show the craziness: http://www.youtube.com/watch?v=0KtPWW6sHlg

I think I determined the source of the bug, and how you can replicate it without flaw.
The key to the bug is the "Android Back Button" once the keyboard has been raised.
Here's how to replicate:
Run the app
Turn it to an orientation where at least 1 of the textfields would be below where the softkeyboard would raise.
Click on that textfield to raise the softkeyboard.
Do no click another textfield and do not click on the stage to lower the keyboard. Instead click the "android back button" to lower the keyboard. Now try to press any of the textfields to raise the keyboard... no luck...now your locked.
Me replicating the bug on 2 devices: http://www.youtube.com/watch?v=z313_0qJ39c
Download the sample app here: https://dl.dropboxusercontent.com/u/67123506/PanGPUTextFieldBug.zip

Textfield bug in Flash CS4 and Flash Player?

Hi there,
I'm goning mad about this, hope someone can help. What's the problem..
I have a textfield on the stage (100% view). When I place a vertcal line at the end of the text and I zoom in to 200% the text in the textfield is somehow smaller!
How is this possible???
This problem doesn't only occur in Flash Pro but also in the Flash player in the browser.
I tested this with Flash Pro on my Macbook Pro, and on serveral browsers (mac and windows). All the same zoom problems.
You can find an example here: http://www.ninos.nl/flash/flash-fonts.html
In this example you can zoom in from the flash context menu and you will see the problem.
It looks like this strange zoom in 'bug' only occurs with textfields. Not with other elements on the stage.
Am I doing something wrong here?
I noticed this when I tested for a collision between a dynamic textfield and an object. On screen I saw the text overlap the object so there must be a collision. But there wasn't. After a zoom in in I saw a different thing. The text didn't overlap the object!! After a zoom out the text overlapped the object again.
Very weird!
Hope someone can help here.
Thanks!
Peter

Hi there,
I found it!
I never thought that this would solve my problem but here it comes..
I used this setting for my textfield: AntiAliasType.ADVANCED.
I must say that it looks great on screen, but that generates my problem when zooming in and test on collision.
When I changed this setting to AntiAliasType.NORMAL it all works like it should be. The text looks less nice but I can live with that..
Very strange.. but solved Hope this can help someone else. Still think that this is a bug
Cheers Peter

Major CS5 bug where Smart Objets get thin horizontal lines??

Our prepress company has come across and proven out a rendering bug in Photoshop CS5 for Mac. It has caused us to consider totally avoiding CS5 until it's fixed. We are finding that CS5 is putting in several randomly generated thin horizontal lines about a pixel in height and varying widths, in cases where CS4 does not. Some files get these lines when converting live "smart objects" from one ICC colorspace to another.
I am providing a link to a specific file that shows proof of this bug. The example file has an embedded sRGB profile. To see the bug, set you working RGB colorpsace to AdobeRGB, and set your Policies to "Ask". During opening, USe the embedded profile. Then convert it to the AdobeRGB 1998 colorspace using File Convert, and do not rasterize the smart objects. You will see lines in the lower right hand corner after it's converted. Now go back and rasterize the smart object layers first, and these lines will not show up. And now do the same with CS4, without rasterizing the smart objects and you will not get lines. CS5 bug, CS4 no bug.
Let me know what you find on your end. Can any of the adobe employees document this for me and get it on the fix list?
Test file:
http://www.mediafire.com/?ant3ya9aaft1a95

I also head a Graphics/Prepress department at a medium format digital print shop, with next day service to the casino industry. My two cents worth, CS4 did not have this issue, CS 4 was a Cocoa app and CS5 a Carbon app, to me that is not a reason why a major software company like Adobe has multiple leading products (PS, ID, Ill) that cause these kind of problems. I can't count the times my print opp's have come back with a file showing lines. Now, I have told my designers that we should also be looking for the lines, now that we know about it.
I have printed fabric before and it is a pain to print one and see if there are lines in it, but which is more painful, printing one to test? Or trashing $3k worth of fabric? I know this works for one image printed x times, but multiple images printing a couple each to fulfill the job would be a huge ordeal. Adobe doesn't understand that yet. The squeaky wheel gets the grease, maybe we should all start calling tech support daily.
I saw a post suggesting rasterize pdf's in lower PS to work around, clearly an ad agency/freelance solution, not a production house solution. Opening and closing PS12 and PS11 somewhere around 15 to 20 times, per work station? We process somewhere around 40 minimum pieces of art a day, and sometimes double that. I could rant on this suggestion all day.
The bottom line is Adobe has no clue where it is coming from, they are more worried about the iPad/mobile industry right now.

Major Safari bug re: private browsing

Hi everyone, I'm encountering a major bug in Safari's private browsing mode. Basically, after you exit Safari, even if you close all previous tabs and use Settings to clear the cache, after you return again to Safari's private browsing mode it briefly flashes a screenshot/grab from random video content you viewed prior. There doesn't seem to be any way to clear this ... any suggestions? I just tried resetting all settings and that didn't work. Side question: does Safari's cache automatically clear after a certain point in time, i.e. 30 days after site visits and content gets stored? Many thanks in advance for all input!

Same here!
I have ghost images which sometimes appear randomly when starting or returning to Safari. They last one or two seconds then go away. I can't really define a pattern but it happens quite frequently...
Tried clearing the cache and cookies but I didn't do anything as the problem still occurs.
Apparently this issue has been known for quite some time and everyone is waiting for it to be fixed.
See more here : Safari on ipad2 ios7 does not clear cache or history properly
Come on. How hard can it be to ask iOS to delete ALL the files in a specific folder?

Major JavaScript bug - form variables not submitted

I'm building a page where data is submitted to Paypal via a form and using Javascript to build Select statements on the fly. These appear as expected, but when the form is submitted none of the variables are POSTed through. The same page works perfectly in IE so there must be a major bug in Firefox's impementation of Javascript - this is a total show-stopper for the page I need to implement.
Go to the URL below and then check availability for type of room ANY. On the booking confirmation page if you leave the first select alone and hit the Pay Now button you will arrive at a debug page that dumps all the POST variables in a new window. Now go back and change the room type in the first select statement just above Pay Now - this updates the second select. Maybe even click it again to go back to the original setting. Now click Pay Now - nothing comes through from the select statement and some associated hidden vars.
Try it in IE and it works just like it should.
== URL of affected sites ==
http://www.west-end-bb.co.uk/test/

Found this which has solved the problem:
[http://www.infoqu.com/dev/javascript-development/crazy-firefox-javascript-bug-156760-1/]
There seems to be an issue with FF and InnerHTML when a form is in a table. By moving the form tag around I was able to place it within the table definition so that it works in FF.

Selection color of TextField in AIR

hi there,
i was wondering why the TextField's selection color in AIR is different from the one in the flashplayer - and if there is a way to change it?
who chose a grey tone as highlight color, and an even lighter grey when the TextField lost its focus? seems like a strange decision to me..
cheers

Look in the documentation in the styles section.
Sincerely,
Michael
El 15/05/2009, a las 5:26, kRizzl0r <[email protected]> escribió:
>
hi there,
>
i was wondering why the TextField's selection color in AIR is
different from the one in the flashplayer - and if there is a way to
change it?
who chose a grey tone as highlight color, and an even lighter grey
when the TextField lost its focus? seems like a strange decision to
me..
>
cheers
>

IOS7 Orientation/AspectRatio Bug AIR 3.9

I have discovered a new bug in AIR 3.9 on iOS7. I am testing on iPAD2
How to replicate:
Create an app that auto-orient to any direction.
Create 1 button at the very top left that when clicked runs the following code: this.stage.setAspectRatio(StageAspectRatio.LANDSCAPE);
Hold your device in portrait mode with the home button at the bottom.... and run the app.
When the app boots up, click the button on the top left.
The app begins to rotate from portrait to landscape (as expected) but there is a problem. The stage has somehow offset itself.
The top left of your screen is no longer 0,0..... it is now 20,-20 (making your entire app look misaligned)
Here are some screenshots for proof (I outlined them so you can see the stage size)
Portrait mode before clicking the button:
Landscape Mode After clicking the botton:
I made my button with rounded corners so that you can see it being off the stage.
I tried this on Android and it doesnt seem to happen.. I'm guessing maybe this has something to do with the iOS Taskbar change.... because the amount it is offset is 20, (the taskbar height in non-retina)... though I'm not sure why it's offseting the X
Here is the project if you want to test it yourself:
http://www.filedropper.com/forcelandscapeorientation
Anyone else experienced this?

Yup we are also getting the same problem
(https://bugbase.adobe.com/index.cfm?event=bug&id=3658334)
But for us it is 100% reproducable on Ipad, Just rotate the device when the splash screen is visible and it crashes , we even tried to disable rotation but does not help. this bug only happen in IOS7/AIR3.9

Android - StageWebView - Loading PDF Bug - AIR 3.9

I think I've discovered another bug in AIR 3.9. Tested on Galaxy S4, and Nexus 7
When using the StageWebView on Android, PDFs will not load correctly. This works correctly on iOS and Desktop.
a Event.Complete event is dispatched, but all you ever see is a white square with Zoom buttons on the bottom right.
Has anyone else ever experienced this?
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               applicationComplete="init()"
               xmlns:s="library://ns.adobe.com/flex/spark" applicationDPI="160">
    <fx:Script>
        <![CDATA[
            import spark.components.Application;
            public function init():void{
                this.stage.scaleMode = StageScaleMode.NO_SCALE;
                this.stage.align = StageAlign.TOP_LEFT;
                var webView:StageWebView = new StageWebView();
                webView.stage = this.stage;
                webView.viewPort = new Rectangle(50,50,this.stage.stageWidth-100, this.stage.stageHeight-100);
                webView.addEventListener(Event.COMPLETE, this._onLoadComplete);
                webView.loadURL("http://labsdownload.adobe.com/pub/labs/flashruntimes/shared/air4-0_flashplayer12-0_release notes.pdf");
            private function _onLoadComplete($event:Event):void{
                trace("COMPLETE");
        ]]>
    </fx:Script>
</s:Application>

I have also this problem on GalaxyTab2 10.1, Android 4.0.3, Air 3.9.0.121
Complied with Air3.9, Asc 2.0.0.354071
webView = new StageWebView(true);
webView.stage = this.stage;
webView.viewPort = new Rectangle(0, 0, stage.stageWidth, stage.stageHeight);
webView.addEventListener(LocationChangeEvent.LOCATION_CHANGE, _onLocationChange);
// webView.loadURL(new File(new File("app:/pdf/arbo.pdf").nativePath).url);
webView.loadURL("http://www.spacex.com/sites/spacex/files/hyperloop_alpha-20130812.pdf");
// webView.loadURL("http://www.google.com");
11-16 14:31:19.979: I/dalvikvm(23528): Could not find method android.webkit.WebSettings.setAllowUniversalAccessFromFileURLs, referenced from method com.adobe.air.AndroidWebView.11-16 14:31:19.979: W/dalvikvm(23528): VFY: unable to resolve virtual method 635: Landroid/webkit/WebSettings;.setAllowUniversalAccessFromFileURLs (Z)V
11-16 14:31:19.979: D/dalvikvm(23528): VFY: replacing opcode 0x6e at 0x003a
11-16 14:31:20.002: I/webclipboard(23528): clipservice: android.sec.clipboard.ClipboardExManager@418a32f8
11-16 14:31:20.033: D/FirewallPolicy(227): getURLFilterEnabled(true)
11-16 14:31:20.041: D/FirewallPolicy(227): isUrlBlocked - Policy disabled
11-16 14:31:20.041: I/ClipboardServiceEx(227): dismissUIDataDialog. service check
11-16 14:31:20.049: D/WML_SISO(23528): InitPasteboardJni
11-16 14:31:20.119: W/webcore(23528): java.lang.Throwable: EventHub.removeMessages(int what = 107) is not supported before the WebViewCore is set up.
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.WebViewCore$EventHub.removeMessages(WebViewCore.java:2475)
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.WebViewCore$EventHub.access$12600(WebViewCore.java:1217)
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.WebViewCore.removeMessages(WebViewCore.java:2587)
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.WebView.sendOurVisibleRect(WebView.java:3410)
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.ZoomManager.setZoomScale(ZoomManager.java:958)
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.ZoomManager.access$2100(ZoomManager.java:57)
11-16 14:31:20.119: W/webcore(23528):      at android.webkit.ZoomManager$PostScale.run(ZoomManager.java:1428)
11-16 14:31:20.119: W/webcore(23528):      at android.os.Handler.handleCallback(Handler.java:605)
11-16 14:31:20.119: W/webcore(23528):      at android.os.Handler.dispatchMessage(Handler.java:92)
11-16 14:31:20.119: W/webcore(23528):      at android.os.Looper.loop(Looper.java:137)
11-16 14:31:20.119: W/webcore(23528):      at android.app.ActivityThread.main(ActivityThread.java:4514)
11-16 14:31:20.119: W/webcore(23528):      at java.lang.reflect.Method.invokeNative(Native Method)
11-16 14:31:20.119: W/webcore(23528):      at java.lang.reflect.Method.invoke(Method.java:511)
11-16 14:31:20.119: W/webcore(23528):      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
11-16 14:31:20.119: W/webcore(23528):      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
11-16 14:31:20.119: W/webcore(23528):      at dalvik.system.NativeStart.main(Native Method)
11-16 14:31:20.190: D/FirewallPolicy(227): getURLFilterEnabled(true)
11-16 14:31:20.190: D/FirewallPolicy(227): isUrlBlocked - Policy disabled

Major performance issue: AIR browser is slow to load AJAX app & kills CPU

Hello,
This issue for so long. I tried to submit a ticket that was erased.
Here's someone else talking about that topic: http://forums.adobe.com/message/3896291#3896291
My question - Is there a solution ahead or I have to wait patiently that all my clients uninstall the application?

The bug referenced in that thread, AIR browser is slow to load AJAX app, is still open/to track. Based off the notes from Jian on Nov 6th, we've been able to reproduce the issue but it does not have enough votes to qualify for our current releases. We need additional users to cast their votes that this is impacting their applications.
There is a note on November 11th, that suggests that removing inset box shadows can resolve this issue in some cases. This is most likely similar to other known bugs where -webkit-box-shadow impacts performance on Windows. All cases have been deferred at this time as the solution is not trivial to address (I've personally entered this bug at least twice.)
Chris

BUG AIR Webkit : referrer empty after a redirect

Hi all,
I've noticed a bug with AIR 1.5.1 : the document.referrer is empty just after a HTTP redirection (status code 302).
As a consequence, the referer for the final page is "http://adobe.com/apollo".
I don't known if it's due to the Webkit port done by the AIR team or else a bug in the Webkit trunk.
How can I make it fixed?
Regards,
jp

This bug is not related to Flex (I don't use Flex). It's reproduced with only the AIR SDK 1.5.1 (that containins webkit version 34190). It's a pure AIR html application. Where can I post this AIR/webkit bug?

Major Graphic BUG???

FCP6/HDV appears to have the same Bug that FCP5 had for a while. Imported Photoshop files (any still format) show up looking like they are single fields instead of frames. In other words, every other scan line of pixels is not showing.
Playback Quality changes don't help. And the truly weird thing is that the same file looks perfectly fine in the Viewer, but not in Canvas.
Rendering doesn't help.
Native Photoshop, JPEG, TIFF--all look horrid. Files that played last week just fine in PS 5.x now look like a mistake.
FCP5 had this bug--similar, but not exactly the same behavior--when it was brand new, and it took Apple months to realize it and fix the mother. In FCP6 the major difference is that the still image looks horrible as soon as it is inserted in the timeline. FCP5 looked fine in the timeline in Canvas, but lost integrity when rendered or viewed running.
All effects, titles, matte painting FX, still overlays, still insertions are affected.
Please, somebody, tell me there's a switch somewhere that fixes this?
-iNova
Dual 2.5GHz G5 Mac OS X (10.4.9)

While I'm not monitoring on an external monitor, the rendered file plays back with a perfectly clear background HD image and a flawed title overlay, so it's not the reviewing apparatus or conditions. Digital Cinema review shows the effect, too. Exported QT files show it, too.
What's significant about RT is that at High, the background is fine and the overlay still is corrupted, appearing to be 1/2 vertical resolution while maintaining full horizontal res. At Medium, being 2 x 2 pixels per detail, both clean background and overlay still look the same. At 50% scale Canvas viewing they look the same, too, which is to be expected. I'm not talking about field artifacts in motion. Those are easy to see on the computer monitor.
In the Viewer window, enlarged right next to the Canvas window, and both at 100%, pixel-direct viewing, the Canvas image is corrupt and the Viewer image of the same file, thrown into the View window from the timeline, looks 100% quality.
Since the Viewer window can portray the still bitmap image while looking perfect, and can portray moving footage perfectly, the issue seems to be in something that the Canvas window's handling routines are doing with the JPEG and .psd files. Since it does the same flaw with TIFF files, it seems logical to assume that it's not the incoming format, rather it's something in the way the timeline/Canvas handles bitmaps.
Are you seeing stills pixel perfect? Scale a 6MP digital image down to 1920 x 1080 and JPEG it, importing it into FCP6. Then view that in Viewer and Canvas at 100% scale after you drop it into the timeline.
One extra oddity; PS files import into the Browser as .psd format (1440 x 1080= exact resolution) self-contained sequences.
That's the way they show up normally--and must, if they had layers. If you double click on the source .psd file, opening it as a sequence, it shows up in its own timeline, and in the Canvas without the mangled look. It looks right.
But drop that source file into another timeline--the way you must to use it in an edit--and the corrupt appearance returns.
So we can add a new bit of mystery solving: It's possible for the Canvas to see a still image file with clarity--IF that file was imported as an existing sequence, the way .psd files do. But somehow still files of several formats can land in the timeline with this flaw. Making titles in Photoshop very ugly. Plus this: Do anything to the OK looking .psd image and render that--poof! The flawed appearance returns.
I'll bet Premiere doesn't make this mistake.
It's not a scaling artifact. It has the look of an image minus every other scan line, showing dramatic aliasing on shallow angle contours and loss of vertical resolution only.
Too much head scratching.

MAJOR TM Bug found in 10.6.1! Time Machine corrupts HFS+ Filesystem! Raid 0

Hey there,
i guess i just found a major bug in 10.6.1 and Time Machine which will corrupt the whole Partion which was selected for the Time Machine Backup.
This is what i got here atm:
2x Western Digital MyBook Mirror Ed. (ext. 2TB Raid0 HDD (2x1TB))
1x Mac Pro running 10.6.1
1x Macbook Pro running 10.6.1
1x Mac Mini running 10.5.8
Ok here we go:
I just updated to Snow Leopard a few weeks ago and wondered why my always working WD MyBook was not working as a Time Machine Backup Partition anymore.
Everytime i started a backup it failed after 10 gig or so. After reading all over the troubleshooting and this forum i am a 100% sure that this is not a usually bug like not formatting the hard drive to GUID Mode or so.
Well... i tried the second MyBook.. same result on both Macs running 10.6.1
Now i got suspicious and opened the MyBook in order to put those 2 HDDs in my Mac Pro and built a 2TB Raid0 via OSX.
Guess what? Same result when running Time Machine! Running Time Machine on a single 1 TB HDD was working perfectly fine.
No i just remebered that there was a Mac Mini hooked up to my TV that was still running 10.5.8 just because of Plex... Hooked up BOTH MyBook Mirror Editions and both worked perfectly fine!
Now where can i report this error? I have no doubt that Time Machine on 10.6.1 is corrupting the HFS+ Filesystem when the partition is a RAID 0 Partition.
Please let me know what you think and where i can report this bug. Anyone knows if this one is already fixed in 10.6.2?
Thanks!
André

Yeah i did check the firmware updates for both mirror editions. Both are up to date. What botheres me is that they are not working aswell when they are out of their enclosure and directly built in to the mac pro. Can this really be a firmware issue then?
From what I've read on repair/recovery sites, WD does put some of their firmware on a special part of the drive's platter itself. So it's still possible to have instructions on the actual disk that can create a problem. I do not know if this is causing your issue, it's just something I became aware of when shooting trouble on some MyBook/Mac issues. There are some WD enhancements to power management that may be problematic for Time Machine. I don't really know the whole story, just relaying what I've read.
It's also possible that 10.6.2 (in beta) will help with an issue like yours. In our machines we've been using Hitachi and Seagate and the occasion Samsung drives for the last few years. Our external closures come from OWC and we haven't had any of the firmware issues that happened with the Leopard release and WD and now maybe the SL release.
The only way I would be able to point a finger right now would be to swap in a couple of other drives and see how they work. Right now it doesn't matter who's at fault, Apple or WD. The drives don't work. If it's a problem with your installation you may be able to determine that by doing the above tests. If it's a problem with Apple's drivers there may not be a repair possible or a future update will be required. The same goes for the WD drives.
Sidenote: For our own network, we have decided to do away with Leopard Server on an old Dual G4 1.42 tower and use our new ReadyNAS drive from Netgear. It's already working perfectly with Time Machine for several computers, file storage for PC/Mac/Linux, torrent download machine, basic web server, etc. We've put in 4 1TB drives and got 2.7TB of redundant hot swap raid. We'll replace the 1TB drives with 2TB drives, one at a time (although the available space won't increase until all 4 drives are swapped in), while the NAS is online, to increase our storage as required and the drives come down in price.
We decided that if the data is important then a striped 2 drive volume isn't safe enough. We would have needed to mirror the drives and loose half the space and still have to keep the old server online.
I'll watch this thread for information from others. I don't have the drives you are using to test with.

Apple Released iOS 7.1 with Major AirPlay Bug Fix

Apple released iOS 7.1 with interface refinements, bug fixes, improvements and new features on Monday. But has the Airplay bug been fixed?
During the test of X-Mirage, we have found that AirPlay on iOS 7 is not as stable as on iOS 6 and we have reported a serious bug to Apple:
iOS 7 BUG – The devices stop sending mirroring data to Apple TV or X-Mirage one minute after iOS devices auto-locks
https://discussions.apple.com/thread/5468657
After using the iOS 7.1 today, we find that Apple has fixed the bug and AirPlay is more stable than before, so our distinguished X-Mirage users, you can update to iOS 7.1 freely and enjoy more fantastic AirPlay Mirroring and Streaming services. Getting the update is easy. Go to Settings. Select General. And tap Software Update.

thanks for the information?

Major textfield bug AIR 3.7/3.8 on Android

Similar Messages

Maybe you are looking for