yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] lostcontrol:
This issue has nothing to do with CoPilot Live but with the scheduler I guess. Background processes probably don't get enough CPU cycles.
[G1 Android Development] Chahk:
Try it in command prompt: "adb lolcat" ;)

No, I have not wiped since the early 4.1 releases, nor should it be necessary.

I am running several other apps with background tasks (K-9 Mail, Google Voice, Twidroid, Weatherbug, a few widgets). I don't think this is related to CoPilot specifically, but rather a problem with the new BFS scheduler starving the background apps of CPU cycles.

I thought the same thing. CoPilot is simply the most processor-intensive app I have on my phone, with which I can reliably reproduce the problem.
[G1 Android Development] kerauno:
You could always do a nandroid backup. And do the procedures that I suggested to see if the problem persists. If it does, than you can restore.

Not sure why the resistance to start clean. All it takes is one of your other apps not to work properly because of bad cache to make the phone unstable.
[G1 Android Development] charlus:
Hello all,

first of all thanks a log to cyanogen, this is really great work !

I've installed this 4.1.11.1 as my first cyanogen ROM and it's really great :)

Just one small hickup, I'm also experiencing terrible lags when I close an app and bring back the home screen. I sometimes have a black screen ,then the wallpaper appears then the icons start appearing one after another very slowly.

It might take a few seconds before I have a full 'home page'.

I have wiped & installed yesterday, re-installed my apps ( i've not installed task manager ).

This is the only glitch so far.

My phone is a French Magic, I've not setup any swap.

Any hints to fix this ?
[G1 Android Development] victor.buciuc:
Hey Guys,

can someone confirm that compcache is enabled on a clean installation of 4.1.11.1? Mine wasn't and I also got that lags with the home screen after using the browser.

I've enabled it manually and everything seems to work better. No lag with the home screen.

Also does anyone know how is compcache initialized on boot on this rom? Is there a script or another way?
[G1 Android Development] kerauno:
Did you create a ext filesystem on your sd card?

If so, then try the following in recovery,

Try clearing the dalvik-cache

and run fix ext filesystem

Also, you may have to wipe and reinstall rom after clearing the cache. Not sure how it will work if just clearing the cache. I've always start fresh since it is an experimental rom.

You need to have an ext file system on your sd card for compcache to be enabled. Someone did post instructions a few days back on how to manually enable it without the ext filesystem.

Update: Here is the link on how to enable compcache manually if you do not have an ext filesystem.

http://xdaforums.com/showthread.php?p=4564755&highlight=enable+compcache#post4564755
[G1 Android Development] victor.buciuc:
Thanks.

I remember having compcache on previous versions. Even if i didn't have an ext partition. Why was it removed? I can see there are plenty of people facing the same trouble.
[G1 Android Development] kolyan:
also notice that i got "foreclose" on last.fm even when i am not running it. happened about 3-4 times now. :confused:
[G1 Android Development] cal3thousand:
Uninstall, reinstall.
[G1 Android Development] BigWorldJust:
So the newest update of this is pretty stable :D?
[G1 Android Development] giovannirm:
HI!!!

I have this little problem

I/ActivityManager( 147): Displayed activity com.android.settings/.Settings: 456
ms (total 456 ms)
I/ActivityManager( 147): Starting activity: Intent { act=android.intent.action.
MAIN cmp=com.android.settings/.WirelessSettings }
D/SettingsWifiEnabler( 538): Received wifi state changed from Enabling to Unkno
wn
I/ActivityManager( 147): Displayed activity com.android.settings/.WirelessSetti
ngs: 480 ms (total 480 ms)
D/SettingsWifiEnabler( 538): Received wifi state changed from Unknown to Enabli
ng
E/WifiHW ( 147): Cannot access "/data/misc/wifi/wpa_supplicant.conf": Permissi
on denied
E/WifiHW ( 147): Wi-Fi will not be enabled
E/vold ( 127): Unable to lookup media '/devices/platform/msm_sdcc.1/mmc_host
/mmc0/mmc0:0001'
E/vold ( 127): Error processing uevent msg (No such file or directory)
E/WifiService( 147): Failed to start supplicant daemon.

it's very strange because if I write these commands via adb(without changing enything on the file):

adb pull /data/misc/wifi/wpa_supplicant.conf wpa_supplicant.conf
adb remount
adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf

everything it's ok... but... If I reboot the phone, I have again the problem....

any idea?

p.s. everything else works fine
[G1 Android Development] IConrad01:
I tried looking through the thread and I seem to be alone in this issue; at random my phone will, while sleeping, go into a black screen state and will simply refuse to wake up from it. No key combinations will cause any changes: the only resolution is to pull the battery out and re-start.

That can't be good for the flash memory. Is there a fix for this? I've tried re-flashing the ROM, I've tried fix_permissions; I've tried checking the filesystems for errors, and I recently did a wipe. This is entirely at random; I'll get three such events in the space of two hours and then the phone will stay up for two days straight.

Cyanogen 4.1.11.1, AeroBlack theme.

DangerSPL.

Cyanogen Recovery (latest).
[G1 Android Development] bouyark:
You are not alone with this problem. Same thing happened to me today. I pretty much did the same thing today and now it is all good. I hope the next release find a fix for this issue.
[G1 Android Development] kerauno:
I experienced this same problem the first time I installed 4.1.x and I did the following in recovery. It has not happened since.

clear the dalvik-cache (I actually removed fat32 and ext3 and then recreated them)

fix ext filesystem errors

wipe

reinstall rom
[G1 Android Development] rakjer:
This actually happened to me 4 times BEFORE I rooted my phone. Phone would go blank from sleep, and the only thing I could do to get it working was to pull the battery. I called T-Mobile and they had me wipe the first time, wipe the second, wipe the third, and finally the fourth time I was able to call from a different phone and they had no clue how to fix it, so they sent me a new phone. They gave me no explanation why this was happening or what caused it. It has not happened since.

So it COULD be the phone and not the ROM itself.

Get your phone back to STOCK and call and get a new one like I did if it keeps happening, as now they have the "report" of this problem happening in their system.

You actually need to call 3 different times for the same problem(the tech actually told me this!) in order to get a replacement sent out.(I'm not saying one should abuse this knowledge though.....)
[G1 Android Development] njuncos:
Come issue??

Any others want to chime in here?

This happened to me recently too and if i remember correctly, this used to be referred to as the "coma" issue...however, ever since cyanogen got the 2.6.29 kernel working quite some time ago, it disappeared to everyone's amazement and relief...

could it be that the coma issue is back??
[G1 Android Development] bouyark:
Thanks for the suggestion. I did this as well the first time I installed 4.1.x. For days everything was working fine up until today. As IConrad01 stated, this is a random occurrence. I will remove fat32 and ext3 once again, wipe and install the rom the next time this happens.
[G1 Android Development] rakjer:
If this "coma" happened to me BEFORE I rooted my G1, cyanogen's ROM CANNOT be the "true" cause.

Must be something in the STOCK ROM that is carried over..??..?
[G1 Android Development] kerauno:
Well you shouldn't have to do it twice. Unless you have not done it in 4.1.11 .

Have you been able to post a last_kmsg log for cyanogen when this happened?
[G1 Android Development] mightykc:
I love the latest ROM but when I turn on GPS and use Sygic Mobile Maps the app force closes every time. Anyone know why?
[G1 Android Development] bouyark:
I did it with 4.1.11. I didn't think I could post a log since I removed the battery in order to restart the device. Is it still possible to post the log?
[G1 Android Development] Xidroid:
Remove the app and reinstall it. If it still does it, you will have to wait for the developer to update it and make it compatible with Donut.
[G1 Android Development] Fedburin:
I was having similar issues until I dropped my swapiness from 60 to 30. I have tried linux-swap vs backswapping. Initially, I thought that backswapping was causing my homescreen to reload as the problem went away when I switched to compcache with linux-swap. Upon further investigation I figured out that the homescreen was loading correctly because I had the swapiness set on linux-swap to 30 from a previous configuration. I am now running compache with backswapping and everything seems to be running ok i.e. no reloading homescreens.
[G1 Android Development] TeCH NiNJa:
i cant find userinit.sh in here.....ne1 know where its location is?
[G1 Android Development] blueheeler:
This seems to be a fairly common problem.

I urge YOU and everyone else with this problem to go to CyanogenMod Issue Tracker at:

http://code.google.com/p/cyanogenmod/issues/detail?id=329&colspec=ID Type Status Priority Version Owner Summary Stars Modified

Please login there and report as much information as you possibly can regarding your "coma" problems. It's currently listed as a verified, medium defect. Hopefully, if we all report our same issues, the priority will be raised to accepted & high priority.

If you have trouble with the link above, try this one:

Look for Issue #329 @

http://code.google.com/p/cyanogenmod/issues/list

For me, this is a critical issue.
[G1 Android Development] mormo:
I have this too, this is same after reinstall app, after reboot is same, but when I turn GPS and wait 15 min SMM turn on without error and work. Strange.

I think is a GPS problem because when GPS is turn off Sygic Mobile Maps run ok.
[G1 Android Development] ZilverZurfarn:
I answered the same q exactly 24 hours ago:

You put userinit.sh where it should be - in the root of your ext partition.

It does not come with CyanogenMod (as it's not necessary unless you want to change the way CyanogenMod handles "virtual memory").

/Mats
[G1 Android Development] jbl321:
I have had this problem a few times, and a related one where the screen refuses to revert to portrait mode after exiting an app in landscape. I have found that for me it is ALWAYS the result of having installed a new app, or reinstalled one I used to use under a previous rom (stock or 4.0.4).

I don't say it is the same for everyone; but some apps don't work with this doughnut rom yet. Task managers and killers are for me particularly bad. Uninstall the app and the problem goes away.

(I removed all apps before I flashed the rom a while ago.)

Anyone else find this?

I am not always actually using the new app when the problems occur; just its presence affects performance. After instaling or removing I do a fix_permissions.
[G1 Android Development] The_Chrome_Coyote:
enabled backingswap using userinit.sh and the guide posted by bdb4269 and the homescreen hanging issues are totally fixed!

I used to have slow homescreen repopulation whenever I left Handcent or Market, now it responds instantly like it did in 4.0.4 ^_^ So happy with this again, I was worrying that I was going to have to wipe and reformat to fix it.

100% good compress
[G1 Android Development] Tsanger:
Hello, just flashed my phone with the latest experimental ROM. Noticed that I am no longer able to sync my hotmail account using the email app. I was able to do so with v4.0.4.
[G1 Android Development] tnleeuw:
Problems with messaging app

Although I can't prove it yet, I've only observed the 'black screen of death' bug after using a terminal emulator first. When on 4.1.10.1 I've 3 times used the term. emulator and 3 times, shortly afterwards, hit the 'black screen' bug. I haven't hit into the problem when I had not opened a terminal emulator.

Unfortunately I haven't been able to reproduce the problem yesterday on 4.1.11.1 when I had my USB cable attached.

What I did see however was that after opening a terminal app, Messaging no longer worked properly! (I even lost an incoming SMS message this way). I haven't yet seen any problems with the Messaging app but yesterday after opening a terminal emulator app was the first time.

I've used Better Term Pro, and the Terminal Emulator app.

The error in Messaging is 'Failed Binder Transaction' and messaging shows just a black screen. 'Home' button no longer responds. Hitting 'Back' several times did at least bring me back to the Home screen, but I had to reboot to get back into Messaging.

(I tried opening the Messaging app from the notification of an incoming message, in case it makes a difference here).

I saw several ANR messages from Messaging app, and also from a couple of other apps.

Logs are attached.

NB: In the attached logs there is a lot of noise from some program(s) creating a BufferedReader() with default buffer size... This really muddies the logs :-(

Sorry, I have no idea (yet) which process it is, so I don't know which app to blame or stop.

Cheers,

--Tim
[G1 Android Development] jcdusse1981:
Hello,

I've installed v4.1.11.1 and i have a problem.

Yesterday, at work, i've stopped my dream because the battery was almost empty.

Last evening, i've tried to reload the battery but the led stayed off. I was not able to power on the phone. This morning, the same. When i try to remove the battery in order to restart the phone, it doesn't work :/

Have you got an idea to help me ?

Thank you.

PS: Sorry for my english : i'm french and i don't speak english very well.
[G1 Android Development] tekkitan:
I am also seeing music apps start by themselves. I have noticed it mainly when running other music apps.

If I play music via the stock Music app, Last.fm will start (and force close) in the background. Advanced Task Manager will show it running and I'll kill it.

If I hit play on Pandora (or start it), the Music app seems to start itself and autoplay.

Not sure if this is a problem cyan can fix. Might be an incompatibility with these apps and the Android 1.6 code? Not sure. I'm not a doctor, I only play one on TV ;)

edit: Another update on this. I guess I haven't listened to music much on this since upgrading to 4.1.11.1. Just on new songs while playing Pandora, Music will start up and start playing music in the background. I am trying to figure out if it just does it on songs that I also have on my phone or not, because it seems to only start sometimes not every song change. But I've notices that it had started on two songs so far that I have actually on my phone. It doesn't play that song though. I'm confused.
[G1 Android Development] tekkitan:
Your phone will not power on at all? You don't see an Android boot screen or anything? Verified that the phone is plugged in and getting a charge?
[G1 Android Development] charlus:
Hello,

to follow up on my post yesterday, I've tried to enable compache ( I thought it was enabled by default in this ROM, but after investigating it appears it's not.

I enabled it manually first, it works fine.

Then I've tried to enable it automatically at boot time by creating a /system/sd/userinit.sh script containing the following code :

#!/system/bin/sh

modprobe ramzswap

rzscontrol /dev/block/ramzswap0 -i

swapon /dev/block/ramzswap0

After reboot, I see that my script was not run ( or failed ) since compcache is not enable ( free shows that no swap is allocated ).

I've tried to figure out what was happening by capturing boot logs ( adb logcat ). The first line I see is this error :

I//system/bin/sh( 54): +++ Welcome to Android 1.6 / CyanogenMod-4.1.11.1

I//system/bin/sh( 54): vm.page-cluster = 0

I//system/bin/sh( 54): --- Loading kernel modules

I//system/bin/sh( 54): [: 1: unknown operand

I/logwrapper( 54): /system/bin/sh terminated by exit(0)

So it appears that a start-up script is failing, which I guess will have some effect on the rest of the boot process ...

Has anyone also this error ? Any hints on how to fix it ( I did a quick search and could not find any reference to this text ).
[G1 Android Development] ZilverZurfarn:
Why reinvent the wheel? Try the userinit.sh/user.conf combo:

http://xdaforums.com/showthread.php?t=542899

It works well for me at least.

/Mats
[G1 Android Development] charlus:
Hello,

I confirm that compcache is not enabled by default on my clean install of 4.1.11.1. ( see my post here )
[G1 Android Development] charlus:
Hello,

thanks for the hint, I'll check that right away and report success/failure.

Any hint on the error message I reported at boot time ? Are you getting this too ?
[G1 Android Development] karolbe:
I have similar experience...unfortunately sometimes it can drop a call a few times in 5 minutes and I am sure that this is not caused by signal loss or the other end. Unfortunately I wasn't able to collect logs so it's difficult to say what's causing it.

I am using the latest Cyanogen 4.1.11.1...but it happened also with a older Cyanogen's roms.
[G1 Android Development] ZilverZurfarn:
Nope, I use Linux Swap.

/Mats
[G1 Android Development] jcdusse1981:
No, not power at all. It's not breaked : it don't boot at all.

It is still plugged in correctly and the led is still off : it seems not charging :/
[G1 Android Development] charlus:
Well I did the setup & config.

Then I rebooted and captured the logs.

Same error shows up at first line during boot :

I//system/bin/sh( 54): +++ Welcome to Android 1.6 / CyanogenMod-4.1.11.1

I//system/bin/sh( 54): vm.page-cluster = 0

I//system/bin/sh( 54): --- Loading kernel modules

I//system/bin/sh( 54): [: 1: unknown operand

I/logwrapper( 54): /system/bin/sh terminated by exit(0)

And it appears that the userinit.sh was not run since I have no swap after boot.

However if I run /system/sd/userinit.sh manually then everything is setup correctly.

Here's the output :

# /system/sd/userinit.sh

swapoff: /dev/block/ramzswap0: Invalid argument

rzscontrol /dev/block/ramzswap0 --disksize_kb=24576 --init

vm.swappiness = 60

find: /system/app/*.odex: No such file or directory

# free

total used free shared buffers

Mem: 98024 93952 4072 0 1476

Swap: 24572 0 24572

Total: 122596 93952 28644

So it confirms that on my installation ,userinit is not run at startup :(

I have a strong feeling that it's a consequence of the error I'm seeing in the logs.

As I said, it's a fresh install of 4.1.11.1, after a wipe.

I've just installed some apps.

I should not be the only one seeing this error message...
[G1 Android Development] tekkitan:
I'd take out the battery and reseat it into the phone to make sure it is in there correctly. If that doesn't work, not sure what else for you to try other than trying a new battery.

You could try posting in the Q&A forum, perhaps you'll get a few more suggestions. This doesn't seem like it would be related to cyanogen's ROM at all. Seems more like a physical problem to me.
[G1 Android Development] blueheeler:
I had the same problem several months back. I took my phone & battery into a T-Mobile store, and they used their charger to see if it would bring any life to phone. It wouldn't. They also put in a battery from a known-working G1, and it wouldn't power-on or charge either.

End result: probably a bad motherboard.

T-Mobile had no problem sending me a replacement.

The store manager made the arrangements and they even did Express Delivery for the same price as normal delivery. Even lent me a phone to use for the 2 days I waited.

If you know anyone with a compatible battery, it's worth trying their battery. If that doesn't work or you don't know anyone, take it into a store.

Don't mention that you've customized your phone !
[G1 Android Development] jcdusse1981:
I've ever tried to remove the battery but that still doesn't work.

I've forgotten to explain that the battery was empty because of the keyboard stayed lightened all time, also when it was off. That's i've posted my problem here ;)
[G1 Android Development] jcdusse1981:
Ok, thank you very much for your advice :)

I will contact Orange France to replace it as soon as possible !
[G1 Android Development] tnleeuw:
As userinit.sh does run properly on my system, just a sanity check: the permissions on your userinit.sh and user.conf are set correctly? Owner / group root (0), userinit.sh should be executable? Files readable by root user at least?

--Tim
[G1 Android Development] wardy277:
I have had the icons disapear on me. i have read that just adding them again will sort it. But now i have 2 icons under one place. IT looks kinda odd. It does this with widgets too. i went to move the weather clock widget and there was another one underneath.

How do u kill the home process. it doesnt appear in advanced task killer free.

Is there another free one that will shwo it?

Chris
[G1 Android Development] charlus:
Yes, I've double checked :

ls -l /system/sd

-rw-r--r-- 1 0 0 0 Aug 1 2008 placeholder

-rw-rw-rw- 1 0 0 2571 Sep 22 09:32 user.conf

-rwxr-xr-x 1 0 0 20964 Sep 6 08:49 userinit.sh

As I said when I run it by hand it works. It's just not being executed at boot time.
[G1 Android Development] karthikjr:
Seconded! I've posted issues with contacts and BSOD before.

I'd thought the crashes were on account of TasKiller.

Uninstalling TasKiller didn't help.

Better Terminal seems to be the only other app that

was run just before bad things started to happen.
[G1 Android Development] userfriendlyme:
have you tried using another charger or perhaps seeing if it will start charging by using the USB and plugging the phone into the pc? Seems that the phones not gonna come on if the battery is completely dead. I would say its and issue with the Battery before i say the phone. If neither works i would try and take the phone to a dealer see if you can test another battery. Ive went through 3 batteries on my phone so its certianly possible.
[G1 Android Development] jcdusse1981:
I've tried using both charger and usb cable and that never works :(
[G1 Android Development] _Belial:
Just installed this on my magic 32B, and love it, fastest rom i've tried so far. My only gripe is that i'm missing full exchange support (Contacts/calendar + mail). Is there an apk somewhere which will give me full support with this rom?

many thanks
[G1 Android Development] jcdusse1981:
Good news : my dream is alive :p

On a french forum, someone advise me to press randomly on the frontal keys and at a moment, the led has powered on ^^

After that, i was able to power on the phone :)

Thank you all for your help :)
[G1 Android Development] tekkitan:
Never heard of that, but good to know for the future. Glad it's working again.
[G1 Android Development] merps:
don't mean to be an arse Charlus - seems that there could be a slight problem with the syntax of your userinit.sh script? Just from the earlier message that you posted (post #8814),

I//system/bin/sh( 54): [: 1: unknown operand

I/logwrapper( 54): /system/bin/sh terminated by exit(0)

sorry as I am still running cm 4.0.4, upgrading - again to 4.1.11.1 so I am not sure if this is a known issue with cm 4.1.11.1 or your script - which shell are you calling?

just my two cents, fwiw...
[G1 Android Development] charlus:
Thanks for the reply.

I'm getting this error regardless of the userinit.sh script used.

I was having the exact same error with my home made userinit.sh script containing only

#!/system/bin/sh

modprobe ramzswap

rzscontrol /dev/block/ramzswap0 -i

swapon /dev/block/ramzswap0

So I'd say this comes from another part of the system.

Since it's the first line in the log I suspect a script running early during the startup process, maybe in initrd if there is one in this ROM.

I'll try to dig into this. But for me it's definitely related to 4.1.11.1 and not to the userinit script.
[G1 Android Development] farmatito:
Try to change this line of a2sd

if [ `getprop cm.a2sd.active` != 1 ];

to

if [ `getprop cm.a2sd.active` -ne 1 ] ;

or to

a2sd=`getprop cm.a2sd.active`
if [ "x$a2sd" != "x1" ] ;

This should fix the warning.