Otsikkoa on muutettu jälkikäteen vieläkin paremmaksi
Otsikkoa on muutettu jälkikäteen vieläkin paremmaksi: ”Nokialta uutuus: Langaton lataus onnistuu nyt langattomasti”.
Otsikkoa on muutettu jälkikäteen vieläkin paremmaksi: ”Nokialta uutuus: Langaton lataus onnistuu nyt langattomasti”.
Oli todella edullinen ja hintaansa nähden oikein hyvä laite. Asetuksissa ihan tarpeeksi säätöjä ja toisaalta asennus niin helpoksi tehty että onnistuisi vaikka isomummulta. 1-2 hengen peruskäytössä täysin riittävä.
Tulin valinneeksi kantamankin eikä sitä näköjään saa enää poiskaan, joten olkoot ”Erinomainen”. Ainakin yksiön sisällä langaton on toiminut hyvin, mutta sen laajemmalla alueella en sitä siis ole testannut.
I couldn’t figure out how to add this to my existing report about the crash. Here’s the log:
08-23 13:49:39.280: I/ActivityManager(1385): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.example.lico_update/.MainActivity bnds=[245,252][355,370] } from pid 1476
08-23 13:49:39.522: I/ActivityManager(1385): Start proc com.example.lico_update for activity com.example.lico_update/.MainActivity: pid=4561 uid=10129 gids={3003}
08-23 13:49:39.522: E/dalvikvm(4561): could not disable core file generation for pid 4561: Operation not permitted
08-23 13:49:39.585: D/dalvikvm(4561): Debugger has detached; object registry had 1 entries
08-23 13:49:39.764: D/dalvikvm(4561): GC_EXTERNAL_ALLOC freed 56K, 49% free 2653K/5123K, external 2734K/2773K, paused 50ms
08-23 13:49:40.077: I/ActivityManager(1385): Displayed com.example.lico_update/.MainActivity: +567ms (total +2m11s892ms)
08-23 13:49:43.827: I/ActivityManager(1385): Starting: Intent { cmp=com.example.lico_update/.ActivityEnterData } from pid 4561
08-23 13:49:44.342: I/ActivityManager(1385): Displayed com.example.lico_update/.ActivityEnterData: +482ms
08-23 13:49:45.475: D/dalvikvm(1464): GC_EXTERNAL_ALLOC freed 259K, 43% free 5098K/8903K, external 3717K/3882K, paused 102ms
08-23 13:49:45.983: D/ConnectivityService(1385): getMobileDataEnabled returning true
08-23 13:49:46.069: I/ActivityManager(1385): Starting: Intent { cmp=com.example.lico_update/.getSysInfo } from pid 4561
08-23 13:49:46.124: D/ConnectivityService(1385): stopUsingNetworkFeature for net 0: enableMMS
08-23 13:49:46.124: D/ConnectivityService(1385): ignoring stopUsingNetworkFeature - not a live request
08-23 13:49:46.131: I/dalvikvm(4561): Could not find method android.view.Display.getSize, referenced from method com.example.lico_update.getSysInfo.onCreate
08-23 13:49:46.131: W/dalvikvm(4561): VFY: unable to resolve virtual method 3610: Landroid/view/Display;.getSize (Landroid/graphics/Point;)V
08-23 13:49:46.131: D/dalvikvm(4561): VFY: replacing opcode 0x6e at 0x0078
08-23 13:49:46.171: I/System.out(4561): Could not parse java.lang.NumberFormatException: unable to parse 'null' as integer
08-23 13:49:46.233: D/AndroidRuntime(4561): Shutting down VM
08-23 13:49:46.233: W/dalvikvm(4561): threadid=1: thread exiting with uncaught exception (group=0x40018560)
08-23 13:49:46.249: E/AndroidRuntime(4561): FATAL EXCEPTION: main
08-23 13:49:46.249: E/AndroidRuntime(4561): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.example.lico_update/com.example.lico_update.getSysInfo}: java.lang.RuntimeException: java.io.IOException: Error running exec(). Command: [uname, -m] Working Directory: null Environment: null
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1696)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1716)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.ActivityThread.access$1500(ActivityThread.java:124)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:968)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.os.Handler.dispatchMessage(Handler.java:99)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.os.Looper.loop(Looper.java:130)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.ActivityThread.main(ActivityThread.java:3806)
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.reflect.Method.invokeNative(Native Method)
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.reflect.Method.invoke(Method.java:507)
08-23 13:49:46.249: E/AndroidRuntime(4561): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
08-23 13:49:46.249: E/AndroidRuntime(4561): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
08-23 13:49:46.249: E/AndroidRuntime(4561): at dalvik.system.NativeStart.main(Native Method)
08-23 13:49:46.249: E/AndroidRuntime(4561): Caused by: java.lang.RuntimeException: java.io.IOException: Error running exec(). Command: [uname, -m] Working Directory: null Environment: null
08-23 13:49:46.249: E/AndroidRuntime(4561): at com.example.lico_update.getSysInfo.Command(getSysInfo.java:349)
08-23 13:49:46.249: E/AndroidRuntime(4561): at com.example.lico_update.getSysInfo.onCreate(getSysInfo.java:207)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
08-23 13:49:46.249: E/AndroidRuntime(4561): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1660)
08-23 13:49:46.249: E/AndroidRuntime(4561): ... 11 more
08-23 13:49:46.249: E/AndroidRuntime(4561): Caused by: java.io.IOException: Error running exec(). Command: [uname, -m] Working Directory: null Environment: null
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.ProcessManager.exec(ProcessManager.java:224)
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.Runtime.exec(Runtime.java:189)
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.Runtime.exec(Runtime.java:275)
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.Runtime.exec(Runtime.java:210)
08-23 13:49:46.249: E/AndroidRuntime(4561): at com.example.lico_update.getSysInfo.Command(getSysInfo.java:336)
08-23 13:49:46.249: E/AndroidRuntime(4561): ... 14 more
08-23 13:49:46.249: E/AndroidRuntime(4561): Caused by: java.io.IOException: Permission denied
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.ProcessManager.exec(Native Method)
08-23 13:49:46.249: E/AndroidRuntime(4561): at java.lang.ProcessManager.exec(ProcessManager.java:222)
08-23 13:49:46.249: E/AndroidRuntime(4561): ... 18 more
08-23 13:49:46.256: W/ActivityManager(1385): Force finishing activity com.example.lico_update/.getSysInfo
08-23 13:49:46.772: W/ActivityManager(1385): Activity pause timeout for HistoryRecord{408cffb0 com.example.lico_update/.getSysInfo}
08-23 13:49:46.983: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:46.983: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:46.983: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:46.983: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:46.983: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:47.046: D/dalvikvm(1476): GC_EXTERNAL_ALLOC freed 494K, 55% free 3559K/7815K, external 14930K/15135K, paused 65ms
08-23 13:49:47.061: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:47.061: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:47.061: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:47.061: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:47.061: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:47.092: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:47.092: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:47.092: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:47.092: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:47.092: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:47.100: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:47.100: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:47.100: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:47.100: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:47.100: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:47.288: I/ActivityManager(1385): No longer want com.google.android.partnersetup (pid 2922): hidden #21
08-23 13:49:48.616: I/Process(4561): Sending signal. PID: 4561 SIG: 9
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:48.803: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:48.835: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.835: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.835: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:48.835: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:48.850: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:48.850: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.866: D/RemoteGridViewAdapter(1476): queryBrowserDatabse is called
08-23 13:49:48.866: D/RemoteGridViewAdapter(1476): getView method is called,position is 0bmTtile is Yle Uutiset | yle.fi
08-23 13:49:48.866: D/RemoteGridViewAdapter(1476): bmUrl is http://beta.yle.fi/m/Count is:3
08-23 13:49:48.866: D/RemoteGridViewAdapter(1476): Thumbnail is present
08-23 13:49:48.897: I/ActivityManager(1385): Process com.example.lico_update (pid 4561) has died.
08-23 13:49:48.897: I/WindowManager(1385): WIN DEATH: Window{40a7e500 com.example.lico_update/com.example.lico_update.ActivityEnterData paused=false}
08-23 13:49:52.389: D/dalvikvm(1655): GC_EXPLICIT freed 9K, 54% free 3219K/6919K, external 2357K/2773K, paused 70ms
08-23 13:49:57.233: W/ActivityManager(1385): Activity destroy timeout for HistoryRecord{408cffb0 com.example.lico_update/.getSysInfo}
08-23 13:49:57.319: W/ActivityManager(1385): Activity destroy timeout for HistoryRecord{4087a678 com.example.lico_update/.ActivityEnterData}
08-23 13:49:57.421: D/dalvikvm(2595): GC_EXPLICIT freed 415K, 50% free 3719K/7367K, external 2357K/2773K, paused 91ms
08-23 13:50:00.006: I/ActivityManager(1385): No longer want com.motorola.blur.home.other (pid 2334): hidden #21
08-23 13:50:00.014: I/ActivityManager(1385): No longer want com.motorola.bookmarkswidget (pid 2351): hidden #22
The application starts, but after entering my lico id (without a machine number and update key, to create a new device) and tapping ”Get system information”, it crashes (”The application lico-update(process com.example.lico_update) has stopped unexpectedly.”).
I guess it’s noteworthy in this context that Linus went the officers-in-reserve route during his time in the Finnish Army. The Finnish Army markets itself as the Finnish school for leadership skills, and the (nowadays supposedly old-school) style of leadership it has traditionally taught is Management by perkele.
The ”Filing bugs when off-line” section of the bug reporting community help can be applied here:
First, on the target system, gather the information in a file:
- For a bug report about a system crash:
apport-cli -p <package name> --save bug.crash- For a bug report about any other issue:
apport-cli -f -p <package name> --save bug.apportYou will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the
.apportor.crashextension.When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report:
ubuntu-bug -c <apport_file.extension>
I know I can file a bug report on the local machine by running `ubuntu-bug`. But what about when I have a bug on another computer elsewhere so that it’s not convenient to get to it physically to file a report there? Can I use Ubuntu’s bug reporting tools to gather data about the bug remotely, transfer that data to my local machine and submit a bug report here with the data from the other system?
This looks slightly more straightforward than thebodzio’s method, so I’m picking this as answering my original query for ”easiest”. For some reason both Colorify and Colorize have been translated as ”Väritä” in my (Finnish) locale, so it would’ve been difficult to realize it’s actually two different functions. They’re not particularly easy to tell apart in English either…