yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] epicphotoeye:
I'm sorry I didn't see this post before I tried reflashing so I can't tell you what happened to the su. Though I might not be opposed to doing it again cause I just wiped and reflashed and still no root. Am I testing to see if I have root wrong? I was under the impression I can either try connecting to localhost:23 with telnet and/or type root in terminal.
[G1 Android Development] epicphotoeye:
so actually, I did the wipe - reflash - and the commands you gave me earlier with no affect it seems. I can go into terminal and type su and it responds with a request:

/system/bin/sh

wants to run:

/system/bin/sh

as

root:root

do I allow this?

Also, after looking through your signature, I realized I have flashed what you call "danger" spl... So, maybe I should fix this, but I'm not sure what I use to overwrite it or if that's causing the problem.
[G1 Android Development] painrage:
su

Itls the best one and "su" is root on this phon you can't actually use the log handle "root" since the phone doesn't have log access. So to check if you have root go to terminal and type su when the white list comes up hit allow. Then there u go u've given most root user apps super user privliges your terminal should go from $ to #
[G1 Android Development] epicphotoeye:
ok, did that and clicked always allow and it did go to #. But when I run power manager 1.5.9 the paid version, and try to adjust settings for using wireless networks, it responds with an error saying it's "unsupported in the base version of Android but can be done on a rooted phone."

I'm gonna try doing some trouble shooting the app recommends but I was assuming this meant I don't have root.
[G1 Android Development] painrage:
yes

Yes you do have root doesn't sound like the app is working right. Go to your app tray and click on super user permission app and see if u've in accidently denied the program your using at one point

And besides it's not saying it'll do it for you it's just saying it's possible
[G1 Android Development] ei8htohms:
ack, please ignore irrelevant, out of date info, I'm too slow posting!

I'm not having the easiest time following what is happening and I'm probably not the most informed person to try to walk you through a fix, but I'm happy to help if I can.

First off:

The "Danger" SPL (1.33.2005) is only dangerous in the flashing process because it has been known to brick phones, virtually 100% of the time if the correct radio is not installed prior to flashing the SPL, but some (very) experienced folks have bricked phones flashing that SPL for no known reason. This is why I listed it as "NOT recommended".

If you have successfully flashed that SPL, I would recommend keeping it. It gives you a larger system partition which allows to run some of the larger ROMs without as much trouble. Don't uninstall that SPL now as you may want it in the future to load a fat ROM and then will court the potentially bricking once again (there's no way to know if flashing it one time successfully necessarily means you won't brick on it in the future). The only (very minor) downside that I see to the "Danger" SPL once it's properly installed is that it only has a single primary splash screen.​

Second:

Put your phone/provider/system details in your sig, so that anyone wanting to give or take advice will have more context. We don't list all that stuff out in our sigs because we want the whole world to know what we're running necessarily (I don't anyway), but if you observe a specific bug or run into difficulty, it is much more useful to anyone trying to help if they can see what you're running. At a minimum: Carrier (T-Mo (US or UK?), AT&T, Rogers, Vodafone, etc.), device (G1, Magic, Ion, Hero, Rogers, MyTouch, etc.), ROM (CM 3.9.7 or other "experimental" for this thread obviously), Recovery Image, SPL and any themes. It doesn't hurt to include SD info like size, speed, partition types and sizes and also userinit info if applicable. It just helps people trying to help you.​

Re-flashing the ROM should be a complete solution WITHOUT any special commands typed into terminal or recovery console. Reflash the ROM, reboot and open Terminal and type:

su
reboot

If your phone reboots, you have root. Feel free to PM me if you'd like and we can converse without cluttering up the thread with this (mostly off-topic) stuff.
[G1 Android Development] jessenus89:
i have the same issue, i need to restart to get the audio back, i was using the headset, then i was receiving a call but i didnt hear anything , i lost all audio!!1
[G1 Android Development] Zappletoo:
You can also type:

su
whoami

If it says "unknown uid 0" then you got root. That'll save you a reboot.
[G1 Android Development] LatinSilEighty:
I was searching through here and found someone else was wondering about this? anyone know what to do? or any different process? and had this already been answered?
[G1 Android Development] ultma75:
check dark hero theme by armyranger n beagz. i think he answered it, but pm him n i think he will tell u again.
[G1 Android Development] karolbe:
yep...I have the same. I have downgraded to a 3.9.5 build which is much faster.
[G1 Android Development] m0nst3rr:
Hey, i just noticed that when i get text messages and someone sends a message where they pressed enter, it just shows up as a box, any clue why?
[G1 Android Development] drpfenderson:
My phone keeps becoming blank. No response to waking or buttons at all. I can "three-finger" it to restart, but that is all. The problem is very sporadic, so I haven't really looked too much into it now. Recently rewiped and installed, but problems persist.

Don't know if logcat works under those circumstances. Is there any way to retrieve a log after restart to find out what is going wrong? Or does anyone have a better recommendation?
[G1 Android Development] robpet2:
so far after testing 3.9.5 , 3.6.5 and 3.8.6.1 where the fastest and def no lag...

last night 3.9.7 started slowing down on me out of no where, rebooted and it still had a lil bit of lag...
[G1 Android Development] lazaro17:
i'm getting this too. a restart fixes it for me but then it slows down again. going to go back to 3.9.5 for time being
[G1 Android Development] maxisma:
No lag here. ..
[G1 Android Development] All~G1:
+1... I was experiencing a lot of lag and multiple ANR's till I swapped out my SDcard. Now everything is screaming fast.
[G1 Android Development] :
Me too. can't pin point cause yet.
[G1 Android Development] Gilliland12:
Same here on two separate phones. Happened after a restart on both (one accidental and one intentional). Had a long load time at the Android then it went to a black screen where it stayed. Licked out on one phone and a simple factory reset did the trick, the other phone I did a nandroid restore (didn't try to do a factory reset on it). Also the accidental restart happened while downloading the maps for copilot. It just restarted out of the blue, not sure if that has anything to do with the build though.

For now I'm probably just gonna stick with the older stable build (atleast on my wifes phone).
[G1 Android Development] kingsizeriz:
does anyone else get random "message not sent" errors? which require a reboot to send messages?
[G1 Android Development] here.david:
Yes, try as I might still unable to send that/those specific message/e-mails just delete and re-do them to send without any issues and a lot of other small issues, have gone back to 3.9.5 for now...
[G1 Android Development] robpet2:
check you mms settings...

if you with tmobile go to

settings, wireless controls,mobile networks,access point names :

make sure this is what you have Change the settings to the following:

Name: T-Mobile US

APN: epc.tmobile.com

proxy: 216.155.165.050

port: 8080

Username: not set (delete everything in this field)

Password: not set (delete all here too)

Server: not set (delete the *)

MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS Proxy: 216.155.165.050

MMS Port: 8080

MMC: 310

MNC: 260

APN type: not set
[G1 Android Development] missxoash:
can anyone verify this works?
[G1 Android Development] robpet2:
the main thing is that if you have TMOBILE, and you are having difficulty sending mms messages, use the mms settings from what i posted... it works...

reboot the phone, and then try sending the mms to someone or to yourself... the mms setting might be blank due to the new mms.apk
[G1 Android Development] userfriendlyme:
Yup he's right. those are the correct settings.
[G1 Android Development] kingsizeriz:
im still trying to get o2 mms to work, wont send or recieve
[G1 Android Development] here.david:
Thanks...here is what was there:

Name: T-Mobile US

APN: epc.tmobile.com

proxy: not set

port: not set

Username: none

Password: not set

Server: *

MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS

MMS

MMC: 310

MNC: 260

APN type: not set

Any idea why as I did not change anything from Oct08, and only had this now after 3.9.7 did it show up?
[G1 Android Development] talltexan:
so this might have been answered already however i coudlnt seem to find the exact answer i have been looking for, my phone wont let me mount my SD card so i did a NANDROID backup and same problem still....... dont really know what i need to do to fix this.
[G1 Android Development] robpet2:
its cause of the new mms.apk thats in these new builds.. i clears the settings.. so all you need is to just do these 2

MMS Proxy: 216.155.165.050

MMS Port: 8080
[G1 Android Development] stellarman:
Hey, thanks for this. I don't use mms that much and hadn't noticed this was not working.
[G1 Android Development] robpet2:
i noticed it when i kept gettin force close messages for mms... then went to check my msgs and had like 10 mms that were trying to send, which was probably what was slowing it down...
[G1 Android Development] epicphotoeye:
Problem after removing SD card

I'm not sure if this is a bug or a problem with my install.

I removed my SD card while the phone was on. The phone rebooted itself after a few seconds. So I put the card back in and rebooted several times, but several of my programs now force close when I try to run them and in the notification bar, it constantly says "loading data, please wait..."
[G1 Android Development] Janis:
Erhem.....

OK, who messed with the messaging icon? :)
[G1 Android Development] bhilgeman:
Ya thats really bad. This rom has apps2sd built in. It gets really angry when you remove the SD. You are going to have to uninstall and reinstall all your apps. Did you back up all of your apps by chance? You may have to reflash the ROM
[G1 Android Development] epicphotoeye:
Well, yea... I was hoping there was something simpler I guess. Like:

$su

#fix -error stupid.user.removed.card

#shock -user when.card.door.opened.again

#cp idiot.img > boot.img

Obviously I don't know linux and I guess I was hoping there were some commands that could fix this without reloading all the apps.

Would this be something good to recommend a safe guard for?
[G1 Android Development] jimbo831:
I have this exact same problem, 100% of the time. I don't know how to do crash tests/logs or whatever, but if someone would share with me instructions on how to log the error so I can help Cyan pinpoint the cause, I'd be happy to help as I have a daily calendar reminder that I can't dismiss.
[G1 Android Development] PsychoI3oy:
The only safeguard to prevent this is between the keyboard and chair. Just like making sure the light is off when you remove a floppy disk and "safely remove hardware" before pulling a usb stick, the sd card in the phone needs to be unmounted (both partitions, only the vfat one happens automagically when you open the cover) before removal.

Try booting into recovery mode (assuming you have one of Cyanogen's recent ones) and 'repair ext' which will do the linux equivalent of a scandisk.
[G1 Android Development] here.david:
You could 1st try to delete all items BUT KEEP the folders on the ext...which I have done and got back OK...

dalvik-cache 0 items

app-private 0 items

app 0 items

lost+found 0 items

also re-flash sometimes (after deleting per above)
[G1 Android Development] epicphotoeye:
for the purposes of completion, I ended up just uninstalling and reinstalling the few programs I had that weren't working. But before I did this, I tried running the repair then fix_permissions and it didn't help. Thank you for the suggestions though! I hope I've given someone a chuckle from all this.
[G1 Android Development] aryndar:
He is (almost) back... Our King!

from twitter..

What an incredible weekend.

about 4 hours ago from twidroid by Cyanogen...
[G1 Android Development] linuxrebel:
I found the following helping me.

I was still getting some of the slowdowns I reported earlier until I did one thing. I plugged my phone into my Linux box and ran both dosfsck and fsck for the ext partition. Even though I'd run the ext error correction in 1.4.1 version of Cyanogen's rad recovery tool. It found a ton of minor, but significant errors, corrected them and then when I started using it, all kinds of speed was there for me.

I'm running 3.9.7 right now. Once I figure out the UI in here I'll put my phone data in my sig. Man I hate graphical UI's .... where's my text file!. :D

Man I wish I could edit the title. It should have read "I found the following helped me." Carp!
[G1 Android Development] linuxrebel:
Do you have a liveCD?

Since the ext2/3/4 (whichever you use) portion for the apps2SD is mounted and in near continuous use, yes pulling the card with the device turned on without doing the eject properly, can scramble things. (A little or a lot depends on if it was trying to write or not.) Kinda like pulling the power cord on your desktop while the comp is running.

2 options as I see it.

1. Run the ext repair tool in Cyanogens CM 1.4.1 recovery tool.

2. Better still if you run Linux or have a live CD, plug the phone into a Linux system, and run the fsck tool against the ext partiton.

Just reinstalling your apps may not fix things if the file system itself got damaged. If you can't run the repair tools you should re-format and then re-install the apps or re-install from backup. BTW it wouldn't hurt to run the dos repair tools on the vfat partition (either dosfsck from Linux, or the ones that come with Windows.) The ext file systems are better able to handle this kind of event than vfat, but not perfect.
[G1 Android Development] speoples20:
Babbler v1.2 Works!!

Babbler just updated to v1.2 and it works with 3.9.7. They changed the way it connects to facebook and seems to work now.:D
[G1 Android Development] 4treyu:
I'm also getting that on 3.9.7, the screen goes blank and then all the icons and widgets have to be reloaded. Sometimes it happens with wifi enabled, sometimes after closing a random app and sometimes after just waking up the phone. I didn't get any of those behaviors on 3.9.5, and at the moment they made me think of a memory leak too.
[G1 Android Development] zimphishmonger:
Devs working together, another win due to open source :D
[G1 Android Development] itp:
Slowdown...

I've experienced the slowdown I've seen others report after using 3.9.7 for a while. I'm wondering if it's not necessarily tied to this particular version, but to the fact that we haven't been rebooting to reflash while Cyanogen has been away.

Anyway, when my phone was getting sluggish, I connected to it via adb shell and ran "top -n 1" at the prompt. I noticed that the process system_server (which is basically a thread container for the android system, everything that's not a particular app) had climbed to 25% CPU use while the phone was idle. After a fresh boot system_server is at 0%. Could anyone else who is seeing slowdown compare and see if their system_server process is also getting out of hand?
[G1 Android Development] xordis:
I came to this thread after noticing exactly the same problem.

system_server sitting at around 20%+ after having the phone on for a while.

Running on a HTC Magic 32B here.
[G1 Android Development] talltexan:
so any one know about the unmountable SD card? anyone else having the problem of mounting it in windows only to have it un mount itself before it can display? This will prove to make Flashing Cy's Roms most difficult.
[G1 Android Development] ZilverZurfarn:
I guess you mean "I restored a Nandroid backup (from a state where the SD card worked)"? In that case, it's either something wrong with your SD card file system/partitions or a hardware issue (phone or (hopefully) card) - certainly not a problem with CyaongenMod 3.9.x (which this thread is all about).

/Mats
[G1 Android Development] talltexan:
ok i was afraid of that, will have to try to reformat my card, could this be the linux swap? that i still have on my card its not in use.
[G1 Android Development] ZilverZurfarn:
Unlikely. I've had my swap partition around a long time, in and out of use. Hasn't caused any ill side effects (as long as it's the 3rd partition).

/Mats
[G1 Android Development] amiuhle:
I never had any trouble with phone speed until I enabled compcache. A while after enabling it, the phone got slower and slower, and I got a FC on several apps once in a while.

I disabled compcache now to see if that was really causing the trouble.

I think compcache could explain the high CPU use in system_server.

Does anyone have speed troubles who has NOT enabled compcache? Could someone who has trouble with compcache enabled also try disabling it?
[G1 Android Development] nurre:
Dont have compcache on currently, and system_server was using 50% cpu usage earlier today constant.
[G1 Android Development] userfriendlyme:
Well i experienced the opposite. I had more trouble before enabling compcache. Since i've done that and used it all weekend with the 3.9.7 update i had a couple fc's but were app related. I do experience a little lag after some hours but it's been easily resolved by killing a few apps that were running in the background. I also installed autostart which i set to prevent some apps from starting up when im not using them. I havent even had to reboot my phone since enabling compcache all weekend. If theres and issue i don't think it can be all pointed to swap or compcache.
[G1 Android Development] senab:
I don't think it's compache as I have it enabled and I do not see any processes that are using >1% CPU. Admittedly I have set my compcache swap to only 12mb with a swappiness of 16, and do kill apps regularly.

To be honest, I'm more than happy with 3.9.7. I've underclocked to 128/384mhz and set powersave_bias back to 0, and my phone is as responsive as previous releases when I had it overclocked to 528hmz. Along with compcache I've got a bit of extra memory if it's really needed (which is rarely).
[G1 Android Development] itp:
High system_server CPU

To everyone experiencing slowness and high system_server CPU utilization --

The next step, as I understand it, is to connect to your phone using ddms (in the same directory as the adb binary). Once you've connected and the window is up, select "system_process" from the list on the left, and then you can look at either "Sysinfo" in the tabs to the right (will show a pie chart, you should see system_server using a large slice of that chart -- this display does not update automatically, so hit the "Update from Device" button every so often), and more importantly, the "Threads" tab. The threads tab will show a list of the threads running inside the system, and by watching the list, you should see one or more threads with significantly higher utime and stime values, and those values will be increasing even when the phone is idle.

That thread name (and possibly the Status column associated with that thread -- wait, timed-wait, running, vmwait, native) may prove to be useful information as we try to figure this out. Along with any other information at your disposal (uptime of the phone when you noticed slowdown, compcache on or off (although I don't think it's compcache), what apps you have running, particularly apps that run periodically in the background, etc.)
[G1 Android Development] nickL0V3:
Spare Parts

Ok, not a huge deal, just a tiny bug (I skimmed through, didnt see this, but 300+ pages is a lot)

In spare parts the use fancy rotation button no longer works

all of these people:

http://xdaforums.com/showthread.php?t=545631&page=6

are having the same problem.

Just throwing that in
[G1 Android Development] 4treyu:
I don't use compcache, I don't even do app2sd, and I have these speed problems people are reporting.
[G1 Android Development] twosixths:
I did the same. Within 24 hours, 3.9.7 was all but unusable, (very slow response, Google Voice & Google 'Apps' (?) error messages when using browser, etc so I downgraded to 3.9.5 (which in my opinion is the best ROM EVER). However, when I went back to 3.9.5 I started getting FCs for Android Media and couldn't open the gallery app. I wiped and re-flashed now everything works great.

Just from experiencing the two roms (3.9.5 & 3.9.7) it seems like 3.9.7 was noticably slower even after a fresh flash. Any idea what changes could have slowed the ROM down?

Am I alone in feeling that 3.9.5 was faster than 3.9.7?
[G1 Android Development] prettyboy85712:
Old news. It will be fixed in the next build.
[G1 Android Development] Glen L:
Force Close Issue!

When your homescreen is full (shortcuts + widgets) then you drag another app from the appdrawer to the homescreen an error occurs
[G1 Android Development] autojack:
Calendar, Market won't load at all (no force quit dialog) with new Cyanogen install

I have an ADP1 and I've just installed Cyanogen 3.9.7. I'm running the pimped 1.4 recovery, and I took a nandroid backup before I touched anything. I'm not running any themes.

When I install Cyanogen without wiping, the calendar and market apps won't work. When I try to load them, the screen changes for a second (white screen for the calendar, black for the market), then just goes back to the home menu. I don't get any force quit dialog or anything.

A lolcat snapshot shows these errors:

W/ActivityManager( 96): Unable to start service Intent { action=android.accounts.IAccountsService comp={com.google.android.googleapps/com.googl

e.android.googleapps.GoogleLoginService} }: not found

W/AccountMonitor( 96): Couldn't connect to Intent { action=android.accounts.IAccountsService comp={com.google.android.googleapps/com.google.and

roid.googleapps.GoogleLoginService} } (Missing service?)

I'm guessing that, without the login service, these apps can't run. I also see lots of permissions errors, but I tried running fix_permissions and rebooting; no luck.

If I do a wipe and install, the calendar works! But then I lose access to all my installed apps. Someone in #android suggested using fastboot to flash my data.img from my nandroid backup to restore the apps. ./fastboot flash userdata data.img definitely restored them... but now the calendar is broken again.

I did search this thread and saw some people reporting the Calendar "force close" issue, but not this "won't even run" issue. So is there any way to switch to Cyanogen AND not have to reinstall all my apps AND have my calendar work? I'm guessing not, other than maybe using one of the app backup programs I've seen in the Market. I'll attach my full lolcat log in case it's helpful. Thanks in advance for any tips...
[G1 Android Development] cyanogen:
I'm back and will be working on the ROM later tonight. I've got a decent list of things to work on, and I'm going to get the Google Code page set up for filing bugs.
[G1 Android Development] salamandar:
Welcome back Cyan, was checkin out that festival you went to online, looks awesome, sometimes I wish I lived on the east coast instead of the west just for the concerts and camping alone! 8P
[G1 Android Development] DirectMatrix:
Cyan, if you need any help maintaining your google code page lemme know....
[G1 Android Development] 4treyu:
If 3.9.7. gets these "memory leak" kind of problems fixed then it will be an awesome rom, cause I find that its battery life is a significant improvement over 3.9.5.