Difference between pages "Template:Device tilapia" and "Talk:Unofficial Ports"

From CyanogenMod
(Difference between pages)
Jump to: navigation, search
 
(Undo revision 14416 by Alessandro panarese (talk))
 
Line 1: Line 1:
{{{{{function}}}<!-- don't touch this line -->
+
i have a samsung double time and i would love to get a customize os to be able to use the feature
|link_kind={{{link_kind}}}<!-- don't touch this either. Used for generating links -->
+
 
|device_name=Nexus 7 (GSM, 2012 version)<!-- REQUIRED. Example: Nexus 7 -->
+
== entry level questions & purposes ==
|device_codename=tilapia<!-- REQUIRED. case sensitive - use all lower case examples: grouper, sholes, tuna, etc. -->
+
 
|device_vendor=asus<!-- REQUIRED. case sensitive - use all lower case.  Used in all directories/URLs on CM repos.  Example: htc, samsung, bn, lge, hp, etc. -->
+
I have a tablet (Craig CMP 741e Android 4.0.3),
|device_vendor_longname=Google<!-- REQUIRED. Upper and/or lower case and spaces. Example: Samsung, Barnes & Noble, HTC, LGE, Hewlett Packard, etc. -->
+
That does not respond well (10-20 sec. system hangs, 30 sec.-30 min. http-browser bangs),
|device_recovery_install_method=fastboot<!-- optional. Choose the method used to flash the recovery. Options are: fastboot, flash_image, dd, or leave blank if the flashing is covered in the CM flashing instructions (such as with most Samsung / HTC devices) -->
+
Yet it's fast (1.20 GHz on most apps, 1.15 GHz benchmark, 1.10 GHz on one crashy app),
|device_manufacturer=Asus<!-- optional. Note: This is NOT the code used in CM directories (that would be device_vendor) but is provided just for additional info -->
+
And many apps do well (streams youtube video HD 800x444, shoutcast audio at 320 kHz, b.g.),
|device_CM_versions_supported=10, 10.1<!-- optional, but you should put something here. Use major CM releases such as: 7, 9, 10, 10.1, etc. -->
+
But, not, the http-browsers (Firefox 22, Dolphin Beta, &c.), and especially-not the http-embedded youtube;
|device_last_CM_branch_supported=<!-- optional. For older devices. Change to the branch name, in lowercase, as used in the repo init. Examples: ics, gingerbread, froyo, etc. IF THIS IS NOT SET, THE LATEST VERSION OF CM IS ASSUMED TO WORK. -->
+
 
|device_aka=<!-- optional. Include any other device names. Wiki redirects can point to the same page. -->
+
So--I'm pondering how to fix the hangs and bangs, And just how a ROM-upgrade can work...
|device_notes=This is essentially the same as the [[Grouper_Info|Nexus 7]], but with a 3G mobile network connection.<!-- optional. You can put as many lines of description as you like here. -->
+
 
|device_release_date=<!-- optional. {{#dateformat:2012 July 8}} -->
+
But--'nobody speaks directly on the web', so--
|device_carrier=<!-- optional, but include any mobile companies that apply. Example: AT&T, Vodaphone -->
+
 
|device_recovery_boot_steps=Hold '''Volume Up''', '''Volume Down''', & the '''Power''' button. Continue to hold all three until the screen flashes, then release all buttons.<!-- optional. Please bold any button names in instructions for easy reading. Example: '''Volume Down''' & '''Power''' -->
+
How do I get an upgrade for Android 4.0.3,
|device_bootloader_boot_steps=<!-- optional. Please bold any button names in instructions for easy reading. Example: '''Volume Down''' & '''Power''' -->
+
Can a processor (Allwinner A10) upgrade to 4.1 by changing its ROM,
|device_fastboot_boot_steps=<!-- optional. Please bold any button names in instructions for easy reading. Example: '''Volume Down''' & '''Power''' -->
+
Can a ROM-upgrade load in parallel to the present ROM,
|device_image=grouper.png<!-- optional link to local graphic of the device -->
+
Can the old ROM always be restored in case of no-upgrade,
|device_soc=NVIDIA Tegra 3<!-- optional. System On a Chip version. Include the manufacturer, if possible an abbreviation. Examples: Samsung Exynos 4210, NVIDIA Tegra 2, TI OMAP4460 -->
+
Will the ROM-upgrade avoid the 'mistakes' that resulted in system-hangs,
|device_cpu=Cortex A9<!-- optional. Example: Cortex A8 -->
+
 
|device_cpu_frequency=1.3 GHz<!-- optional. Example: 1.2 GHz -->
+
Or, is the problem really only a system-app-load design botch--that should be corrected at the app level?
|device_cpu_cores=quad<!-- optional. Example: dual -->
+
 
|device_ram=1GB<!-- optional. Example: 1GB -->
+
== mtk6589 device ==
|device_gpu=Nvidia GeForce ULP<!-- optional. Examples: Mali-400, PowerVR SGX540 -->
+
 
|device_type=tablet<!-- optional. Examples: phone, tablet, game console, etc. -->
+
i have an android 4.2.9 single micro sim
|device_weight=340 g (12 oz)<!-- optional. Example: 118 g (4.2 oz) -->
+
phone from china with the mtk6589 it has been rooted ...is there a CM rom android4.3 for this device
|device_dimensions=198.5 mm (7.81 in) (h)<br />120 mm (4.7 in) (w)<br />10.56 mm (0.416 in) (d)<!-- optional. Example: 122 mm (4.82 in) (h)<br />64 mm (2.53 in) (w)<br />9.9 mm (0.39 in) (d) -->
+
|device_screen_dimension=178 mm (7.0 in)<!-- optional. Example: 102 mm (4.00 in) -->
+
|device_screen_resolution=1280×800 (WXGA)<!-- optional. Example: 1280x720, 1280x800 (WXGA) -->
+
|device_screen_density=213 ppi<!-- optional. Example: 220 PPI -->
+
|device_screen_technology=IPS LCD<!-- optional. Example: IPS+ LCD, Super AMOLED+ -->
+
|device_internal_storage=32GB<!-- optional. Example: 2GB -->
+
|device_sdcard=none<!-- optional. Examples: up to 32GB, none -->
+
|device_bluetooth=3.0<!-- optional. Example: 3.0 -->
+
|device_wifi=802.11 a/b/g/n<!-- optional. Example: 802.11 a/b/g/n -->
+
|device_gsm_frequency=<!-- optional. Example: 800 850 900 2100 MHz UMTS/HSPA+ -->
+
|device_cdma_frequency=<!-- optional. Example: 2000 MHz CDMA<br />900 MHz 1xEV-DO -->
+
|device_wimax_frequency=<!-- optional. Example: 802.16e -->
+
|device_lte_frequency=<!-- optional. Example: 700 MHz -->
+
|device_camera=1.2MP<!-- optional. Example: 5MP -->
+
|device_camera_flash=<!-- optional. Examples: LED, none -->
+
|device_secondary_camera=<!-- optional. Example: 1.3MP -->
+
|device_peripherals=accelerometer, gyroscope, proximity sensor, digital compass, GPS, magnometer, microphone, NFC<!-- optional. You can include such things as accelerometers or digital compasses -->
+
|device_is_nexus_device=y<!-- set this to anything to add unlock instructions to build guide. LEAVE EMPTY FOR NON-NEXUS DEVICES! -->
+
|device_oem_unlock_command=<!-- non-nexus devices that still use fastboot to unlock should put the fastboot unlock command here. Nexus devices, don't use this. -->
+
|device_local_manifest=<!-- set this to a link to add local_manifest.xml to build guide -->
+
|device_kernel_override=android_kernel_asus_grouper<!-- replace auto-generated kernel link when device name does not match kernel name. Example: aries, smdk4210 -->
+
|device_sound=<!-- optional. -->
+
|device_cm_forum=691-google-nexus-7/<!-- optional. Example: 529-google-galaxy-nexus-gsm/ -->
+
|device_irc_channel=#nexus7<!-- optional. Assumes freenode IRC server. Example: #nexus7 -->
+
|device_power=<!-- optional. you can put battery info, voltage, mAh, and/or how many hours of use, removable or not etc. Example: 1500 mAh-->
+
|device_maintainers=nemith<!-- optional. You can put as long a list of maintainers as you like including links. -->
+
|device_contributors=<!-- optional. Put non-maintainer contributors here. -->
+
|device_additional_info=<!-- optional. Last chance to put any other notes. -->
+
|install_samsung_recoverytype=<!-- optional, only used for Samsung.  Examples: initramfs, initrd, or dual -->
+
|install_md5sum=19c39aff057995fa0d7c32d21ab9507e<!-- optional. Used for md5sum of files for use with exploits -->
+
|install_devname=koush<!-- optional. Used for posting creator of said files for install -->
+
|install_file=http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.2.3-tilapia.img<!-- optional. URL for recovery/exploit -->
+
|device_download_mode_steps=<!-- optional, only for Samsung. -->
+
|device_hboot=<!-- optional, only for HTC -->
+
|device_htcunlock=<!-- optional, only for HTC Dev Unlock -->
+
|device_sonyunlock=<!-- optional, only for Sony(/Ericsson) Dev Unlock -->
+
|device_motounlock=<!-- optional, only for Motorola Dev Unlock -->
+
}}
+

Revision as of 22:33, 15 September 2013

i have a samsung double time and i would love to get a customize os to be able to use the feature

entry level questions & purposes

I have a tablet (Craig CMP 741e Android 4.0.3), That does not respond well (10-20 sec. system hangs, 30 sec.-30 min. http-browser bangs), Yet it's fast (1.20 GHz on most apps, 1.15 GHz benchmark, 1.10 GHz on one crashy app), And many apps do well (streams youtube video HD 800x444, shoutcast audio at 320 kHz, b.g.), But, not, the http-browsers (Firefox 22, Dolphin Beta, &c.), and especially-not the http-embedded youtube;

So--I'm pondering how to fix the hangs and bangs, And just how a ROM-upgrade can work...

But--'nobody speaks directly on the web', so--

How do I get an upgrade for Android 4.0.3, Can a processor (Allwinner A10) upgrade to 4.1 by changing its ROM, Can a ROM-upgrade load in parallel to the present ROM, Can the old ROM always be restored in case of no-upgrade, Will the ROM-upgrade avoid the 'mistakes' that resulted in system-hangs,

Or, is the problem really only a system-app-load design botch--that should be corrected at the app level?

mtk6589 device

i have an android 4.2.9 single micro sim phone from china with the mtk6589 it has been rooted ...is there a CM rom android4.3 for this device