Re: unique audiovisual experience?

>ElReg did a "walk-through" for Office 365,

Does a video of a desktop application include lots of animation, sounds, music etc that are owned by the application's creator?

I would argue that recording the screen of a desktop application is a little bit different than recording a game that contains significant amounts of graphical and audio content.

Re: unique audiovisual experience?

The have adverts on their website etc too. I don't think Nintendo is claiming any right to that even though that revenue is going to be partially generated from their uploads that contain other people's content.

Yes, it would be nicer if Nintendo did offer to share revenue but I suspect youtube is setup in such a way that if a copyright owner makes a revenue claim they get all of it because it's mostly setup to handle people uploading music videos etc.

Re: Conversion

>Fedora continues to become less stable

Fedora uses need to complain louder about having Lennart's next big code fart forced upon them time and time again really. Everyone else is very sick of the Fedora guys taking over critical things like udev and screwing them up.

>So, I read this article and the other Debian article with interest,

>especially in terms of it not being updated all the time.

A lot of "desktop" Debian users run testing or unstable from my experience. Some people run stable + backports but if you don't mind getting your hands dirty sometimes testing is pretty good IMHO.

Re: It was a pig to install.

Please take the time to install reportbug and report the issues you found so that fixes go into updates.

Re: Problem is tho

If you're moaning about experimental breaking stuff you shouldn't be touching it.

Re: Taped up

>unless someone here speaks fluent Japanese and can translate the original article,

I would have a go at reading the original article.. but guess what? The link doesn't actually work. You have to wonder if Phil actually checks all the articles he reposts from RocketNews24.

From the source that RocketNews24 "translated" which is a digest of the original article that doesn't seem to exist;

ネット接続口をテープで覆うなど

This reads "Cover the network connection with tape *etc*".

Maybe they could get rid of the 3 or 4 people (or same person with multiple accounts?) that brings up Eadon in the comments section of every article? I'm starting to think you guys have a crush on him as you can't stop bringing him up or slavishly following his posts.

The mk808 doesn't have i2c, spi, masses of gpio or the BB's gpmc.

The mk808 also only has very out of date kernel sources available and rock chip has no interest in actually respecting the GPL. Those TV sticks are fine if you to mess around with android but you can't use them for serious business (tm).

Re: Here's How It Should Have Been Done

DNS is UDP port 53. I'm not sure trying to act as if you're some sort of networking genius but not taking a few milliseconds to google "DNS port" gives me any faith in your firewall advice.

Re: @Daniel Palmer

I have some really old Java code that runs on 1.4 up to the latest openjdk6 and 7 releases.. I'm sure the is code out there that will run on all of those and embedded jvms. There is a lot of C code out there that only compiles and runs correctly on a vendors build of GCC from a specific snapshot. Python seems to break apps with each point release. This is a common issue all the way through the stack all the way down to the hardware.

Re: Backwards compatibiliy

Do you get frustrated with <insert instruction set here> when a certain chip behaves slightly differently, has bugs/different bugs or triggers unwanted behaviour because some code depending on an undocumented feature that it doesn't have? Backwards compatibility is nice to have but there isn't going to be a system in existence that has 100% perfect backwards compatibility.

Re: Not just your key

Debian supplied blacklist packages so that known insecure keys couldn't be use to autheticate.. other distros/system admins could have implemented those blacklists too if insecure debian keys was a major problem for them.

Re: One culture where it might work?

>Witness the recent palaver over a member (Minami Minegishi, age 20) of AKB48

That isn't really a reflection of any "Japanese culture" thing.. she's an idol and it's in her contract not to have a boyfriend or at least not get caught with one. Putting aside whether such a contract is acceptable or not ... I guess the reason she went insanely over the top with her apology is because she didn't want to get kicked out of AKB48 and lose all of the various TV spots she has because of that...

Re: To the 'Honourable' Minister of Internal Affairs and Communications

グーグルで翻訳したら？

Re: Strangely relevant

>Problem is, I wrote it the program in C for Windows using SDL libraries.

I guess this is SDL 1.2? The 1.2 port for Android was a hack AFAIK.. you should try 2.0. You will need to rework a lot of code but 2.0 works fairly well on Android and it fixes a lot of hairy bits in SDL.

>throw it through the Android SDK / NDK and run it as a "Android" thing, as far as I'm aware,

It's not as easy as that but it isn't too hard either.

> written in C, was made to run under Android in this way: http://chris.boyle.name/projects/android-puzzles) .

From the source it looks like some Java for UI level stuff and a bit of JNI calling into some existing C code. With SDL 2.0 your codebase can be totally C aside from a single Java class to startup/setup SDL and jump into your code. The Java + some bits of JNI'd C code isn't actually that bad of a solution though.. it's not "portable" though.

Re: This is not about phones

>The host instruction set shouldn't matter.

Of course it matters.. the Windows executable is machine code for a certain instruction set..

>From what I can tell it's running on an Android emulator,

That doesn't really matter. Except for being slow as hell the Android emulator is just the same as a regular Android device running a debug build of Android. If you run an ARM AVD it's emulating a complete ARM system (which is why it's slow).

>and is working to translate Win API calls to Android API calls.

Windows executables aren't shell scripts. They might just call APIs which are reimplemented in Wine but this is all on the machine code level. To run x86 Windows executables you need to be able to run x86 code.. there is no way around that. If the host isn't x86 you have a lot more work fitting the host and the hosted Windows application together.. It isn't impossible but it's not simple at all.

>This isn't new, there was a version of WINE running on Mac PowerPCs

> before they switched to x86 (DarWINE?)

I'm sure someone tried to with a X86 emulator into Wine at some point but I think darwine only ever targetted x86 macs.

Re: Daniel Palmer

>While the emulator is a dog, even the recent versions that run much better than older ones,

That is certainly true. For me the GPU rendering made a huge difference. It's annoying to use with all of the weird artifacts in the emulator display but at least I can actually test against OS releases I don't have on a real device. It's a shame the 4.1 and 4.2 images are currently broken beyond use with all the Trace junk..

>It's not a good line that it "runs perfectly on my Nexus 1". Runs and runs efficiently are entirely different.

I use a few phones for profiling (when it's needed, most of the time it just works because I know what to avoid doing..). My "if it runs on this it'll run anywhere" device is a really crap ARMv6 with no 3D hardware phone running some hacked 2.1 ROM. There are things that perfect on that POS but struggle in the emulator with GPU rendering on a 2ghz+ machine.. simple things like updating a Canvas really fast so the user can draw something in realtime.

Re: Yet another bad research paper

Phil's "articles" are basically copy and pastes of press releases with all of the important details cut out and then no link to the original.

The original press release is here;

http://www.fujitsu.com/global/news/pr/archives/month/2013/20130129-02.html

It specifically states "New protocol improves throughput and latency in low-quality communications environments".

Re: But how ill it look on a phone?

>Will it look good on a 4" smartphone screen?

Why not.. as long as the phone is fast enough to decode and scale it..

but small mobile devices is what 1seg is for; http://en.wikipedia.org/wiki/1seg

Re: I just created this account to say this...

I think a lot of reporting on stuff "in Japan!" is intentional mis-reporting to make things seem more weird/unusual than they actually are.

Re: Cooking with Google: one of the simplest appliances possible ...

>The Japanese invented the electric rice cooker, and Apple copied their safety connector.

I'm not sure the magnetic connector was invented for rice cookers as many people seem to think. We have an induction hot plate and hot water pot with the same connector. Japan has a bunch of standard connectors that I haven't seen anywhere else.. for example if you rent an apartment that isn't furnished you probably won't get any lights in the rooms. Instead you get a modified AC socket with locking supports in the ceiling.

>Cooking rice is not such an easy job.

It's not so hard to get edible cooked riced but the Japanese can be very anal about their rice which is why there are rice cookers for about 50 quid for the "don't cares" and several hundred quid cookers for the people that want the "traditional cooked in a massive pot by a jiji" flavour. Considering there are hot water pots that can be remote controlled so that your elderly parents don't go without hot water (saw it advertised on TV yesterday) I don't see a rice cooker with Android as being all that "weird".

Re: Java is the real problem.

>The simplest answer is to stop using Java like it's a blood line, or at least the only option.

>I will never understand how the Android NDK isn't a top priority for Google.

What does the NDK not do now that you want it to do? I have no problems using the NDK for what it's intended for; Creating shared libraries containing performance critical or ported code to interface with via JNI.

>Google: "In general, you should only use the NDK if it is essential to your app—

>never because you simply prefer to program in C/C++."

The UI framework is all written in Java... NativeActivity exists for applications (activities) that don't want any of the Java APIs like the UI framework.

>You can almost count the days until Google puts out a press release in regards to the

>NDK that will read "This is how it should be done".

For games there is no reason not to go 100% native (although you can write pretty decent games in Java via libgdx) and there is an SDL port that mostly works if you want it to be "portable". I very much doubt google are going to start promoting C/C++ as the way to develop apps considering all of the high level APIs are implemented in Java and the libraries you use to get access to stuff like the screen, sound etc are limited and vary between versions of Android.

I think the point you were trying to make is; Java == Easy piracy. Java can be reverse engineered but so can C. You should take a look at something like IDA (http://www.hex-rays.com/products/ida/index.shtml). The issue with a lot of cracked Android apps was that the dev only called the license check once at start-up and used google's code without making any changes.. and then didn't use proguard so it's very easy to remove the single license check. A similar issue but for "applications" written in assembly or C is "save patching" in console backup units. Backup units don't have all of the different backup types that are possible.. they rely on the fact that game developers link against a library supplied in the SDK to handle the backup storage.. so all the patcher needs to do is search for a signature of the library and replace it.

Re: I'm sorry, but that's just wrong

It does seem a bit backward to be honest.. if anything they should have built a nicer apt/dpkg frontend based on Synaptic. This sort of thing (one click install from website) has been done before and I can't remember anyone using it.

Maybe this will help the kiddie winks once they actually get some to people that don't just want a cheap XBMC machine..

Re: Not a sad day

>Anyone who has a 386 processor and wants to install Linux on it now can easily download one

>of the zillions of distros that support kernel

I don't think that is true.. as someone else said glibc doesn't work on 386 anymore.. IIRC even Debian's i386 arch has only worked on 486+ for at least the last stable release, maybe the one before that.

Re: Sad day

>but this is a step in the wrong direction

I'm not sure how dumping legacy stuff that causes issues supporting the majority of users is a "step in the wrong direction". I would go further than Linus.. I would remove all of the archs and boards that haven't been touched for years and only allow them back in when someone steps up and offers to support them and can prove that they still work or are fixable.

>especially when you consider that with Linux , so much can be done with so little CPU.

If you turn off everything that makes using a recent kernel worth using..

Re: The beautiful cathedral of Unix, ...

Not sure why others have downvoted you..

For BSD at least there was/is a ton of hacky code.. there are some BSD history videos were it's clearly stated by one of the people involved early on that BSDs much lauded TCP/IP stack was a massive hack and only done because AT&T or whoever was actually contracted to do the TCP/IP stack took to long about it.

They are called "sumaho" - smart phone.

There are some low end handsets from Panasonic etc which the people that would have bought another keitai would have bought but the people being a smart phone because they want a smart phone are going for the Samsung units. I'm not sure how you saw lots of Sony phones as the carriers usually hide the brand of the domestic phones and ship them under their own brand. I.e. my KDDI IS06 is made by Pantech from Korea and my sister in laws IS04 (I think) is made by Panasonic. The only way to actually tell though is to pull the back cover off and look at the sticker under the battery.

Re: >> the day English has officially lost it's grip on the world

On a computer at least most people input Japanese via romaji -> hiragana (phonetic script) -> candidate lookup for any kanji/katakana sections of the input..

i.e. if you want to type Japan you input nihon by pressing the roman letters, the hiragana appears and then on my machine at least you press space and it usually converts it into the right symbols or you get a list of candidates ordered by probability.. once you start teaching the input method the characters you use it gets a lot faster.. So lots of key presses but I think the amount of information encoded by character balances the number of key presses required to input them... for TLDs it's not really worth it as writing out "china" in full doesn't have any benefit over typing in cn and just knowing that cn == china. I'm not sure about the Chinese but a lot of Japanese people have trouble remembering kanji for words they use in daily conversation so I can imagine this becoming a pain when you want to go to a site which you can remember the pronunciation of but you can't remember which kanji is used to write it.

Re: And the purpose of this element is...?

Just a brain fart.. but I guess that you need a syllable with an i sound to use "umu" (i.e caesium is se-shi-u-mu).

So maybe that it would be nipponi-umu. Makes more sense when you look at the words in romaji.

Re: And the purpose of this element is...?

-ium is transliterated to umu in Japanese .. i.e. Calcium is karushiumu (カルシウム) and sodium is sojiumu (ソジウム）so it would be nihonnumu or I would guess nipponnumu. (double nn == ん otherwise you would get ぬ). There are "proper" kanji words for some of the elements.. but not being a science bod I don't know when you would use one or the other. Looking at my dictionary though some common compounds use the kanji word for one part and the transliterated English or German for other parts.

Re: Japan

Food isn't too bad.. there just isn't much really cheap stuff. Imagine always shopping at Sainsbury's instead of ASDA or Tesco. Rents are pretty good outside of Tokyo. My families apartment is much nicer and cheaper than any flat I had in the UK... I guess that most of the expats that would be living here for the money opposed to anything else would be working in finance etc and won't be looking for places out in the middle of nowhere though.

Re: Only really the board though surely?

Mining raw materials != Manufacture.

Re: Only really the board though surely?

>That is the case, but if you cannot even buy UK manufactured

Doesn't change where they were manufactured..

>Just on the upbeat, the SoC contains an Arm , which was designed in Cambridge

>,and a GPU which was also designed in Cambridge.

That's lovely and all.. but this article is about the Pi being manufactured in the UK.. which most of it isn't. I don't actually see what the advantage of this anyhow... I take it pick and place machines run the same pretty much anywhere.