|
epsilonomega posted:Has anyone put Cyanogen 6.1 on the Droid yet? I'm hesitant because I've read about issues with Google apps not working properly (I use Google Voice all the time). I installed it, and I'm digging the new features, but I hit a few snags: some apps not showing up on the Market, Voice Search constantly FCing, and a few other little things I don't remember. This is even WITH a pre-install wipe and letting ROM Manager handle all the dirty work. I finally solved it by downloading the install zip and the gapps zip from the Cyanogenmod site and doing the wipe/install manually, and now things are running as smooth as ever. Can't recommend it enough...it's hard to beat having a power control widget in the notification bar.
|
| # ¿ Dec 10, 2010 02:57 |
|
|
|
| # ¿ May 21, 2013 11:29 |
|
|
Emo Businessman posted:I selected the only google apps that were available when I installed Cyanogen 6.1.2 through that Rom Downloader application. I've gotten really weird results (including missing Market apps) using ROM Manager, and I don't think I'm the only one. It's probably worth manually downloading and re-flashing both the update and the Google apps packages. Maybe even worth trying once without a wipe, but of course you should be ready to do it again with a wipe if that doesn't work out.
|
| # ¿ Dec 17, 2010 06:01 |
|
|
n0manarmy posted:Well balls, that's no fun It's pretty quick, though. My Droid boot time seriously halved when I got rid of the fancy boot animation I'd been using and just let Android use the default one.
|
| # ¿ Dec 20, 2010 03:40 |
|
|
Casao posted:I'm not sure how to tell how much you have in /system easily, so hopefully someone will correct me. This is an incomplete solution, but if you use Root Explorer to navigate to /system, the bar at the top of the screen will tell you how much space is free there. Doesn't give you any info about the partition's total size, but you can at least see how much room you have to play.
|
| # ¿ Dec 28, 2010 19:21 |
|
|
Tranax posted:Crossposting from the help thread, was told I'd have a little more luck here, not sure if these problems are specifically related to the rom but that's when they popped up. I'm going to go out on a limb and guess that you used ROM Manager to install CM? If so, try re-downloading the ROM and GApps files from here: http://forum.cyanogenmod.com/files/...motorola-droid/ and then installing them manually from CWM recovery (along with a full wipe of data/cache, of course). For whatever reason, ROM Manager seems to give wonky results, especially with the latest CM. I had weird issues with my first few installs using ROM Manager (even though I wiped), but doing everything manually fixed everything.
|
| # ¿ Jan 7, 2011 16:10 |
|
|
Protokoll posted:I'm going from one ROM to another and I want to absolutely nuke everything on my phone. If I wipe the cache and data through Clockwork and format my internal storage/SD card (one and the same on the Nexus S), is there any other residual data on my device that I can delete? The ROM install scripts should handle wiping the other partitions (/boot and /system being the important ones). Protokoll posted:Also, is there a way to prevent Google from restoring my apps when I flash a new ROM? I have the option to backup disabled but when I flashed CM7 and then another ROM, it restored apps both times. Not sure if this works on the S, but on most vanilla Android phones, you can skip the initial setup wizard (the one with the big green Android in the middle of the screen) by tapping the four corners of the screen in a clockwise fashion, starting from the upper left: http://www.droid-life.com/2010/06/1...motorola-droid/ If you go into Settings:Accounts and add your Google account after that, it shouldn't download your apps that time.
|
| # ¿ Jan 9, 2011 00:09 |
|
|
DkHelmet posted:No, I pulled the VMM.apk from Virtuous and dropped it in /system/app with a rw'd partition. It's in there, just not running. The permissions might be wrong. I forget exactly what they should be (rw-r--r-- maybe?), but if you just match them up with the other apps in that directory and reboot, you should be good.
|
| # ¿ Jan 13, 2011 20:55 |
|
|
Maker Of Shoes posted:I'll let you know how it performs over the next few days. Every previous GB ROM I've run has poo poo its pants after 24 hours. I flashed this new CM nightly about 3 hours ago and so far no quirks but the next day will be very telling. Just out of curiosity, what did form did this pants-making GBS threads take? Horrible laggy performance? Constant FCs? Bootloops?
|
| # ¿ Jan 17, 2011 02:56 |
|
|
Maker Of Shoes posted:Most notably would be the phone taking 10-15 seconds to unlock and after a day or two the Dialer app would also poo poo out whether it be not launching at all or when somebody called my phone would just white screen and ring until I yanked the battery. Yikes, fun times. I might wait to hear how things go before I take the plunge, then. Hopefully they'll get it stable on the Inc soon.
|
| # ¿ Jan 17, 2011 06:47 |
|
|
Skeezy posted:No clue but it shouldn't be an issue. Nothing bad happens from what I can tell. Specifically, it's green when it has a solid connection to Google's servers and white when it doesn't. It's a new GB feature.
|
| # ¿ Jan 18, 2011 04:19 |
|
|
Zarkov Cortez posted:That's a little disappointing Then you're really not going to like this. Personally, I plan to follow their advice.
|
| # ¿ Jan 20, 2011 05:58 |
|
|
BathroomTile posted:Other people pointed this out, I think in another thread, but Motorola turned their back on this: Huh, interesting. Definitely a reversal of what seems to have been a long-standing policy. I'll be interested to see what they come out with, but they've ruffled enough feathers that they won't get too far if they attach any ridiculous policies or pricetags to their "developer" phone.
|
| # ¿ Jan 20, 2011 22:51 |
|
|
ndrake posted:Very basic question, but does anyone have an incredible that they flashed to the latest stable cyanogen? I'm new to rooting, when I tried it I couldn't activate the phone. At the activation screen there is no keypad, and google nets me "hold menu to get a keyboard," which gets a keyboard, not a keypad, and the phone doesn't seem to pass the keypresses on to verizon (so I can't push 1 to activate). Anyone else run into this problem? I'm sure it's something simple... I've flashed CM 6.1 a bunch due to some idiotic belief that it might be worth trying a Sense ROM here and there, and I've never had any trouble like this. The usual prescription for weird crap with CM is to wipe and reinstall. If that doesn't work, try downloading the ZIPs for the ROM and the Gapps from the website and doing a manual wipe/install rather than using ROM Manager.
|
| # ¿ Jan 25, 2011 13:48 |
|
|
Ashex posted:Bugger, I went with an HTC because I perceive it as having a higher build quality then the SGS phones. So far I've noticed that the camera isn't as nice, speaker phone is a bit tinny, and the DAC isn't as good. If it makes you feel any better, Bluetooth streaming from my DI sounds better than it did on my Moto Droid. Could be placebo effect, but hey, as long as I'm happy, right?
|
| # ¿ Jan 25, 2011 17:36 |
|
|
IOwnCalculus posted:I thought you could at least backup data between the two, if not the apps / system data itself? Data from apps like Angry Birds and Homerun Battle should be fine. Just don't try to restore stuff like SMS or your browser bookmarks.
|
| # ¿ Feb 1, 2011 01:11 |
|
|
Kaluza-Klein posted:I have an original verizon Droid that I love, but the wife is begging for it and letting me use her upgrade to get the latest and greatest. She isn't letting me wait for the Thunderbolt If she honestly can't wait another ten days and swapping with her until then* isn't an option, and rooting/aftermarket support is a big deal, you might actually be interested in the Droid Incredible. Smaller screen than the X and Fascinate, but no locked bootloader BS and it's got a great ROM community since it's so similar to the N1 in terms of hardware. It still holds up great against the X and blows the Fascinate out of the water in aftermarket support. All that said, the Thunderbolt is a relatively minor upgrade over the Incredible (and X and Fascinate), but it would definitely be worth waiting for if you can convince her to wait that long. * You can do this manually through your My Verizon account online; I forget exactly what the option is, but it's something like "Activate a new device" under your line. You just enter the ESN of the "new" phone and do a *22899 afterwards. Not sure if it'll work with a device that's already activated on another line on your plan, though; you may need to go into VZW for that.
|
| # ¿ Feb 4, 2011 19:48 |
|
|
savesthedayrocks posted:I'm looking for some troubleshooting advice, and I don't know where to pinpoint the problem. When you checked all the options, did you check each individual app's notification settings? Most apps like Gmail, SMS, and the like have their own individual "Vibrate Always/Only on Silent/Never" option. As an added bonus, most of them don't have the currently selected option displayed, so you have to tap the option to check/set it.
|
| # ¿ Feb 6, 2011 00:14 |
|
|
travisray2004 posted:Ok so I want to upgrade my Incredible to Clockwork Recovery 3.0.0.5 and figured that I can use this: Yeah, the other dude who replied to you is on to something. That thread you linked is for a totally different device by a totally different manufacturer on a totally different cell network. The best possible outcome you could end up with would be it not working, and you run the risk of screwing something up badly. At the very least wait until someone hacks it onto the Inc rather than just grabbing random packages and trying to install them. Why do you want to upgrade CWM Recovery anyway?
|
| # ¿ Feb 9, 2011 01:10 |
|
|
Sizzlechest posted:Will that wipe out the backup already there? I want to prevent the restore once CM 7 is loaded for the first time in case it's loving something up. You can also skip setting up a Google account on the first boot and create it manually from Settings later on.
|
| # ¿ Feb 18, 2011 03:37 |
|
|
There are suggestions to fix the CM GPS issues on the EVO on the previous and current pages of this very thread. Might be worth a try on the Desire. Links: http://forums.somethingawful.com/sh...1&pagenumber=58 http://forums.somethingawful.com/sh...1&pagenumber=59
|
| # ¿ Feb 18, 2011 12:11 |
|
|
helsabot posted:Quick question- do I need to do a wipe before flashing a new kernel? I just starting MIUI and its great but sometimes when I hit the power button the screen doesn't wake up so I'm trying a new kernel...does that even make sense? Absolutely do NOT wipe data before flashing a kernel. Some people advocate wiping cache or even just dalvik-cache, though.
|
| # ¿ Feb 21, 2011 03:29 |
|
|
Mo0 posted:When I have a boot loop on CM7, and my Moto Droid only goes to "Bootloader 2C.6C" (black screen that tells me I can plug in a USB cable to "start programming" but nothing else) when I hold up+X while turning it on, do I have a bricked phone, or can I somehow flash using that bootloader that I've never seen before? If your phone is stuck on the bootloader screen, you can use RSD Lite to flash an .sbf, but you'll pretty much end up back at stock and have to re-root and everything again.
|
| # ¿ Feb 24, 2011 02:20 |
|
|
Sizzlechest posted:\ The default behaviour is whatever is showing on the main tab. There's no one set of profiles that everyone agrees on; some people just turn down the maximum frequency and switch to a conservative governor when the screen is off (and this is handled automatically by the smartass governor), while others have a ton of different settings for every conceivable combination of temperature and remaining battery life. Personally I haven't even had SetCPU installed since I got a kernel with the smartass governor.
|
| # ¿ Feb 28, 2011 15:29 |
|
|
Jerome Agricola posted:The Desire has S-On. For what it's worth, I think you can free up some space on /data by moving the apks for Market-updated system apps into /system. You'd probably have to delete the originals first and then reboot, though. Titanium Backup can do this automatically as well.
|
| # ¿ Mar 3, 2011 02:28 |
|
|
Gourd of Taste posted:Hey is there a quick one-click root for the incredible? Considering doing it for a friend and if z4root works it's not a thing but if it's going to be a lot of work.. http://unrevoked.com/#inc
|
| # ¿ Mar 3, 2011 04:19 |
|
|
Ozmodiar posted:So, I know that by default you can create a folder called "Ringtones" on your SD card and Android will recognize that and allow you to set things in there as a ringtone...but I have two problems with it: I had this same issue and got sick of it as well, but luckily the fix is easy. Just use Root Explorer (or something similar) to go to /system/media/audio/. In that directory, you'll see the same folder structure (./alarms, ./notifications, ./ringtones) that you have in the SD card folder; just move the audio files into the appropriate directory and make sure to set the permissions on each one to rw-r--r-- (or 644). After a reboot, go in and redo all of your custom ringtone/notification settings, and you should be good.
|
| # ¿ Mar 3, 2011 23:51 |
|
|
Ozmodiar posted:Thanks...but I don't follow 100%. No worries about the folder structure; just put the audio files in the correct folder for what you want them to do (e.g., ringtones into the ringtone folder, etc.). It doesn't look like the CM File Manager will let you set permissions, so you'd have to either use the Terminal Emulator or Root Explorer to do that part. Let me know which one you'd prefer and I can walk you through the appropriate process.
|
| # ¿ Mar 4, 2011 23:58 |
|
|
Ozmodiar posted:Thanks for the help. Root Explorer is way easier (and generally awesome overall), so I'd say it's totally worth the investment, especially if you plan to do a lot of ROM re-flashing and need to repeat this process (since any ROM installation will wipe /system). Anyhow, here's what you'll want to do: 1. Open Root Explorer and navigate to folder containing the audio files you want to use as ringtones 2. Hit Menu:Multi-Select and tick the relevant files (it will help you later on if you remember the filenames of the files you're using) 3. Tap the little "Copy" button at the bottom of the screen 4. Navigate to /system/media/audio/ringtones 5. IMPORTANT: See the little button that appeared in the upper-right hand corner of the screen? The one marked "Mount R/W"? Click that. It should change to saying "Mount R/O". (Root Explorer may also ask for root access at this point, but I think it might have done that upon initial launch....can't remember exactly.) 6. Tap the "Paste" button at the bottom of the screen. It'll copy the files that you had previously selected. 7. Now you have to set the permissions of the files you just copied so that the system can use them. Scroll down through the folder you're in and find the first of the files you copied. 8. Long-press that file and select "Permissions" in the dialog 9. You'll get a little 3x3 grid of permissions; in the "User" row you want to tick "Read" and "Write", and in the other two rows (Group and Others), you only want to tick "Read". The final result should look like a reverse L-block from Tetris, with the long end pointing downward. 10. Tap "OK" 11. Repeat steps 8-10 for each of the files you copied. You'll know you did it properly if the little group of letters and dashes underneath the filename is the same as all the previously-existing files in the folder (in this case, it should be "rw-r--r--") 12. If you also have files you want to use as alarms or notification sounds, repeat the above steps, but go to the appropriate folder for that audio type in step 4. 13. After you've gotten all the files copied and permissions set, you'll need to reboot to get the OS to detect the new files. You may also want to rename or delete (after backing it up to your computer!) the folder with the original files so you don't have the OS detecting both copies of each file. Once you've done it a couple times, it's really not nearly as big a pain as it looks. Penguissimo fucked around with this message at Mar 5, 2011 around 04:55 |
| # ¿ Mar 5, 2011 04:53 |
|
|
Kaluza-Klein posted:I got an HTC Inspire yesterday, a nice upgrade from the original Droid. That sounds like a boot loop. Try wiping and reflashing, and if you still get it, poke around a bit on XDA to see if that particular nightly is just broken.
|
| # ¿ Mar 5, 2011 15:58 |
|
|
Gyshall posted:The headphone on my loving OG Droid is loose and I need to have it replaced from Verizon. Right now I'm rooted and running CM6 - how do I unroot it? Your best bet if you're sending the phone back would be to grab the stock .sbf and use RSD Lite to nuke the thing back to a clean, like-new state.
|
| # ¿ Mar 7, 2011 15:03 |
|
|
heat posted:There isn't an option for restoring just data because it doesn't back them up separately. I don't know how many apps you have with data you care about, but you can probably get away with restoring just those apps one at a time (no idea if you would have to uninstall the Google restored version first, probably not) You can absolutely restore just data. Just do a batch restore of all user apps, untick the ones you don't want to restore, and it'll toss up a dialog asking whether you want to restore apps+data, just apps, or just data. The last option is the one he wants.
|
| # ¿ Mar 15, 2011 16:52 |
|
|
Ozmodiar posted:Yeah...I got that much... Interactive is a bit fuzzy, but it apparently scales the processor speed using a more sophisticated algorithm than ondemand, which supposedly increases responsiveness. Conservative scales the processor up in steps based on load, rather than ondemand (which just goes to max once load crosses a certain threshold). According to the SetCPU coder, "The userspace governor is currently useless. It's another way for applications to set the CPU speed that SetCPU does not use." I've become a fan of the smartass governor, which is available in some new kernels and automatically throttles back the max frequency when the screen is off. Saves the need for a SetCPU profile to do this.
|
| # ¿ Mar 16, 2011 23:49 |
|
|
LastInLine posted:Honestly I couldn't find anything on those but here is the thread on it at xda. Feel free to look, it might be in there. More specifically, you can find the full explanation here: http://www.setcpu.com/#7
|
| # ¿ Mar 17, 2011 00:05 |
|
|
brc64 posted:I'm having an unusual issue with CM7 on my EVO. Basically, the screen responds.. strangely.. when the phone is plugged in. It's most noticeable when trying to type on the keyboard while plugged in. I frequently get double-presses on letters and other weird behavior that I don't see when typing unplugged. Are you using a third-party charger/cable? Some phones can apparently behave weirdly when plugged into cheap aftermarket chargers. I know this was a problem with the original Droid.
|
| # ¿ Mar 21, 2011 17:33 |
|
|
chomper posted:So apparently I need to update my OG Motorola Droid to the new FRG83G... You might be better off waiting a few days/hours/minutes and just flashing a rooted FRG83G image, which I'm sure will be up on XDA before long.
|
| # ¿ Mar 22, 2011 04:50 |
|
|
chomper posted:Will do... in the meantime, is there any way to stop the constant pop up annoying me to update? Actually, good news...it looks like the rooted image is already available! http://www.droidforums.net/forum/me...xed-frg83d.html I didn't realise that FRG83D was the OTA from December, though. Didn't the OG Droid just get another OTA in the past week or two? I'd double-check to make sure that FRG83D is the one you're being prompted for, since if it's not the newest one, you'll just get pestered to update again as soon as you install this one anyway.
|
| # ¿ Mar 22, 2011 12:47 |
|
|
yamdankee posted:Yeah I tried that but it keeps doing the same thing. Might have to reinstall in that case. Swype's licensing scheme is ridiculously picky about things like ROM changes and the phase of the moon, and even Titanium Backup doesn't always work, but you can usually clear things up by nuking it and reinstalling from the beta site.
|
| # ¿ Mar 24, 2011 16:40 |
|
|
rotaryfun posted:Can anyone explain kernals to me? Very simply put, the kernel is basically the piece of software that acts as a go-between for the OS and the hardware. With Android, the biggest implication of this is, as you said, overclocking. Some kernels also allow you to underclock below the speed allowed by the stock kernel. Many kernel devs have also tweaked the voltage used by the processor, which can result in battery gains if done properly. Since no two chips are identical, though, different people often get wildly varying results with this last one; if the voltage is too low for your phone to handle, you'll get into bootloops. You can also find kernels that have tweaked stuff like charging speed, governor (which decides how fast to run the processor at any given time) Other advanced features offered by some kernels include the ability to use different types of filesystem, enhanced memory management techniques like compcache, and certain types of swap. Generally you don't need to worry about this stuff unless you're a power user. The worst consequence you'd likely have to worry about would be the need for a wipe and restore/reinstall. As long as you do a nandroid backup before flashing the kernel, you should be fine. If your phone won't start up, or it freezes/randomly reboots a lot after flashing the kernel, you know you need to try another one. Theoretically it would be possible to ruin your phone's hardware with a bad kernel, but in practice the hardware will reboot itself before reaching dangerous operating temperatures. The OG Droid in particular seems to handle overclocking well; I've never seen one that couldn't get at least to 1 GHz.
|
| # ¿ Mar 24, 2011 19:14 |
|
|
quadratic posted:How exactly does one say MIUI? I've been saying "my you eye", but I don't know if that's right. (Or if there even is a right way.) According to this XDA thread: quote:If you were to translate the name ‘MIUI’ to English, it would probably sound something like ‘meeooee’. No idea how accurate that is, but the article cited by the guy who posted that sentence looks a lot more authoritative than the guy who speculated that it stands for "My iPhone UI".
|
| # ¿ Mar 24, 2011 23:16 |
|
|
|
| # ¿ May 21, 2013 11:29 |
|
|
chomper posted:There is a sticky in the CyanogenMOD Motorola Droid forum that said it's uncertain when a final will be released, as "development is, and always will be, slow for the Moto Droid." Is there a reason for this other than the phone's age and relative lack of power?
|
| # ¿ Apr 11, 2011 15:33 |
|
