yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] pinetreehater:
Use Wireless Network

Use Wireless Network will not seem to hold its setting (enable). I also notice dependencies are not operating (such as google maps and the google search page>>my location for search) correctly.

When I select use wireless Networks, it pops up and ask if I will allow google to use my location for improved search results. But the check mark doesn't stick.

No themes. No wipe. Attached logcat
[G1 Android Development] bkmo:
Known issue on 3.9.6, supposed to be fixed on 3.9.7, but I am still downloading it on my GPRS connection. :(
[G1 Android Development] TheGreenJester:
I can also confirm that this is happening. I had it enabled, but once I disabled it - enabling will not stick.
[G1 Android Development] persiansown:
I'm posting this issue again because it got buried last time. It also happened again on 3.9.7

I had an issue with messaging. I had the old messaging app with the modifications manually installed as an app. When I updated, that one remained instead of the updated one, so I uninstalled it. When I did that, there was no messaging app at all. I tried replacing the default Mms.apk with the one I downloaded from that thread and there still wasn't a messaging app. After reflashing, it still didn't appear so I just installed it in data for now instead of /system/app.

Any ideas why Cyanogen? I thought placing the apk into /system/app and then rebooting should install it, but it didn't. What freaked me out though was that even reflashing didn't bring it back.
[G1 Android Development] mewnz:
I found the same issue, however..

if I turned on GPS locating as well, exited the menu, then went back in and turned off GPS, the wireless setting would stick.
[G1 Android Development] oldsk00lz:
3.9.5 with overclocking of 384/528/200

Okay, I have 24pages of new posts to read, and will do so soon. I also see that there is an updated version, but wanted to go ahead post some quick 3.9.5 findings from my tests today.

I have been running it with the Overclock settings of 384/528/200 (min/max/powersave) today, and it has been running GREAT. I have been running for 13 hours and still have power.

7:15a 100%

8:15a 96%

10:30a 90% (3g enabled, still hitting 2g network though)

11:40a 86%

2:05p 80%

3:42p 75%

5:30p 68% (now accessed 3G network)

6:56p 50% (steep dive, but activated GPS, as well)

8:22p 10% (STILL FAST DIVE - Left GPS on, but not using, also 3G on but not browsing, and had a 1hour+ call.

8:27% 8%

Battery usage shows Call=32%, Voice=32%, Standby=29%, Screen On=6%

From above I see that I was getting great battery life on 2g, and then as soon as I could reach the 3g network, I started getting pounded. Might have been GPS, I should have turned off when I was done with it.

I look forward to testing the new build!!! Nice!

-oldsk00lz
[G1 Android Development] pinetreehater:
Temp Fix for wireless network enable

Actually...that works. Temp fix is better than no fix. Added something in brackets to your quote...it is what you meant anyway, just clarifies.
[G1 Android Development] wesbalmer:
Any info on using the rzscontrol command would be much appreciated.
[G1 Android Development] pinetreehater:
Start here http://xdaforums.com/showthread.php?t=542899...huanyu has made it quite simple to understand with a lot of work helping people get this going.

BUT, at post 115 there is an improved script by Uwonsum. It maintains the ability to easily configure a bunch of settings (see sig), but also supports the new .6 compcache (which requires rzscontrol).
[G1 Android Development] mewnz:
Translated from Australian, I'd say thats what I meant :-)
[G1 Android Development] cyanogen:
Cpu scaling is set at 245 min, 528 max with powersave_bias at 200. The only /proc setting I'm doing is /proc/sys/vm/page-cluster to 0. The tweaks for settings laptop-mode or dirty_writeback_centisecs I think are unsafe and will cause you to lose data.

I'm not really sure. The sure-fire way to reset it is to make sure you have no copies of it on your device, then edit /data/system/packages.xml and delete anything for com.android.mms (then reboot/restart).
[G1 Android Development] Janis:
Just jumping in

This feels more like a chat room it moves so fast.

@Cyanogen: the extra line isn't a big deal, but it would show off your attention to detail if you fixed it. I was wondering about it, but "ehhhhh" suits perfectly.

@mak213: Market DL AudioHack. It's worth it, both in the ease of resetting it when you get in your car, forgot you flashed last night and you barely heard the ringer, AND in supporting a really top notch, cutting edge developer. It's cheap, and buying from someone really is showing your support, for good or ill.

@Pinetreehater & ThGreenJester: I turned off my GPS, then enabled Wireless Networks, closed out of Settings and it stuck, then went back in and turned my GPS on. Hope that works for you. (I got the feeling that the phone was saying "what do I need that vague crap for, I've got GPS! Well dang, if you're gonna take my GPS I guess I'll have to live with Wireless.... Oh, thanks for turning the GPS back on, just for that I'll keep them both on for you." I wasn't sure if I should thank the phone or what.)
[G1 Android Development] paindoo:
Browser is FC

I just had a fresh install of 3.9.7 and oddly my browser is force closing everytime I tried to launch it should I push the browser.apk from previous release?
[G1 Android Development] tekkitan:
First goto Settings>Applications>Manage Applications>Browser then click "Clear data"
[G1 Android Development] cyanogen:
I'll take a look at the network location weirdness. I think some rabid donuts might be there.
[G1 Android Development] tekkitan:
/me tosses cyan a holy hand grenade :P
[G1 Android Development] ogwilson:
Just a question. I saw that someone had problems getting their icons/homescreen widgets getting back on. Mine too have disappeared, and I saw that he suggested running fix_permissions in terminal emulator. I did this, however I keep getting permission denied and operation not permitted on all of the operations that command tries to execute.

Does anyone know how I'm supposed to be doing this?
[G1 Android Development] zimphishmonger:
That has been answered. The hero apps and framework are closed-source and are tightly integrated to one-another (meaning VERY difficult to port), which means we dont have access to the source code to make changes, etc.

Cyanogen even commented regarding it in the FAQ
[G1 Android Development] zimphishmonger:
Best quote on XDA...Sorry for being off-topic
[G1 Android Development] on1ydabest:
SU Request

After flashing from 3.6.8.1 to 3.9.7 I seem to have lost root on the Android side. It works perfectly fine from recovery. When I try to execute a program that requires SU, Superuser Permissions opens up but either stals or crashes or both. I also tried su in terminal, no luck. I tried typing telnetd and connecting to local host via telnet, no luck. Anybody have any suggestions?
[G1 Android Development] miketaylor00:
Make sure your USB debugging is enabled. I think that was the fix when this was a problem on an old JF build.
[G1 Android Development] DownloaderZ:
gmail issue

NOTE: NOT SURE IF THIS IS CONSIDERED A GMAIL TIMEOUT, IT IS PLEASE IGNORE AND LET ME KNOW

Hi bug/issue report

i went from 3.9.4 to .6 and it obv went to the g1 screen.

Then i nandroided back to 3.8.6.

And now i am on 3.9.7

on the backup and on the .7 gmail messages wont send and just sit there and say sending....and never send.

Would a log of me sending a message help?
[G1 Android Development] cyanogen:
Run "su" first, or do it from recovery.

Probably not ROM related unless you have some exceptions in the log.
[G1 Android Development] DMKrow:
Calendar bug remains in 3.9.7

I believe this bug remains in 3.9.7 - I saw the same logcat messages. I did a no-wipe upgrade from 3.9.6->3.9.7. I did a search, and no one seemed to mention the calendar bug, so I hope I am not repeating.

recreate the bug by setting appointment and then snooze or dismiss the alert.

Issue: Calendar snooze exception "WHERE based updates not supported"

-DMKrow
[G1 Android Development] alapapa:
if you don't want to use the large, elegant script...you can set up compcache with this build like this:

#!/system/bin/sh

modprobe ramzswap;

/system/bin/rzscontrol /dev/block/ramzswap0 --backing_swap=/dev/block/mmcblk0p3 --memlimit_kb=32768 --init;
swapon /dev/block/ramzswap0;

..the backing_swap & memlimit_kb flags are optional

you can get stats like so:

rzscontrol /dev/block/ramzswap0 --stats
[G1 Android Development] cyanogen:
Okay, I'll test it for the next build. I'm building the very latest calendar code, so there might be something bad in there.
[G1 Android Development] MattyMatt5481:
Anyone else having trouble putting the myfaves rogram on the new build, I ran a zip for it and flashed using the terminal, and it doesn't appear on the ap drawer, even after reboot
[G1 Android Development] Janis:
Comment: battery still there after 3.9.5, not after 3.5.7

I just did two no wipe flashes 3.9.2 -> 3.9.5 -> 3.9.7

(I put way too much time arranging my appdrawer. It's not the leanest UI for setting it up.... Is that saved in system data, or is it in app data? I'm afraid to find out. If it doesn't get backed up with system settings, can anyone tell me how to back it up? That and Locale settings are really the only things preventing me from wiping.)

The battery in the menu screen was still there after I flashed to 3.9.5, but it disappeared after I flashed to 3.9.7.

I thought it was odd; not problematic, just mildly interesting.
[G1 Android Development] tekkitan:
The battery meter went away in 3.9.6. Read the changelog in the second post.

edit: you said menu, did you mean lock screen? if not, sorry i misread :)
[G1 Android Development] lukekirstein:
Good job buddy, you just found one of the new features. Check the Change-log, and you wouldn't have to "discover bugs" :D

Myfaves has never worked, will never work, and it's a waste of time to try and get it to work. You can edit online, and still get MyFaves rates.
[G1 Android Development] rondey-:
Not true. You need to remount /system/app as rw then copy the myfaves.apk over, reboot. Contacts might disappear for a minute but google will resync them. More in depth directions and the apk can be found here.
[G1 Android Development] oldsk00lz:
Rom: CM3.9.7

Issue: Power Control widget does not reset the GPS status (green bar) to the updated GPS state, when GPS state is changed manually through settings (and Toggle Settings app). It looks like changing the Wifi and Bluetooth manually works fine, and will refresh itself and the proper GPS status in the widget. Note that the widget updates correctly when toggling GPS from the control.

Severity: no biggie

I am going with the new CPU settings delivered in ROM (245min) versus 354min which I was using. I'll test and report back on battery usage.

-oldsk00lz
[G1 Android Development] uwonsum:
You are correct--seems to be just be a refresh issue...does not have any negative effect.
[G1 Android Development] mewnz:
calendar reminder causes FC

have noticed an issue when I set a calendar appt, after the reminder event occurs, I get an FC from the calendar storage app.

It occurs when I dismiss the reminder.

I have cleared the storage data in application management and forced a resync, but problem still occurs.
[G1 Android Development] spacezorro:
sqlite problem?

With v3.9.7

I am getting piles of

with Force Closes
[G1 Android Development] NeoBlade:
DKMZ and myself have posted about this issue and Cyanogen has kindly replied saying he'll be looking at it. He's been adding some new bits to the Calendar from what he said so just hang tight until a solution is found.

It annoyed me though so I had to remove my test notification from the Calendar itself, then let the notification crash by pressing dismiss all and it went.
[G1 Android Development] monossidoz:
I can not change the brightness, it is only my problem?

I can not from the UI but from the shell works

echo "120" > /sys/class/leds/lcd-backlight/brightness

version 3.9.7
[G1 Android Development] damokay:
Just flashed 3.9.7 and no probs changing brightness here (either from the widget or settings menu).
[G1 Android Development] innerspace:
3.9.7 -> great success!

Thanks for sorting out what was apparently a boot.img size issue on 3.9.6

Flashed 3.9.7 from 3.9.5 and all is well. Must say, initial boot took a long time, probably about 6/7 minutes.

I'm not seeing any force closes, not having any issues with brightness or wireless settings not sticking or any other issue mentioned since its release, though I rarely use reminders in my calendar. All in all looks solid. I will say I'm noticing a significant slowdown when running w/out compcache & backing_swap. I'll be heading on over to that wonderful compcache thread now and setting it up.

Thanks again cyanogen.

On a personal note, my family is from North Hills... always was a Steelers fan at heart, you just make it easier.
[G1 Android Development] yukkio:
Cyanogen I'm trying to port to magic your last rom (like old roms for personal use). Have you made something different in 3.9.7 boot.img? I can't unpack it with my mkbooting. I think I need a new mkbooting from donut.

Sorry if this post breaks any forum rule.

Thank you.

BR.

Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
[G1 Android Development] sillyshy:
I have installed everything the right way and for past 10 mins I get the android loading screen blue letters with white movements and did wipe install and did it over still same old problems.

All I did to install was ALT W and ALT S after it was renamed.
[G1 Android Development] ZilverZurfarn:
Run logcat during boot to see where it stalls. Post relevant parts of the log. Then maybe someone can start figuring out why it wont boot.

/Mats
[G1 Android Development] robpet2:
also if you are flashing to the newest build from a themed version, flash back to non themed version of cyan thread before flashing to the newest cyan rom... Not sure if people are getting errors due to this, but it could be one reason...
[G1 Android Development] sillyshy:
No this was never themed it was just rooted today. CYanogen 3.9 takes forever to load keeps showing me the andriod screen.
[G1 Android Development] sillyshy:
What is that and how do you run it?
[G1 Android Development] tekkitan:
Have you tried the latest stable build to see if that works? (3.6.8.1)
[G1 Android Development] ZilverZurfarn:
I guess you mean logcat? It's an ADB command that logs the phone activities on your computer when hooked up via USB. Not to be condescending, but if you have to ask, this ROM is not for you. It's an experimental build, and those who install it are supposed to help debugging it.

/Mats
[G1 Android Development] richpadg:
One thing I have noticed and was hoping to get some help with. On my G1 #1 the available memory is 64mb / 74mb but on my G1 #2 it is 80mb / 89mb. Just wondering why I would have 89 total on one and only 74 on the other. Both are running pretty much identical settings.
[G1 Android Development] innerspace:
adb is the Android Debugging tool included in the Android SDK. I'm just going to venture out on a limb here and recommend you head on back to the stable thread and build 3.8.6.1, the 3.9 builds are EXPERIMENTAL and not intended for general use. You need to do some reading my friend.

As for the current release...

G1 is literally running like a Dream after enabling compcache w/ backing_swap using the newest userinit/user.conf combo. Absolutely fantastic work cyanogen, I can't wait to see how things round out with 4.0. I have this sneaking suspicion you've got a bombshell up your sleeve.

Still no issues at all, no FCs - nothing. Lovin' it!
[G1 Android Development] userfriendlyme:
3.9.7 works good for me so far. I've had it on since its been posted and seems to be running as good as 3.9.6 for those who were able to flash it. I do think the battery life is greatly improved for me on 3.9.7. Just using my phone like normal since its been updated and im seeing the much better levels and not a loss of performance.

Will you still be including the adjustable setting for the power usage in your update? I haven't enabled compcache or Swap and don't think i will...it's doing what i need with out it. As always good work Cyanogen more beer coming.
[G1 Android Development] innerspace:
At one point on 3.6 builds I was down to <20MB free internal memory, couldn't figure out why until I blew out the partitions on my sdcard and started from scratch, instant 70+MB free after the first flash. **********************************
[G1 Android Development] richpadg:
Would this actually have an effect on how much is actually available to me? Not how much is free, but the total system internal memory. It's like I have lost 15mb somewhere.
[G1 Android Development] robpet2:
why ext4 ??? why...

use ext2 or ext3...

does this rom say that it supports ext4?? - http://xdaforums.com/showpost.php?p=4185546&postcount=2
[G1 Android Development] innerspace:
I'm sorry, I didn't say that right at all... need sleep I guess. I was losing internal memory as you are, seems that others were having similar problems. I'm not entirely certain why it happened, I just know that after completely blowing out the partitions and reflashing from scratch the issue disappeared, so I'd venture to say this is not related to the ROM at all but is something else entirely. Maybe hit Q&A with the question.
[G1 Android Development] All~G1:
I would check what SPL's you have. I do know that Haykuro's "Danger" SPL saved IM, someone please correct me if I'm wrong. You could also take innerspace's advice. I personally had a lot of problems with 3.9.5+ and after I reformatted the EXT partition I've noticed a big change in stability on 3.9.7, but I did not gain or any IM.

EDIT: Also you can clear you dalvik cache to gain more available IM, but it wont acctually increase the amount of IM you are capable of having.
[G1 Android Development] innerspace:
ok... CALM DOWN... ext2/3/4 doesn't matter at all... at least not in regard to his issue. And the changelog you linked to doesn't say anything about partition formats. ext4 is the latest format. Its been working fine for me for a loooong time.
[G1 Android Development] jroid:
works fine for me too. Believe me if cyan himself said a long time ago that he was running it and said it was better than ext3 and actually implemented it with gparted it really must be better than ext3.
[G1 Android Development] ScottGood:
Cyan,

I think you misunderstood my post, I was merely telling temp what I did with the launcher zip because I'm seeing Drawable files in my gallery and can't figure out why. that is all, I'm guessing user error and I need to track down the files on my SD card and remove them.

My point is, I thought I found a bug
[G1 Android Development] jawash22:
Just open up keyboard and close it...easy...:cool:
[G1 Android Development] YPhoto:
I went back to compcache for this build with a swappiness of 40. Was running great, but after a few hours of normal usage, started to see lags, some very long followed by fc/waits. I was not experiencing this earlier today while running a 32 meg linux-swap file. I will play some more, but I think I may go back to the swap.
[G1 Android Development] ubernicholi:
try compcache with swappiness set to 20 and set to 32 megs. no issues on my end, alternatively try setting it to 24 megs
[G1 Android Development] YPhoto:
Thanks, changed and we'll see what happens.
[G1 Android Development] Chahk:
I haven't enabled compcache yet, just running linux-swap partition. With previous builds there have been reports of issues related to compcache, such as slowdowns and phones running hotter than usual (both in my case actually). Has anyone experienced this on 3.9?
[G1 Android Development] southsko:
How do we access the OTA updater. I didn't see any app... command line?

Thanks for the update
[G1 Android Development] jubeh:
i've always found checkin and system updater fishy, i never knew what checkin did, though, but ever since I started modifying roms to fit my needs, i always remove system updater. I've always felt it had something to do with google or t-mo pushing OTA updates to my phone w/o my permission and take my root away. I'll ask again, can you do away with checkin if you do away with the setup-wizard too? will it affect anything. I guess it's something I can try myself.
[G1 Android Development] Hummeroid:
Quite warm. Like, hotter than a macbook warm. I thought it was just from charging, but then I realized it was unplugged for over an hour...
[G1 Android Development] firetech:
I flashed 3.9 today, coming from 3.6.8.1, which I wiped a few days ago (no wipe for this upgrade though), and I'm seeing strange behavior with the time (of day) selectors in the calendar (not sure if it was there in 3.6.8.1, haven't used the calendar for a while).

Even though I'm using a 24 hour clock, the time buttons when creating an item sometimes (haven't really gooten the hang of when, but mostly when the end time is changed automatically after changing the start time) show 12 hour time (which is then parsed as 24 hour time). Clicking on the buttons show the 24 hour time in the boxes and 12 hour time in the title until you change one of the boxes with the +/- buttons.

Also, typing manually in the boxes and then pressing "Set" has no effect. I have to use the +/- buttons (which do affect the manually entered values, though). Can this be caused by the new AOSP patches perhaps?

Other than this, the ROM feels solid! :)

EDIT: It seems like it always parses the 24 hour times before 12:00 as 12 hour times in pm when opening the time edit windows (it is pm here now, might affect the situation). Note that even though the edit windows parse the time wrong, it is still correctly saved.
[G1 Android Development] Diceman4:
You don't see it because it isn't there yet :D It is listed under Ideas to Implement (i.e. ideas not yet completed but planned)
[G1 Android Development] phantasm714:
ive had compcache running on CM since it was available (currently on 3.9) and have not had any heat issues. i have had some minor lag issues depending on the swappiness, but 20 seems to be the sweet spot for me.
[G1 Android Development] temporizer:
I stuck with swap because of the heat issue. Plus I think it runs smoother than compcache, imo.

I noticed this too, first with the clock tho.

It automatically reverts to PM upon opening: If you set it for AM and close it, it stays. If you edit the time, it reverts to pm,

Confirmation?
[G1 Android Development] drpfenderson:
No...no need to reboot. As said before - just rotate your screen.

As mentioned before, try lowering your swapiness to 20 (or 40, if you feel it necessary). I've been running Cyan's ever since adding compcache with those settings, and have not had any heat problems whatsoever. Processor is clocked at Cyan's default and I use it pretty regularly. No slowdown over time, lag, or anything.

I was having a lot of problems when it was set at 60. But not many since lowering. There is some good info on swappiness levels here, and it mostly comes down to high numbers for desktops, low numbers for mobile devices. Since the G1 runs only a few programs/processes at a time, lower swap doesn't affect it as badly as on a desktop/server machine. Also, reading through this paper on compcache should clarify some tweaking points.
[G1 Android Development] BigWorldJust:
How stable is this? Thinking of going to this or 3.6.8.1.