yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] MagicDude4Eva:
Performance issues?

I have done a clean install (wipe and repartition of the SDCARD) where I started off with v.4.2.11 and subsequently upgraded to v4.2.13. I find the v4.2 branch extremely sluggish compared to Enomther (used this in the past).

Any interaction (be it Browser, Messages, Marketplace) takes extremely long. If I don't use the phone for some time and then select the Dialer it will take 5 seconds the first time and then 2 seconds the 2nd time to call the app.

It seems that it is swopping out the first time and while in memory relatively fast. I didn't see this type of behaviour on Enomther's ROM.

My mem-stats (there is no swap - why?)

total used free shared buffers

Mem: 97908 96452 1456 0 496

Swap: 0 0 0

Total: 97908 96452 1456

Model: SD USD (sd/mmc)

Disk /dev/block/mmcblk0: 16.1GB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 512B 15.5GB 15.5GB primary fat32 lba

2 15.5GB 16.0GB 512MB primary ext3

3 16.0GB 16.1GB 32.5MB primary linux-swap(v1)

Am I missing something?
[G1 Android Development] PsychoI3oy:
Swap is not automatic with CM; you have to make a userinit.sh: http://wiki.cyanogenmod.com/index.php/Userinit.sh
[G1 Android Development] HaloTechnology:
every time i call contact it fc proccess.android
[G1 Android Development] jaaronmoody:
here you go
[G1 Android Development] Stone Cold:
I had this same problem. I ended up fixing it by restoring a backup I made before I flashed the new image to get out of it.

Bottom line is there's something in .13 that makes that setting react like that. I never found a way to turn the setting off from recovery. However, it seems feasable that since it works in previous versions, you could flash an older version back on (if you still have it on your SD card). Once you're in that version, you can turn off the setting and flash back to .13. I'd think that would be worth a shot before wiping...
[G1 Android Development] ryan508:
to be honest theres no point using swap i had it and my phone was running sluggish but now i have gone for the 10mb ram hack and is very speedy
[G1 Android Development] PsychoI3oy:
Bottom line is people shouldn't be messing with development tools unless they're actually developing.

(and yes I can confirm this issue and was almost late to work while I waited for a .12.2 nandroid to restore and .13 to flash again).
[G1 Android Development] Stone Cold:
I think we can both agree on this bottom line:

Kids, *ALWAYS* make a nandroid/bart backup before you flash a new ROM! It takes less than five minutes and it *will* save your bacon someday.
[G1 Android Development] MaDaFGG:
How to delete the ulock pattern ? I don't see any way to do it. I draw a pattern just for fun and now i forget it ... But i has turn off the require unlock pattern, then i can use my phone normal ... But just one funny action (...) you guy know it -0-

And i just use 3 home page, and 2 home page is blank, how to remove 2 these home page ?
[G1 Android Development] ZilverZurfarn:
There wouldn't be much use with a lock you simply can disable, would it?

CM comes with 5 home screens. Get Advanced Launcher (see another thread in this forum) if you can't live with 5 screens.

/Mats
[G1 Android Development] MaDaFGG:
Err, i forget my pattern that i draw just for fun, dude ... ~!
[G1 Android Development] ZilverZurfarn:
Still - A lock you can open without a key (forgotten or not!) is pointless. But there is a back door: http://xdaforums.com/showthread.php?t=485988

/Mats
[G1 Android Development] _zygo_:
So, if we have a swap partition on the SD, but no userinit, then the swap isn't being used and we don't have to worry about shortening the life of the SD? I've read the posts about this a few times (possibly from you,) and had been considering partitioning to remove the swap partition. But I shouldn't have to worry about it if I don't have a usernit, correct?
[G1 Android Development] tnpapadakos:
the comment about "why have swap if i already have the 10MB hack" got me to thinking (as i have both right now)

if i want to scrap swap after enabling it, how do i get rid of it?

delete the userinit.sh file off my sd?

or is there a script to run?

just want to know for future reference
[G1 Android Development] _zygo_:
Haha...I think we are asking the same question. If swap isn't automatic, and requires a userinit, it would seem NOT having a userinit would prevent an SD-based swap from being used. I wouldn't think you would need to do anything but remove your userinit, just like I haven't been using the swap by not having a userinit (if my thinking is correct.)
[G1 Android Development] tnpapadakos:
i know, one would think, right?

but the enabling of it had to have created some other effects on the system, like associations or paths between the rom and the sdcard or something, so i'm wondering if there's a "proper" way to remove it...cleanly, which leaves no residue on the system
[G1 Android Development] ZilverZurfarn:
No. If you enabled swap with userinit.sh, just remove userint.sh (or edit user.conf) to get rid of swap usage. That's the proper way.

/Mats
[G1 Android Development] tnpapadakos:
thanks bro!
[G1 Android Development] dasoccerbomb:
OMG I am glad i read this post... I have been suffering from these random reboots for the past two days now and I had tried everything from wiping to re-rooting and etc but once i uninstalled Wall Switch all is well now :-) What other program do we use to rotate our BG's now?

thanks guys
[G1 Android Development] Charrion:
I wouldn't recommend deleting the app but you can disable notifications from it so you don't get double notifications when txts arrive. Just go in to settings for Messaging and uncheck Notifications.
[G1 Android Development] HaloTechnology:
it still FC every time i initiate A Call
[G1 Android Development] prettyboy85712:
Try flashing the newest dialer. LINK
[G1 Android Development] sjbayer3:
Stop telling people to reflash the dialer when their getting force close on making a call.

The problem before was a FC with Long Click, NOT making calls.

I had this problem earlier, I had to restore a nand backup, then I reflashed and it worked fine.
[G1 Android Development] wergeld:
Wallpaper Switch Causes Reboot with Locale Installed

Same issue with using Locale to switch wallpaper. I am using latest free version of Locale on CM 4.2.13 and it does it like clockwork at 8am and 530pm.

When it reboots after switching wallpaper it gets stuck in a boot loop with acore FCs. I have to manually hit "Wait" then it stops looping.
[G1 Android Development] :
Now that there's a Camera driver for Eclair, could we expect Cyan to jump to Android 2.x soon...?
[G1 Android Development] ebbysaja:
anybody can give me userinit.sh file. i can't make it.

i already have swap partition 64mb
[G1 Android Development] lnjryan:
Probably the MOST important thing to remember.

This has pulled my hiney out of the fire many times.
[G1 Android Development] tjhart85:
Until I updated to Contacts 2.8, I couldn't make calls & when a call came IN, it would just ring and not let me answer.

When I pushed the 2.8 update (NO REBOOT) and that update fixed all my problems.
[G1 Android Development] Klyentel:
There's an app called Backgrounds on the market...works pretty good for switching backgrounds. You create a slide show and have it to switch, hourly, daily, weekly or whatever. It runs in the background only when switching then it kills itself.....lmao....'kills itself'...haha anyway, I like, been using it for a long time, you make slide shows out your favorites that are on the app or out of your gallery

Its got some cool backgrounds too. Worked with all my CM updates, never force closed, rebooted, or anything.
[G1 Android Development] skrki:
Use wget to get the latest update from the web. Make sure you're online, cos this will download all the files you need to your sdcard:

#wget -O /sdcard/cyans_latest_greatest.zip http://n0rp.chemlab.org/android/update-cm-4.2.13-signed.zip
#wget -O /sdcard/defanged_base.zip http://<url>

Use this from the "adb shell" on your desktop, or from your device terminal.

Example URLs:

http://rapidshare.com/files/330451254/DRC83_base_defanged_working_maps.zip
preferred ^

http://rapidshare.com/files/318465504/signed-dream_devphone_userdebug-ota-14721.zip
http://rapidshare.com/files/318481144/AOSP_ADP_1.6_r1.4_DRD20_rooted_base_v2.zip
[G1 Android Development] pershoot:
noticing serious latency when a phone call comes in, then it misses, and an acore is presented.

also noticing delays on missed phone calls being reported.

will snap a logcat and report in issue tracker.
[G1 Android Development] skrki:
Tag, you've been Omega-wiped!

Sry, but that's the amusement mentioned earlier :)

See, that post suggests having a swap partition makes a difference with this ROM, when it actually doesn't. CM spares your SD card, until YOU tell it to start pushing it. Whether it is by userinit, autostart, some other clever method you may think of, or manual, it is only user action that initiates the swap space, so having the physical partition does not hurt - moreover, leaves you the option to activate/deactivate it whenever you need, i.e. when switching ROMs, looking for performance, or whatever.

How ever helpful this post may or may not be, one could conclude the stated just by reading the OP.
[G1 Android Development] wergeld:
I think this should be added to CM Updater since it reboots and applies update automagically then there is probably a way to have it make a Nandroid/BART backup as well.
[G1 Android Development] hbguy:
HELP with REBOOT

I've been having trouble with this rom. When I go into terminal emulator, type in su then reboot (its weird because it takes a while for the nu ber sign to appear). The phone proceeds to reboot then gets stuck at the loading screen (I've customized the splash so it just stays on that). Then I've wiped the phone before, put the 1.6 recovery image then flashed Cyanogen's rom and it works but all my data is gone. I've done this 2 or 3 times already.

Could someone help me with this. I can't use my phone like this :(.

Thank you,

hbguy
[G1 Android Development] TeeJay3800:
These are the kinds of things I'm concerned about. Why would I leave the stock T-Mobile ROM which I've experienced NO bugs with, to switch to a modified ROM like CM which apparently is FULL of bugs? I've read through much of this thread, people experience bugs and glitches left and right.

I would love to switch to CM because of the new features, all the back ported bits from Eclair, and the performance improvements, but I don't want a phone full of bugs and force closes! What should I do? Is my impression of the glitches worse than they actually are?
[G1 Android Development] _zygo_:
My original tutorial for rooting, and then installing CM (around the first week the MT3G was rooted,) included the steps for formatting the SD with a swap partition, in case I was loading a different ROM, and so I followed those instructions. I wasn't suggesting a swap partition made a difference in any way or that it was required. In fact, I hadn't given the swap partition much thought until a few posts back. My phone seems to work smoothly and properly without APPS2SD, swap enabled, home screen saved to memory, compcache, or any type of RAM hack. I experience zero lag and no home screen refresh lag. That's why I commented on the completely over-the-top "Omega Wipe," (and its inclusion of the RAM hack) and your smug, know-it-all public amusement of the procedure (even though I believe a wipe and reflash, which are included in the "Omega" procedures, should be standard troubleshooting steps.) As for the OP mentioning swap, do you mean the OP's reference to the CM wiki, as I don't see it mentioned in the OP? When I first started using the ROM, I don't think the wiki had that much material, and if I remember, the ROM's use of the SD-based swap came later.
[G1 Android Development] goff.caley:
Thank you all for your replies, I did in fact fix it. There is a nasty little bug there in the developmental tools that really does blow. I did not have a sdReader, and stupid me thought it was a smart idea to delete the .zip bundles of the sdcard to free up room. I figured out really quickly that that was not a smart idea. Anyways I used my fiances Samsung to to mount my sdCard on the PC and transfer the files that way. From there I just put the card on the phone and recovered from there.

Is there a way to removed the developers pack at least til the bugs are worked out? And if you were to upgrade from your current build of cyan, to a newer, is it as simple as overwriting the image?
[G1 Android Development] skrki:
Ah, a conformation finally... I've had it happen once so far. It's almost like the reported issue where your phone would start vibrating on phone call, screen blank, until it reboots (or you manually reboot it). The difference is, the screen stays on the Home (doesnt respond to it though), and once the caller hangs up, the phone recovers. I've tried picking up, but no go.. Will also contribute with a logcat when I can.
[G1 Android Development] pershoot:
your here to help the cause and assist for the greater good. if you're not comfortable dealing with a few bugs and issues, etc., then please feel free to switch back to stock.
[G1 Android Development] prettyboy85712:
You can always switch back to the stock ROM.
[G1 Android Development] TeeJay3800:
I'm actually still using the stock ROM. I would love to help the community and improve the CM ROM, but at this point I don't know if I'm cut out for that. Generally, I consider myself fairly competent with technology, and have even flashed phones before (most recently my SE TM506 with the generic unbranded firmware). However, I've never done anything close to the type of thing involved in rooting an Android device and flashing a modded ROM.

The CyanogenMod ROM looks very exciting because of all the advantages it has over the stock ROM, but with bugs being so prevalent, and with me not knowing if I can deal with them appropriately, I'm not sure a modded ROM is something I should be using. What would you guys do if you were me?
[G1 Android Development] veliath:
"work email" force-close

I have noticed this problem. The log for 4.2.12.x says the "work email" app has been moved. I wonder if that is the reason. I'm planning to move back to 4.2.11.1

veliath
[G1 Android Development] Stone Cold:
When it comes to the specific subject of incoming calls, my wife's stock MyTouch delays a few rings before anything happens. This is the same on my rooted G1. My wife's MyTouch also experiences lag, and force closes here and there. All on the STOCK ROM!

I'm been running CyanogenMod since 4.1.99, and I upgraded from JF.15. I rooted my phone within a week of owning it. My experiences, while some a little inconvenient, have mostly been positive.

Doing something like this is really personal choice. I rooted because I wanted wi-fi tethering. The work that's been done on the ROM looked cool to me, a tinkerer and computer geek, so I knew I couldn't live without it.

I think as long as you do backups before you proceed and know you can get back to where you started, there's not much unsafe to do (though the initial stuff can look a little intimidating). It's all about common sense.

My phone does things that simply aren't possible without Cyanogen's ROM. I would have probably already become bored with my phone if it wasn't on there.

I'm not here to sway a descision either way, but I'm guessing for every post with a problem, there are plenty of people who use the ROM with no problems and simply never post. I've been rooted and I haven't posted a message here until a few days ago...
[G1 Android Development] goff.caley:
To further support Stone Cold, TeeJay, there is alot of fun in knowing that you can and are capable and making your phone do exactly what you want. you also get the pleasure of learning something new about your device.
[G1 Android Development] TeeJay3800:
Thanks for your input! You pretty much hit the nail on the head right there. I've only had my G1 for 2 1/2 months and I already feel somewhat bored with it. I also hate not having the latest version of Android, and CM seems to bring you pretty close to 2.x with all the back-ported stuff. I've been thinking a lot the last few weeks about whether or not to root and switch to CM, but am having a hard time reaching a decision on my own, so I appreciate the help!
[G1 Android Development] prettyboy85712:
Baby steps....just root your phone.
[G1 Android Development] RAQemUP:
Ya, I say just root your phone following the guide to the letter and you should be all set. If you really do not like it, you can just go back to stock. At least then you can say you tried something else. You really shouldn't dog something till you try it really.

I am sure there are a good number of people who generally are problem free. Keep in mind that in these threads here, people are only going to comment on problems they are having. The people without problem really have no reason to post and probably usually don't bother posting.
[G1 Android Development] Stone Cold:
Well you lived through a couple of unhelpful replies and you write in complete sentences. You seem cut out to me...

Cyanogen's wiki is very well written, it really gives you all the knowledge you need. As for dealing with the problems, it's kinda like computers. There's the folks who just blame everything on the OS (never an application or setting), never seem to have any real details to their problem (just complaints), and never troubleshoot. Those are the people who should be running the stock OS. This is really cutting edge stuff going on here...no way it's going to be perfect everytime. Then there's the aproach of being patient (you may have to go back to an older version or live with a problem temporarily), learning the tools to collect information (adb logcat is totally cool), and sensibly posting *specific details* of a problem and asking for help.

Again, I'm not trying to sway your opinion, but you ARE posting in a post full of people who are using the ROM. What would I do if I were you? You already know you want it! :p

I was scared too. That first reboot after the first flash was a doozy... But once I got through it (with instructions much worse than currently on the CyanogenMod wiki), I haven't looked back.
[G1 Android Development] PsychoI3oy:
teejay (and anyone else on the fence about rooting), I understand trepidation about rooting/installing, and if this thread was the only information to go by, I'd never have installed CM.

That being said, there's over 50,000 active installs of the cm updater app so you have to figure there's at least that many users. Compare the number of complainers here (and ignore the installation issues, unable to follow directions issues, and caused-by-bad-data issues), and you'll find that there are very few real problems.

Don't get me wrong, there are known issues. But the big ones get fixed quickly and the more minor ones are either to sporadic to diagnose, present in Android in general, or would require major overhauls to fix. Aside from the issue with Contacts (which is minor and easily fixable) 4.2.13 is the most stable and usable version of CM, not to mention quite fast.

Read through the wiki (link in my sig) and join #cyanogenmod on freenode to ask questions. The most important thing you can do is learn (outside of this thread, please) what you're doing, why you're doing it, and how it effects the phone.
[G1 Android Development] crypticc:
bravo, encore
[G1 Android Development] _zygo_:
And probably that many more who manage to install and update the ROM without the CM updater app (I can't believe how many people complain about updates not showing in their CM updater app, when in the time it took them to complain, they could have manually downloaded and installed the update, and had full control of the installation while doing so.)
[G1 Android Development] terrancextc:
Try flashing DRC83_base_defanged.zip from cyanogen wiki and then cyanogenmod that might fix it
[G1 Android Development] tjhart85:
Every now and then I go back to a stock build to see if it's gotten any better. It hasn't.

The only issues I had before were my emails not being pushed out fast enough, which is fixed with this.

I do run the extra 10MB ram hack because I don't do anything that requires the video to have that extra 10MB (the 3D games on android suck IMHO, so I don't bother with them).

I also do use a 128MB swap partition on my SD card. I've been using droidswap, but just made the switch to the userinit.sh instead as droidswap doesn't seem to autoload it's settings every startup (I had the option set, but it didn't work).

Using the swap partition will result in a shortened lifespan for your SD card, but since 8GB only costs like $20, it's not a huge deal IMHO.

The end result, using CM with swap and rom hack results in a pretty speedy build that is WAY better than stock. Add the fact that Cyanogen has built in all sorts of neat things (tethering for example) and that being rooted allows me to use Wysie's Contacts (which has so many features that SHOULD be built into stock it's insane) makes it very worth it. For a while, we had a newer version of Market installed than anyone else (possibly one of the reasons Steve got a C&D letter). With root, you can have a task manager, browser cache can be moved to an sd card (results in your pages reloading a LOT less) and probably most important, you can move your apps to the SD card! All of these things combined make a modded ROM a significantly better choice than stock

Any issues you have, you can always go back to a stock build. No big deal. You'll still have the hacked bootloader, so you'll be able to put a new custom rom on whenever you want, so you've really got nothing to lose by giving it a shot. If you don't like what you see, flash a stock tmobile & forget about the whole thing :D
[G1 Android Development] psguardian:
For the most part Cyanogen puts out a stable product. MOST ALL of the solitary 'issues' reported here are just that = solitary, some yutz didn't follow the instructions or tried to invent a short-cut & F'd up his/her phone. These are not bugs, bugs are when you have 50 people right after a release (the Groupies that install 10sec after it hits Cyans FTP) all say the SAME thing is broken.

Generally after 24hrs ANYTHING Cyan missed in his code has been laid bare on the table & is fixed or a fix is in the works (a 4.x.xx.1 will be posted). IF the forum blows up again rinse-later-repeat the reading & waiting game. Once you have 24hrs after a release without the forum blowing up Groupie style its safe to install.

You don't have to be a Groupie to use CM ROMs, just wait for them to make sure the waters are warm & slip in with the 2nd wave of installers. So long as you follow the tried & true KNOWN working methods for ROOTING & installing CM ROMs you can have all the joy & full featured use without any of the "will this be the release that borks my phone?!" headache. & remember nandroid backup is your friend. Once you have the defanged base & CM + fixed Contacts.apk installed make a nandroid, set up all your apps & widgets & make a 2nd nandroid. Now live happily ever after :)

~psguardian
[G1 Android Development] wettems35:
IM application?

i had downloaded the IM app from cmupdater just before 4.2.13 came out, but when i flashed 4.2.13 my IM app dissapeared and it is no longer in cmupdater. any suggestions on how to get it back?
[G1 Android Development] gsgleason:
It sounds like I'd buy some nice tight skinny jeans and visit the apple store.
[G1 Android Development] psguardian:
Ouch! C'mon now this one has potential lol. No valley girl accent in the posts, complete sentences, tech background, prior firmware swaps on other handsets, I think they could be a stable CM follower :D

~psguardian