Linked by Thom Holwerda on Thu 17th Jul 2014 17:17 UTC
Microsoft

This news will probably fall through the cracks in most reporting about Microsoft's massive layoffs, but aside from the Nokia X, Microsoft is also killing off Series 40 and Asha.

Nokia might have been famous for its feature phones, but Microsoft is planning to wind that business down over the course of the next 18 months. In an internal memo sent to Microsoft employees, Jo Harlow, who heads up the phone business under Microsoft devices, reveals the focus is very much on Windows Phone. Development and investment for Asha, Series 40, and Nokia X handsets will shift to what is described as "maintenance mode," and services to support existing devices will be shut down over the next 18 months. "This means there will be no new features or updates to services on any mobile phones platform as a result of these plans," says Harlow, in the internal memo seen by The Verge.

The story of Series 40 started in 1999 with the iconic Nokia 7110, and it will now end with the Nokia Asha 210 (I think?), or the Nokia Asha 230 if you consider the Asha Software Platform to be Series 40 (nobody really seems to know for sure just how related the two are). In 2012 Nokia announced it had sold over 1.5 billion Series 40 devices, making it one of the most successful software platforms of all time.

It makes sense for Microsoft to kill these platforms. Windows Phone handles devices with lower specifications relatively well, something which the company will hopefully only improve. It does mean the end of an iconic operating system that is intrinsically tied to Nokia, a company who spread the mobile phone and its infrastructure to all four corners in the world, paving the way for pompous phone upstarts like Apple and Google.

One small tidbit I will always associate with Series 40 and Nokia are the signal reception and battery life bars flanking the sides of the early Series 40 user interface like the pillars of the Parthenon. Beautifully elegant and clever use of the limited screen real estate available at the time.

Thread beginning with comment 592699
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: ...
by japh on Fri 18th Jul 2014 12:35 UTC in reply to "RE: ..."
japh
Member since:
2005-11-11

Someday, I would love to see a breakdown of what occupies all the RAM Android occupies. Is it the backround services? The UI? The fact every app runs inside it's own VM?


There's a linux kernel behind it all so it is possible to get information about the different processes. I'm guessing someone will have implemented something like the Linux "top" command for android.

So if you're really curious, I'm sure the data is there.

Reply Parent Score: 1

RE[3]: ...
by glarepate on Sun 20th Jul 2014 18:38 in reply to "RE[2]: ..."
glarepate Member since:
2006-01-04

"Something like" this?:

~$ adb shell
shell@ghost:/ $ top



User 2%, System 3%, IOW 0%, IRQ 0%
User 7 + Nice 0 + Sys 11 + Idle 286 + IOW 0 + IRQ 0 + SIRQ 0 = 304

PID PR CPU% S #THR VSS RSS PCY UID Name
21868 0 3% R 1 1592K 604K shell top
20802 1 0% S 57 659172K 87772K bg u0_a128 com.overdrive.mobile.android.mediaconsole
1153 0 0% S 33 592264K 66632K fg u0_a26 com.android.systemui
1029 0 0% S 86 725616K 106208K fg system system_server
400 0 0% S 25 27308K 976K root /system/bin/thermald
14456 0 0% S 1 460K 72K bg u0_a149 su
21011 0 0% S 1 0K 0K root kworker/0:2
27065 0 0% S 84 634980K 111036K fg u0_a134 com.tul.aviate
17 0 0% S 1 0K 0K root irq/203-msmdata
33 0 0% S 1 0K 0K root sync_supers
34 0 0% S 1 0K 0K root bdi-default
35 1 0% S 1 0K 0K root kblockd
36 0 0% S 1 0K 0K root msm_slim_ctrl_r
37 1 0% S 1 0K 0K root sb-1
38 0 0% S 1 0K 0K root khubd
39 1 0% S 1 0K 0K root irq/84-msm_iomm
40 1 0% S 1 0K 0K root irq/84-msm_iomm
41 1 0% S 1 0K 0K root irq/96-msm_iomm
42 1 0% S 1 0K 0K root irq/96-msm_iomm
43 1 0% S 1 0K 0K root irq/94-msm_iomm
44 1 0% S 1 0K 0K root irq/94-msm_iomm
45 1 0% S 1 0K 0K root irq/92-msm_iomm
46 1 0% S 1 0K 0K root irq/92-msm_iomm
47 1 0% S 1 0K 0K root irq/100-msm_iom
48 1 0% S 1 0K 0K root irq/100-msm_iom
49 1 0% S 1 0K 0K root irq/86-msm_iomm
50 1 0% S 1 0K 0K root irq/86-msm_iomm
51 1 0% S 1 0K 0K root irq/90-msm_iomm
52 1 0% S 1 0K 0K root irq/90-msm_iomm
53 1 0% S 1 0K 0K root irq/88-msm_iomm
54 1 0% S 1 0K 0K root irq/102-msm_iom
55 1 0% S 1 0K 0K root irq/102-msm_iom
56 1 0% S 1 0K 0K root irq/98-msm_iomm
57 1 0% S 1 0K 0K root irq/98-msm_iomm
58 1 0% S 1 0K 0K root irq/243-msm_iom
59 1 0% S 1 0K 0K root irq/243-msm_iom
60 1 0% S 1 0K 0K root l2cap
61 1 0% S 1 0K 0K root a2mp
62 1 0% S 1 0K 0K root cfg80211
63 1 0% S 1 0K 0K root modem_notifier
64 1 0% S 1 0K 0K root smd_channel_clo
65 1 0% S 1 0K 0K root smsm_cb_wq
66 1 0% S 1 0K 0K root qmi
67 1 0% S 1 0K 0K root nmea
68 1 0% S 1 0K 0K root msm_ipc_router
69 1 0% S 1 0K 0K root apr_driver
70 0 0% S 1 0K 0K root kswapd0
71 1 0% S 1 0K 0K root fsnotify_mark
72 1 0% S 1 0K 0K root crypto
89 1 0% S 1 0K 0K root mdp_dma_wq
90 1 0% S 1 0K 0K root mdp_vsync_wq
91 1 0% S 1 0K 0K root mdp_pipe_ctrl_w
92 1 0% S 1 0K 0K root mdp_cursor_ctrl
93 1 0% S 1 0K 0K root mot_panel_esd
94 1 0% S 1 0K 0K root vidc_worker_que
95 1 0% S 1 0K 0K root vidc_timer_wq
96 1 0% S 1 0K 0K root smux_notify_wq
97 1 0% S 1 0K 0K root smux_tx_wq
98 1 0% S 1 0K 0K root smux_rx_wq
99 1 0% S 1 0K 0K root smux_loopback_w
100 1 0% S 1 0K 0K root k_hsuart
101 1 0% S 1 0K 0K root diag_wq
102 1 0% S 1 0K 0K root hsic_diag_wq
103 1 0% S 1 0K 0K root hsic_2_diag_wq
104 1 0% S 1 0K 0K root smux_diag_wq
105 1 0% S 1 0K 0K root diag_cntl_wq
106 1 0% S 1 0K 0K root diag_dci_wq
107 1 0% S 1 0K 0K root kgsl-3d0
108 1 0% S 1 0K 0K root msp430_wq
109 1 0% S 1 0K 0K root msp430_quickpee
110 0 0% S 1 0K 0K root irq/353-c55_ctr
111 0 0% S 1 0K 0K root irq/350-wcd9xxx
112 1 0% S 1 0K 0K root spi_qsd.0
119 1 0% S 1 0K 0K root usbnet
120 1 0% S 1 0K 0K root mdm_bridge
121 1 0% S 1 0K 0K root ks_bridge:1
122 1 0% S 1 0K 0K root ks_bridge:2
123 1 0% S 1 0K 0K root ks_bridge:3
124 1 0% S 1 0K 0K root ks_bridge:4
126 1 0% S 1 0K 0K root k_rmnet_mux_wor
127 1 0% S 1 0K 0K root f_mtp
128 0 0% S 1 0K 0K root file-storage
129 1 0% S 1 0K 0K root uether
130 1 0% S 1 0K 0K root kpsmoused
131 1 0% S 1 0K 0K root rmi_det_workque
132 1 0% S 1 0K 0K root w1_bus_master1
134 1 0% S 1 0K 0K root mmi_batt_wq
135 1 0% S 1 0K 0K root iewq
136 0 0% S 1 0K 0K root cfinteractive
137 1 0% S 1 0K 0K root cfinteractive
138 1 0% S 1 0K 0K root binder
139 1 0% S 1 0K 0K root tfa9890
140 1 0% S 1 0K 0K root tpa6165
145 0 0% S 1 0K 0K root mmcqd/0
146 1 0% S 1 0K 0K root krfcommd
147 1 0% S 1 0K 0K root msm-cpufreq
148 1 0% S 1 0K 0K root bam_dmux_rx
149 1 0% S 1 0K 0K root bam_dmux_tx
150 1 0% S 1 0K 0K root rq_stats
151 1 0% S 1 0K 0K root deferwq
1 0 0% S 1 852K 648K root /init
154 0 0% S 1 0K 0K root jbd2/mmcblk0p38
155 1 0% S 1 0K 0K root ext4-dio-unwrit
156 1 0% S 1 0K 0K root ext4-dio-unwrit
253 0 0% S 1 0K 0K root flush-179:0
258 0 0% S 1 0K 0K root jbd2/mmcblk0p1-
259 1 0% S 1 0K 0K root ext4-dio-unwrit
262 0 0% S 1 0K 0K root f2fs_gc-259:8
267 0 0% S 1 0K 0K root jbd2/mmcblk0p36
268 1 0% S 1 0K 0K root ext4-dio-unwrit
269 0 0% S 1 0K 0K root jbd2/mmcblk0p23
270 1 0% S 1 0K 0K root ext4-dio-unwrit
273 0 0% S 1 0K 0K root kjournald
282 0 0% S 1 1196K 624K mot_pwri /system/bin/batt_health
308 0 0% S 1 1432K 4K fg root /sbin/healthd
309 1 0% S 1 1312K 596K system /system/bin/servicemanager
310 0 0% S 3 5012K 976K root /system/bin/vold
312 0 0% S 6 30260K 9804K camera /system/bin/mm-qcamera-daemon
318 0 0% S 8 11720K 2540K root /system/bin/netd
319 0 0% S 1 1292K 572K root /system/bin/debuggerd
322 0 0% S 17 25628K 3756K radio /system/bin/rild
323 0 0% S 13 61324K 7684K fg sy

Reply Parent Score: 2

RE[4]: ...
by dominik.holler on Sun 20th Jul 2014 20:34 in reply to "RE[3]: ..."
dominik.holler Member since:
2007-05-24

or maybe more eye candy app os monitor https://f-droid.org/repository/browse/?fdid=com.eolwral.osmonitor

Edited 2014-07-20 20:34 UTC

Reply Parent Score: 1