Template talk:Infobox mobile phone

message: Why the marketing slogan is allowed in wikipedia?
What is the value of that?
Please explain the value or remove just it.  —Preceding unsigned comment added by 81.38.126.239 (talk) 13:25, 8 May 2010 (UTC)
replies: text: As no-one has replied to this comment since 8 May, I shall remove the template section soon as per WP:PROMOTION unless someone more involved with this template does so or gives a stronger argument for its presence.   Trev M  ~  11:05, 5 August 2010 (UTC)
thread_title:  Marketing Slogan? 

message: It needs a section:Sample photo by Primary camera.So that it'll be easy to determine the quality of the camera.
Coercorash (talk) 05:10, 20 May 2010 (UTC)
thread_title:  Sample photo by camera 

message: I don't understand how to edit templates, can anyone please add a "type" field (which can be Camera phone, Feature phone or Smartphone) Artem-S-Tashkinov (talk) 00:22, 4 March 2011 (UTC)
thread_title:  Type 

message: Hi, I'm new to Wikipedia, how to add a slogan using the infobox?  — Preceding unsigned comment added by Pawlen-T (talk • contribs) 05:14, 23 August 2011 (UTC)
replies: text: I oppose to the slogan as it does not add any value as it is used for marketing purposes (wikipedia is not a marketing tool)  — Preceding unsigned comment added by 85.53.35.228 (talk) 09:02, 28 May 2012 (UTC)
thread_title:  Add slogan to infobox? 

message: There seem to be an inconsistent use of the manufacturer tag. Is the manufacturer Nokia and Apple or Compal and Foxconn? At the moment we see an emphasis on the contractor (many times in China) as a way to sheer some negative bias on the device. If the latter is true (in contrast with the template instructions), we need a new tag more clearly defining this matter clearer. --Caygill (talk) 10:16, 10 March 2012 (UTC)
replies: text: If you read Manufacturing you will see it should be Compal and Foxconn. Maybe this infobox needs a designer or developer label.  — Preceding unsigned comment added by 2.137.99.205 (talk) 18:34, 3 April 2012 (UTC)
thread_title:  Manufacturer 

message: What is the reason behind the iPhone having its own infobox instead of using "Infobox mobile phone"?
I am going to move all iPhone pages to "Infobox mobile phone" if no one disagrees.  — Preceding unsigned comment added by 2.137.99.205 (talk) 18:29, 3 April 2012 (UTC)
replies: text: Agreed. --IncidentFlux [ TalkBack | Contributions ] 19:38, 29 June 2012 (UTC)
thread_title:  Infobox iPhone 

message: Shouldn't there be a mention of whether the device has a SIM card or not? --Jerome Potts (talk) 16:41, 25 May 2012 (UTC)
replies: text: And also the size of the SIM given that devices on sale currently can have standard, micro, or nano-SIM. --Biker Biker (talk) 00:32, 13 September 2012 (UTC)
replies: text: Thirded. This is at least as pertinent as memory card type. danno_uk 22:15, 30 November 2014 (UTC)

text:  Having the SIM card type in infoboxes would be really useful. — Dsimic (talk | contribs) 18:53, 3 December 2014 (UTC)
thread_title:  SIM card? 

message: I have just nominated  for deletion as an unnecessary fork of this template. See Wikipedia:Templates for discussion/Log/2012 September 13. --Biker Biker (talk) 00:31, 13 September 2012 (UTC)
thread_title:  {{tl|Info box iPhone}} nominated for deletion 

message: Please add a "sound" field to this template, similar to the "sound" field in "Template:Infobox information appliance", such as being used in HP Touchpad article.  Why, because there is no obvious field to add "speaker" or "3.5mm headphone" jack.  Some people don't think the 3.5mm jack should be in the connectivity field, thus is why it doesn't appear on the iPhone 4S and iPhone 5 articles (and possibly more).  I would like to see more cross-compatibility between templates.  Thanks!  • Sbmeirow • Talk •  22:28, 14 September 2012 (UTC)
thread_title:  Please add Sound field 

message: Hi guys,
I just noticed that there is currently no "infobox mobile operating system". Here are the first two fields that can be added to it, once we decide to create it or not:
| label35 = Compatible media formats
| data35  = 
| label36 = Ringtones & notifications
| data36  = 
| media_formats = 
| ringtone      = 
;media_formats: list of the audio and video file formats and codecs that are compatible with the device. Example:  | media_formats = Audio AAC (unprotected), AAC+ (unprotected), AAC++ (unprotected), AMR, MIDI, MP3, WMA  Video DivX, Xvid, H.263, H.264, 3G2, 3GP, MP4, WMV 
;ringtone: Compatible ringtone and notification types - MP3, polyphonic, vibration, etc.
| media_formats = Audio AAC (unprotected), AAC+ (unprotected), AAC++ (unprotected), AMR, MIDI, MP3, WMA  Video DivX, Xvid, H.263, H.264, 3G2, 3GP, MP4, WMV
| ringtone      = All compatible audio formats  Vibration
:Instead of media_formats we should separate video codecs, audio codecs and digital container formats --Davidjonesmartin (talk) 13:23, 9 November 2012 (UTC)
replies: text: That's a very good point. However, those fields should go in the proposed "Infobox mobile phone os". The reason is this: What media formats can a Toshiba Satellite play? None at all, because it's the operating system that does that. InternetMeme (talk) 18:57, 9 November 2012 (UTC)
replies: text: For practical purposes, it is also dependent on the phone, as many current phones have hardware acceleration H.264 codecs and maybe other ones. See for example: http://reviews.cnet.com/8301-13970_7-57387626-78/qualcomm-shows-horsepower-of-next-gen-h.265-video/ Davidjonesmartin (talk) 10:06, 7 September 2013 (UTC)
thread_title:  Infobox mobile operating system 

message: I just added this field. It's become common practice, especially among Android devices, that each device is assigned a codename, which is very commonly referenced in developer texts and ROM modding discussions. The codenames are really easy to find out, but there's a readily available list right here in Wikipedia in this article. Hope everyone is OK with the addition. Cheers. --uKER (talk) 02:59, 26 December 2013 (UTC)
thread_title:  New field: Codename 

message: After looking at various articles, some fields seems out of place to me, when compared to the order of how manufacturers list their hardware features. This is a request to move 3 fields from their current locations to immediately above "website" field, in this order.  For example, look at these fields in the infobox for iPhone 6, doesn't it seem like they should be pushed further down?  Please discuss and throw rocks at me <grin>.  • Sbmeirow • Talk • 14:40, 7 March 2015 (UTC)
thread_title:  Request to move "battery" / "weight" / "size" fields to above "website" field 

message: The editor User:Davidjonesmartin, without a full consensus, added fields to this infobox for whether a phone has an unlockable bootloader and can have root access. Any attempt to remove them were met with a reversion (WP:OWN violation), and his only edits have been surrounding this template and his advocation of root access and unlockable bootloaders on smartphones ("Many people want to know if their phones allow changing the operating system", "I consider this info very important, to the point that I will not buy a phone without Root access."; WP:NOTADVOCACY).
In previous discussions, which, however did not reach a conclusion (but did show a lean towards opposition), it was argued that this fields are hard to reliably source (given that activities related to these take place on forums, which are never reliable sources) and are ultimately cruft that only serve specific, niche audiences. Wikipedia is not XDA-developers, among other things. Plus, it was argued that the fields contribute to an Android-centric POV that are not applicable to other devices.
Per the edit war, the template had been protected, and Davidjonesmartin has not returned since the last discussion. These fields have ultimately been rarely used, if not at all, so I would like to propose their removal. ViperSnake151  Talk   17:50, 11 May 2015 (UTC)
replies: text: Not done: The page's protection level and/or your user rights have changed since this request was placed. You should now be able to edit the page yourself. If you still seem to be unable to, please reopen the request with further details. I think we can try dropping this to semi-protection again seeing as Davidjonesmartin is no longer active, so the chances of another edit war are reduced. If there is any more trouble I recommend requesting protection again at WP:RFPP. — Mr. Stradivarius ♪ talk ♪ 06:43, 23 June 2015 (UTC)
thread_title:  Remove root/unlockable bootloader fields 

message: Please add color field for this infobox. It will be helpful. Ayub407 (talk) 16:19, 4 August 2015 (UTC)
thread_title: Color

message: Since slogan field has been removed from infobox company on October 2016, I propose remove this field from the infobox, with the same reason. 219.218.130.12 (talk) 04:10, 11 September 2017 (UTC)
replies: text: How widely is it used? Ruslik_Zero 19:57, 11 September 2017 (UTC)

text: Not done: please establish a consensus for this alteration before using the  template. — nihlus kryik  (talk) 02:20, 12 September 2017 (UTC)

text: I ran it through AWB and came back with 40 uses (non-empty) within the first couple hundred of pages. It's probably on about 8-10% of the pages using the template. — nihlus kryik  (talk) 02:31, 12 September 2017 (UTC)
thread_title:  Semi-protected edit request on 11 September 2017 

message: Currently in the template documentation, the two parameters have been explained as such:
| memory       = 
| storage      = 
But then, nowadays, when phone manufacturers release their phone, they rarely report the two numbers separately, and, on some phone, the number can even be dynamically adjustable by the system. In many wikipedia mobile phone articles, the two parameter are also used in other ways that are different from this description, as in for example some article used the "memory" parameter to denote the total amount of volatile memory in the device, while the "storage" parameter is used to denote the total of flash memory available on the phone regardless of purpose. Should this part of infobox be repurposed or modified? That might also need someone to go through all the mobile phone articles in wikipedia. C933103 (talk) 12:44, 24 February 2018 (UTC)
thread_title:  The "Memory" and "storage" parameter. 

message: Greenhouse gas emissions are produced through production, transport, and use of products. Including this in infoboxes will provide valuable statistics for environmentally-conscious readers. This information is publicly-published by Apple Inc. for their specific products, and is already included in List of iOS devices as a trait based on this data. I hereby request that this be included as a parameter in mobile device infoboxes. ViperSnake151  Talk   21:25, 13 February 2019 (UTC)
replies: text: I feel like this information would be generally hard to gather and might vary widely over the production cycle of a given phone FAISSALOO(talk) 20:18, 19 July 2020 (UTC)
thread_title:  Greenhouse gas emissions 

message: This is something that is missing - and is surprisingly hard to find online.  I'm sure other people look at COO labels...  They are required by law in north america for a reason... Mrybczynski (talk) 00:22, 12 March 2020 (UTC)
thread_title:  country of origin label? 

message: I'm working on the page for the Nokia C2-01 and I've realised that what's listed as a CPU is in fact a Baseband processor, is it worth having an additional parameter for this? Alot of older devices use them FAISSALOO(talk) 20:17, 19 July 2020 (UTC)
thread_title:  Baseband processors? 

message: For me and probably for a few others (https://stats.lineageos.org/) this is relevant (eventually with version).
A little less surveillance and some likelyhood that the device does not get obsolete when the vendor stops providing updates. --HeWhoMowedTheLawn (talk) 18:06, 7 January 2021 (UTC)
replies: text: Seconded. LineageOS is special among custom ROMs for supporting so many devices, often getting news coverage (from, e.g., 9to5Google) when it adds support for a new device, supporting 6+ year old devices with the latest version of Android that barely deviates from AOSP, and for having extremely high quality standards and professionalism. It's, by far, the most popular non-stock Android distribution, and I think the size of the project and its attention in Android media circles (making it citable as well) make it deserving of inclusion on device pages. It's already present in the normal OS field on the Samsung Galaxy S II and Nexus 7 (2013) pages, and possibly more, so either a separate field or officially recognizing it as a valid entry in the OS field would be great. TheQuietTortoise (talk) 01:03, 9 January 2021 (UTC)
thread_title:  supported by [[LineageOS]] field 

message: I suggest moving sound just after ext_display since sound and display seem rather linked, and moving input after connectivity (same). The RedBurn (ϕ) 17:09, 8 June 2022 (UTC)
replies: text: The RedBurn (ϕ) 18:51, 9 June 2022 (UTC)
thread_title:  sound -> after ext_display, input -> after connectivity 

message: Hey, I came across this infobox while GA reviewing Pixel 6 and wanted to leave some suggestions for improvement and recommend that someone consider what is truly needed in , with these specific comments:
* There are many data fields but no headers to logically organize their contents.
* Slogan parameters have been removed from many infoboxes, e.g. Template talk:Infobox company/Archive 11#Slogans.
* There may be too many data fields in general. See MOS:INFOBOXPURPOSE.
I speak from experience with the 2020 redesign of Infobox radio station, Infobox television station, and Infobox television channel. If you have questions, let me know. Sammi Brie (she/her • t • c) 06:27, 1 August 2022 (UTC)
thread_title:  Suggestions for improvement 

message: Any specific reason to not add to ?  — GhostInTheMachine talk to me 21:02, 15 October 2023 (UTC)
replies: text: Added the cat to the template and ref in the doc. It found 843 needing fixing  — GhostInTheMachine talk to me 15:40, 28 December 2023 (UTC)
thread_title:  Tracking category? 

message: Based on the actual parameters used by the template code, I have updated the parameter check list in the template, updated the bare example and the example with comments, updated the template data and added to the set of parameter descriptions. Please check through the descriptions and fill in any that are blank  — GhostInTheMachine talk to me 15:54, 28 December 2023 (UTC)
thread_title:  Synced 

message: Is SAR (specific absorption rate) a necessary field? I am unfamiliar with the term in smart phone products, but maybe it’s more common to reference in older generations? I would like to deprecate it, but I don’t want to miss anything if there’s some product class (sub-class) where it’s important. — HTGS (talk) 20:44, 29 January 2024 (UTC)
replies: text: Now deprecated. — HTGS (talk) 03:21, 8 February 2024 (UTC)
thread_title:  SAR (specific absorption rate)