Difference between revisions of "Wiki Problems"

From WebOS-Ports
Jump to: navigation, search
(Created page with "==Something screwy?== Hey! Did you find an issue with this Wiki and you don't know how to fix it yourself? This page is for reporting problems-- maybe it'...")
 
(Something screwy?)
Line 1: Line 1:
==Something screwy?==
+
==Something Wrong?==
  
Hey!  Did you find an issue with this Wiki and you don't know how to [[Documentation|fix it yourself]]?
+
Did you find a problem with this Wiki and you don't know how to [[Documentation|fix it yourself]]?
  
 
This page is for reporting problems-- maybe it's a bad installation instruction or something wrong with the build walkthroughs.
 
This page is for reporting problems-- maybe it's a bad installation instruction or something wrong with the build walkthroughs.
Line 9: Line 9:
 
{{Note|heading=Fixing Individual Device Settings VS. Fixing Wiki-Wide Templates|note=*If the problem is with information regarding a device such as the info page, the install instructions, or the build page, try editing the device template for that page, linked at the bottom of every device info page.  '''Modifying these settings will only affect the device in question, although may affect several pages relating to that device.'''
 
{{Note|heading=Fixing Individual Device Settings VS. Fixing Wiki-Wide Templates|note=*If the problem is with information regarding a device such as the info page, the install instructions, or the build page, try editing the device template for that page, linked at the bottom of every device info page.  '''Modifying these settings will only affect the device in question, although may affect several pages relating to that device.'''
  
*If the problem relates to ALL the devices, you may want to look at the template that is used by the device.  '''Modifying a template will change dozens if not hundreds of pages simultaneously for many devices, so only play with these if you know what you are doing!'''}}
+
*If the problem relates to ALL the devices, you may want to look at the template that is used by the device.  '''Modifying a template will change dozens if not hundreds of pages simultaneously for many devices, so only play with these if you know what you are doing!'''}}
  
 
If you can't fix the problem yourself, describe the problem below thoroughly and include links to where the problem is, as well as what the solution should be.  Also add a '''<nowiki>--~~~~</nowiki>''' at the end of your message to "sign" it.  Hopefully someone who's able to look at the problem can fix it.
 
If you can't fix the problem yourself, describe the problem below thoroughly and include links to where the problem is, as well as what the solution should be.  Also add a '''<nowiki>--~~~~</nowiki>''' at the end of your message to "sign" it.  Hopefully someone who's able to look at the problem can fix it.

Revision as of 00:10, 22 May 2013

Something Wrong?

Did you find a problem with this Wiki and you don't know how to fix it yourself?

This page is for reporting problems-- maybe it's a bad installation instruction or something wrong with the build walkthroughs.

Of course, since this is a wiki, you can try to fix the page yourself.

Note: Fixing Individual Device Settings VS. Fixing Wiki-Wide Templates

  • If the problem is with information regarding a device such as the info page, the install instructions, or the build page, try editing the device template for that page, linked at the bottom of every device info page. Modifying these settings will only affect the device in question, although may affect several pages relating to that device.
  • If the problem relates to ALL the devices, you may want to look at the template that is used by the device. Modifying a template will change dozens if not hundreds of pages simultaneously for many devices, so only play with these if you know what you are doing!

If you can't fix the problem yourself, describe the problem below thoroughly and include links to where the problem is, as well as what the solution should be. Also add a --~~~~ at the end of your message to "sign" it. Hopefully someone who's able to look at the problem can fix it.

If you do fix the problem, please remove the report from this page.

Examples

Bad example:
I couldn't get my Nexus 7 build working!
Good example:
On the page Grouper_Info, I noticed there was a bad link. The kernel for the source code is actually located at http://www.github.com/cyanogenmod/android_device_asus_grouper, not http://www.github.com/cyanogenmod/baddirectory as reported on the page. --Fattire (talk) 07:38, 8 December 2012 (UTC)

Note: please leave edit time in UTC as far as possible to maintain uniformity

Report any issues you discover below

Note:

Put new issues at the top! And don't forget to add your name and a date by appending --~~~~ at the end.


Install_CM_for_spyder - Razor Blade links are missing for [Linux]http://batakang.com/ftp/DROID_RAZR/razr_blade_linux.zip and [Mac]http://batakang.com/ftp/DROID_RAZR/razr_blade_mac.zip
--Jesse Buffington (talk) 13:16, 20 May 2013 (UTC)


Install_CM_for_targa the Razr's edge exploit doesn't work for JB. Had to use: http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/ --Jeremy West (not sure how to sign)


http://wiki.cyanogenmod.org/w/M7_Info lists the CPU as 1.7 GHz quad-core Cortex A9, while in reality it's 1.7GHz quad-core Krait 300. Krait is Qualcomm's own ARM-compatible design, not based on Cortex-anything. Also the display is called "SLCD3" or "Super-LCD 3", not "Super-LCD 2" --Kaotik (talk)


Someone added on the http://wiki.cyanogenmod.org/w/Unofficial_Ports site links to my CM-port for Acer A210 release threads on xda-developers and android-hilfe.de fora. But due to some build issues to be fixed (my build needs currently some changes outside /deices/<vendor>/<product> treepath) I did not publish the source yet. Maybe you want to remove these links until I fixed the build issues and publish the source. --U.k-f (talk) 08:34, 7 May 2013 (UTC)


On the page http://wiki.cyanogenmod.org/w/Install_CM_for_p1c it would be helpful to say that the recovery mode for this particular model is to "Simultaneously Hold Home Button, Volume Up, & the Power button, continue to hold all three until the screen flashes "Samsung", then release all buttons." --AndyCool22 at gmail dot com May 4 2013


In the page for Live with Walkman (coconut), you need to be more clear on how to use the fastboot mode, which is by turning phone off then pressing volume up while connecting to PC. Also, at that time, Windows fails to install driver for "S1Boot Fastboot", causing the fastboot utility to keep waiting for device. In order to fix this, you need to follow the instructions on the linked Sony page to download an inf file and replace the one shipped with SDK, then use that file as source for driver installation. --RenatoSilva (talk) 23:20, 1 May 2013 (UTC)


Mac driver is missing in the package that is provided on http://wiki.cyanogenmod.org/w/Install_CM_for_i9300#Installing_a_custom_recovery_on_Galaxy_S_III_.28International.29 This is the download http://cmw.cmfs.me/common/heimdall_v1.4rc1_mac.zip package that needs to add the Mac kernel driver which is this file: /System/Library/Extensions/heimdall.kext/Contents/Info.plist --Hashier (talk) 11:39, 13 March 2013 (UTC)


Missing step - HP touchpad With the instructions at http://wiki.cyanogenmod.org/w/Install_CM_for_tenderloin I have successfully reached step 12 of part 1 and can us MoBoot to get into WebOS or into ClockworkModRecovery. But the next section speaks of using the command "adb" to put the CM zip file on the SDcard. I can't see where the adb command is supposed to run! I checked the video version of the instructions and this isn't covered - on the video version, as soon as MoBoot is running, "Boot CMod" is one of the boot options. It isn't for me!! --Ccomley (talk) 21:41, 24 February 2013 (UTC)

There is documentation in this wiki about adb and how to use it, but I can make that more linkable in the document I guess --Fattire (talk) 21:50, 26 February 2013 (UTC) UPDATE: It says "See adb documentation for additional help with this step". Was this not there before? If not, we can remove this wiki problem item. --Fattire (talk) 21:52, 26 February 2013 (UTC)

On the "Install CM for tenderloin" page I noticed two things that could be documented.

  • After installing the novacom package and booting the TouchPad in USB mode I did not get the novacom (boootie) driver until after I had rebooted my PC.
  • When running the novacom command it simply hangs if you are not running it as administrator. Start the command shell using the "Run as Administrator" option if you do normally run as administrator.

Wade Satterfield 23:00, 23 February 2013 (UTC)


  • Installation on an HP Touchpad, Installing CyanogenMod from Recovery

On Windows based system, after completed the steps Installing the ClockWorkMod Recovery using ACMEInstaller3. There is no sdcard folder on the Touchpad, and no sdcard can be plugged on the contrary of what is written. By default, as I understand, the sdard folder corresponds to the root of the Touhpad. When installing Cyanogen for the first time : 1/ Connect your Touchpad to your computer, enable the Mass Storage Mode, create a sdccard folder at the Touchpad root.Your folder can have any name, but sdcard is easier as the ClockWorkMod Recovery asks you for an sdcard. 2/ Place the CyanogenMod rom .zip file in the sdcard folder 3/ Reboot the Touchpad and follow the steps 4 6 to 9 of the Installing CyanogenMod section. --vitam1970 (talk) 22:00, 23 February 2013 (UTC)

There is a note that says Some devices do not have removable SD cards. Regardless, there should still be a partition on the device named "/sdcard" that can be used for flashing purposes, even though the contents of /sdcard may actually be in internal storage. -- This should be true for the tenderloin device just like any other. If I recall correctly, the /sdcard maps to the same virtual file system as the /media partition in WebOS. so I'm pretty sure it's there. Also, FWIW the /sdcard partition is NOT the same as the root of the touchpad, which is "/". --Fattire (talk) 21:59, 26 February 2013 (UTC)

Hint for the newbies : Google apps are not packaged with CyanogenMod9 builds. Just have a look at Goo.im to get the .zip approved by developers. Copy the archive in you sdcard folder on your touchpad, reboot and make a ClockWorkMod update. --vitam1970 (talk) 22:00, 23 February 2013 (UTC)


There's a bug in the libusb for heimdall (Windows--not sure about other platforms) that has been fixed since the version linked to here was built. (latest version from 2/1/13 available here: https://github.com/Benjamin-Dobell/Heimdall/tree/master/libusbx-1.0/lib/Win32/Release). I know it affects t-mobile S3s...not sure about others. I don't have quite enough confidence to recompile the whole thing and post it here. Also I'm not sure that even the libusb fix has completely fixed the problem--with the latest libusb, heimdall claimed to have successfully flashed the latest clockworkmod, but I was still at the previous version (although the counter incremented....odd). (further discussion at: https://github.com/libusbx/libusbx/issues/78) --Mattjm (talk) 00:20, 9 February 2013 (UTC)

Thanks for the heads up Mattjm, we will get it updated --Utkanos (talk) 01:37, 10 February 2013 (UTC)
Mattjm, are you able to test a new build I have? Please find me on IRC if so. --Utkanos (talk) 04:13, 19 February 2013 (UTC)

  • The installation instructions for the HP Touch Pad lack an important step. The android_winusb.inf included in the latest Google USB driver package lacks entries for this device. For me, it worked to add

%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&REV_0227&MI_01

%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01

after the last lines of the [Google.NTx86] and [Google.NTamd64] sections. Others reported success with

%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_6860&REV_0227&MI_01

%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_6860&MI_01

Check the Properties page for the device in Windows Device Manager for the PID that your device sends. --Marcus Ohlhaut (talk) 07:07, 27 January 2013 (UTC)

Issues Considered fixed

Note:

Any issues which were mentioned above previously and are considered "fixed" should be moved here. If someone feels that an issue is not yet fixed, they are free to move it back up, but please leave a comment why you consider it "not fixed".


http://wiki.cyanogenmod.org/w/Install_CM_for_quincyatt The md5 for the qunicyatt version of ClockWorkMod is reported on the page as a377cc819926c910b1974b38d9143f02 however, tar.md5 file reports an md5 of f3e92c325e876ec771247e2375e53cd7 , even though the tar.md5.md5 file on the server in the same directory reports the same incorrect md5 as the one on the wiki page. --42ndfloor (talk) 16:52, 25 April 2013 (UTC)

Thanks, a user fixed this already --Utkanos (talk) 15:37, 28 April 2013 (UTC)

http://wiki.cyanogenmod.org/w/Mint_Info shows that the latest CM version is jellybean, but under CM support it lists both 10 and 10.1. Builds started on the 17th for 10.1, so the latest CM version needs to be updated (I didn't know if there is a specific variable somewhere that needs to be changed, so I figured I'd leave it to the gurus). --Bassmadrigal (talk) 12:42, 24 April 2013 (UTC)

Nevermind. I figured out where to edit it and it is now updated --Bassmadrigal (talk) 12:53, 24 April 2013 (UTC)
Thanks for amending it. --Utkanos (talk) 15:37, 28 April 2013 (UTC)

On the page http://wiki.cyanogenmod.org/w/Install_CM_for_hercules it points users to the default build of Heimdall, which doesn't work with the SGH-T989 at this time. There is a fork of Heimdall with support for the SGH-T989 available at git://github.com/jamiejackson/Heimdall.git. Also, ClockworkMod will sometimes fail to work with a SGH-T989. It would, therefore, be helpful to note this on the instructions and provide some links to another Recovery Mod, such as TWRP: http://www.teamw.in/project/twrp2 --Hosef (talk) 03:41, 20 April 2013 (UTC)

This is already noted in the notes field at the top of the device page with a link to the repo where it can be built. What fails on cwmr recovery? I'll speak with the maintainer on it and update if need be. --Utkanos (talk) 15:37, 28 April 2013 (UTC)

The heimdall code example for flashing the recovery image onto a Samsung Galaxy S2 i777 is incorrect. That will flash the kernel, not the recovery image. This trashed my phone and I had to follow the instructions hereEntropy512's Original I777 UCKH7 Kernel plus Non-Rooted System Package in order to salvage my phone. For me on Mac OS X, the command line was more like "sudo ./heimdall flash --recovery recovery.img --no-reboot". Please fix this, so that I'm the last noob to hit that stumbling block. --Taltman (talk) 06:34, 19 February 2013 (UTC)

The recovery linked is NOT a kernel, it's a fakeflash that only replaces the running recovery with cwmr at run time. It is not a permanent change to the device. The above would never work on i777 as it does not have a dedicated recovery partition and the kernel itself contains the recovery. I will try to find a zImage instead of a fakeflash. For now I have replaced the instructions to make it more clear. --Utkanos (talk) 05:27, 20 February 2013 (UTC)

The build instructions for Motorola Xoom everest Build_for_everest#Extract_proprietary_blobs refers to a folder that does not exist and a script that does not appear to exist either.

The missing folder is ~/android/system/device/Motorola/everest and the missing script is $ ./extract-files.sh --Funcle (talk) 17:30, 20 January 2013 (UTC)

  • changed device_vendor to moto -- White 18:04 20 Jan 2013 (UTC)
  • The missing script, if it's not there yet, needs to be added by the device maintainer (or by someone else). Every supported CM device should have it. --Fattire (talk) 20:27, 27 January 2013 (UTC)
  • this is not really a wiki problem. The file will/should be updated by the device maintainer. Moving this to fixed but I think we should keep this till the maintainer actually gets around to including the extract script. -- White 05:07 9 Feb 2013 UTC