yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Nedlinin:
Fastboot is not a regular style boot. You hold down the Camera button while pressing power.

This style of booting is pretty much failsafe as far as being recognized by the PC. Booting like this, I am recognized and was able to erase boot.
[G1 Android Development] Nedlinin:
With the card removed, I still get stuck at the same place (G1 splash without the ability to use adb)
[G1 Android Development] anon1ski:
oh ok. i thought i read a couple pages back that someone couldnt even get into fastboot somehow thats why i said from what i hear. i havent even tried fastboot because i dont have my usb with me :mad: apparently i misread:o
[G1 Android Development] mirox3m:
The same G1 screen ........
[G1 Android Development] DownloaderZ:
I'm not nor every did I use apps2sd and I still was stuck @ g1 screen

Now now 3.6.8.1 from nandroid
[G1 Android Development] tekkitan:
hmm, guess it isn't that then. not sure what else it might be. seems pretty widespread though.
[G1 Android Development] 4treyu:
Damn, now that's scary. Could I have been so extremely lucky? I guess we'll all be flashing 3.9.7 soon enough.
[G1 Android Development] borodin1:
3.9.5 ->3.9.6 with no wipe. No problem. First boot took forever (over 3 min). All apps survived, as far as I can tell at this point. Speed is awesome, responsiveness is better then average. Comcache was easy (something I could not achieve in previous builds, thanks for the walk-thru Cyan). Miss the old lock screen... will survive.

Did not see anything new right away, must be "under the hood" changes.

Preliminary judgement: another solid build from Cyan.

Good luck to all of those having problems.
[G1 Android Development] andrew richardson:
WOW! this rom is hella fast!

One of the tests I use is to open several background apps, then rotate the screen and open the app drawer. No lag or stalling!

Just on a wild guess, did some of the donut crumbs include a new accelerometer driver? :D It's REALLY sensitive now! Play some music in the background and run the "Bubble Level" app. Watch it jump around. It was also causing my screen to occasionally "dim out" like it was going to rotate, but didn't.

No other issues so far. Actually, the music-accelerometer doesn't bother me. Start the music, start up "Bubble" and call it a music visualizer! It's a new FEATURE! :D

Thanks again for the great work!
[G1 Android Development] marshallladd:
I never used compcache at all. To use it and enable it via cyanogen's instructions I assume I will need a third partition on my sdcard. What format should it be in and what size? Sorry if this is a dumb question.

And now it is looking like it won't matter for now since I to can't get past the G1 screen. I upgraded with no wipe from .5, and no theme, no previous compcache or usernit script.
[G1 Android Development] cidica:
Just wiped and flashed 3.9.6 and right now I'm at the setup screen no issues. I did wipe sd and and the system. But no problems here so far boot up did take some time but thats normal so I'm used to that but so far so good it seams.
[G1 Android Development] Keyser.Soze:
I have app2sd but I updated to 3.9.6 from 3.9.5 w/o wipe and everything is fine. I went from Haykuro 1.5r2 -> CM 3.6.8.1 -> 3.9x all the way to 3.9.6 without wipe and had no issues.

KS.
[G1 Android Development] KNK:
Okay installed 3.9.6 after a wipe and sd crd format, I can not enable Location services ... it gives me a force quit on android settings.

Can anyone try this to see if it is just me?
[G1 Android Development] anon1ski:
hmm. i wonder what the criteria is for having the problem........it seems to be hitting people with all different types of setups.
[G1 Android Development] :
Upgrading from 3.9.5 to 3.9.6.

Flashed 3.9.6 ROM and 3.9.6 themes. Rebooted, stuck at G1 screen.

Removed userinit.sh (w/compcache) and rebooted, stuck at G1 screen. Pulled battery, wiped, restored from Nandroid backup that I did when @ CM 3.6.8.1 stable, then reflashed 3.9.6.

I've been at the G1 screen for over 5 minutes with no visible progress.

Reflashing to 3.9.5, I have no problems.
[G1 Android Development] borodin1:
Skim comcache thread and then last couple of pages in this thread once you get the rom going and you should have a good idea on how to set it up

Good luck
[G1 Android Development] borodin1:
In "Security and Location" menu? I have both GPS and Wireless enabled, no problem. Or do you mean something else?
[G1 Android Development] innerspace:
a little background info...

well, just to contribute some clarification.

steps i took:

already had backup of 3.9.5

downloaded 3.9.6, pushed to sdcard

adb shell reboot recovery, anyzip flash

reboot, stuck at G1 screen...

thought - whoops, I'll bet its that pesky userinit file

reboot recovery, adb shell, cd /system/sd , ls = no results...

thought, hrmmm... that's weird

reboot recovery, switchrom back to 3.9.5

adb shell, rm user.conf , rm userinit.sh

reboot recovery, flash anyzip to 3.9.6 again

stuck at G1 screen.

insert facepalm.

reboot recovery, adb shell works

tried fastboot erase boot, stuck at <waiting for device>.

restored 3.9.5 via switchrom again, started torrent of Harry Potter film in hopes it will keep me up long enough to see a fix. Posted this.

So I haven't wiped my sdcard yet, am wondering if this could be an issue with dalvik cache or something else, or are we too early in the boot process for that to be an issue?

EDIT -> Also, I simply must know, what are our top four concerns?
[G1 Android Development] firetech:
I'm also getting stuck at the "G1 screen" (which on my phone is an Android screen without animation, since it's an ADP1) in 3.9.6. Logcat never kicks in (stucks at "waiting for device", and flashing the boot.img from my 3.9.5 nandroid backup doesn't help. Tried both with wipe (wiped after flash, though) and without.

3.9.5 works without problems, and since I downloaded 3.9.6 with the getcyan script, it's md5sum was checked and confirmed to be correct. I'm using apps2sd, but booting without the sdcard didn't help either. If this isn't a problem in the ROM itself, I guess solar flares must have hit every affected phone... I'm crossing my fingers for you fixing it, cyan!
[G1 Android Development] KNK:
Nope that's what I meant. Went to Settings > Security and Location > Use Wireless Networks and I get a Force close on android.settings :(
[G1 Android Development] cidica:
I just tested mine as well and I'm not having the issue able to turn on and turn off with no force closes.
[G1 Android Development] cire253:
no problems

I flashed and had no problems.

1st - Nandroid backup

2nd - Wipe

3rd - Apply update

4th - Reboot

works fine for me
[G1 Android Development] borodin1:
You're right... just unchecked both and rechecked them - same thing force closed...looking thru the log now....
[G1 Android Development] andrew richardson:
Hmm. I didn't have any problems, even still had my compcache script still in /system/sd. No wipe, the only thing I did different is, a few hours ago, I deleted my dalvik-cache while I was still on 3.9.5. :confused:

It did take a little longer to boot, maybe 7-8 min or so, usually takes about 3-5.

Maybe I just got lucky. :confused:

Hope it gets figured out for everyone.
[G1 Android Development] cyanogen:
I know what's causing it, I think. Need to sleep first though. Update later..
[G1 Android Development] userfriendlyme:
After the whole userinit.sh issue with updating to his 3.9.5 build i didnt enable compcache at all after the update. I flashed 3.9.6 without any problems moved right past the G1 screen.
[G1 Android Development] firetech:
Can the 3.9.6 problem be SPL specific? My limited research says that all who have gotten 3.9.6 to work (and have their SPL in their signature) run HaykuroSPL or HardSPL.

I'm running the original SPL on ADP1 (EngineeringSPL if I'm not mistaken, don't really want to change it either). Could this be it?
[G1 Android Development] anon1ski:
sounds good man. thanks for everything.

and as for the spl problem, im running haykuros spl. and still nothing.
[G1 Android Development] The Spirit:
runs very smooth and without any problems
[G1 Android Development] damokay:
Quick question (while I am sat here watching my G1 boot up screen and wondering whether I have waited 8 minutes or not)... assuming this rom does boot for me does this mean I can just delete userinit.sh or do I need to find the backup I took before I started playing with compcache?

Thanks
[G1 Android Development] cyanogen:
If someone with the issue could try pushing vold from 3.9.5 onto their /system/bin from recovery, that would eliminate my #1 concern.
[G1 Android Development] damokay:
Nothing in my sig yet but I'm running HardSPL and I seem to have been looking at that screen for a looooong time!
[G1 Android Development] innerspace:
I think that's not related, I'm running the HardSPL, just don't have it in my sig, was running out of room ;) I'm gonna take a wild stab in the dark and speculate that this has something to do with the io change, dalvik-cache or kernel changes. Bear in mind I have NO IDEA what I'm talking about. None-whatsoever.

So it seems that, at this point in time, cyanogen's primary concern is sleep. this I understand as I don't get enough of it. I'm sure this will all be sorted out swiftly tomorrow, for now, 3.9.5 ftw. Stability is, of course, only our 5th concern, and somewhere in there are some donuts.
[G1 Android Development] dixxa:
I've took out the boot.img from the lastest release.

Booted in fastboot after a wipe + flash and typed.

fastboot boot boot.img.

it actually booted. but if I boot normally I get stuck at G1 screen. that's strange.
[G1 Android Development] innerspace:
so flash, reboot into recovery and then push vold from 3.9.5? will do.
[G1 Android Development] ThR1LL:
Has anyone else experienced when they are on the lock screen instead of the battery image it says Power is at: %d%%
[G1 Android Development] innerspace:
feature, not bug... see changelog page 1

unless you're actually seeing %d%% instead of lets say 67%
[G1 Android Development] 4treyu:
I didn't get stuck at G1 screen after flashing but I can confirm that "security and location --> wireless networks" is behaving weirdly. I don't get fc from it but it just doesn't stay on when I enable it. It only stays on if I enable GPS right after enabling wireless networks (in that order). I don't think that's supposed to be like that.
[G1 Android Development] Keyser.Soze:
Just tested and I have the same issue. Originally "Use Wireless Networks" was enabled on my phone, I unchecked and then re-checked it, got a Force Close.

KS
[G1 Android Development] cyanogen:
I would guess it's because you installed a theme not designed for this build.

Sleeping for real now :)
[G1 Android Development] innerspace:
@cyanogen -> vold to /system/bin is a nogo

reboot recovery, flash 3.9.6, adb push c:\vold /system/bin

reboot, device not recognized by windows... been about 3 minutes now, no activity, still g1 screen.
[G1 Android Development] ThR1LL:
Thank you so much for the awesom ROM! Actually I think this is because I flashed from the new JACxHERO rom. I'll just repartition my whole sd, wipe, and reflash and see if this fixes it. I'll edit my post if it does :D
[G1 Android Development] firetech:
I can confirm this. Running 3.9.6 now, although not very crash safe ;) (Good thing I have a 3.9.5 nandroid ready.)

I can confirm this as well.
[G1 Android Development] cidica:
Well only problem I'm having with this newest build is that Weatherbug no longer works without a force close. Was working fine on 3.9.5 but not anymore I'll see if I can get a logcat later tired now.
[G1 Android Development] beju69:
it doesn't work. it froze at operator splash screen.

I tryied twice, but the same effect. Where is problem?

i have hardspl and recovery 1.4. I'm flashing from full name, not from update.zip.

but keep going, every next rom is better :)
[G1 Android Development] dixxa:
This is something with the partitions.

even if I booted via fastboot I can't see my sdcard or my ext partition in system> storage.
[G1 Android Development] The Spirit:
Just tested and I have the same issue. Originally "Use Wireless Networks" was enabled on my phone, I unchecked and then re-checked it, got a Force Close.
[G1 Android Development] senab:
I've personally set mine to 128/384 with a powersave_bias of 0. I've then set up compcache at 12mb and a swappiness of 16 (i.e. it's only really used if really needed). Runs slightly quicker and *should* be less power hungry. :D
[G1 Android Development] fahadayaz:
I'm having the same problem.. and yes.. it does literally say "%d%%"

am not using a custom theme. just open home.

lol dont bother replying cyan.. get ur well earned rest and then come back and thrash those problems into submission.. :D
[G1 Android Development] userfriendlyme:
I see the same thing also but only when the phones not charging and you pull up the lock screen. i havent used any themes since 3.5.
[G1 Android Development] Jonno12345:
Here's a logcat regarding the wireless network force close

I/ActivityManager( 5262): Starting activity: Intent { action=android.intent.acti
on.MAIN comp={com.android.settings/com.android.settings.SecuritySettings} }
I/keystore( 6810): connecting...
I/keystore( 5243): new connection
I/keystore( 5243): closing connection
I/keystore( 6810): disconnecting...
I/keystore( 6810): connecting...
I/keystore( 5243): new connection
I/keystore( 5243): closing connection
I/keystore( 6810): disconnecting...
I/keystore( 6810): connecting...
I/keystore( 5243): new connection
I/keystore( 5243): closing connection
I/keystore( 6810): disconnecting...
D/LocationManager( 6810): Constructor: service = android.location.ILocationManag
er$Stub$Proxy@437219d8
I/ActivityManager( 5262): Displayed activity com.android.settings/.SecuritySetti
ngs: 593 ms
W/ResourceType( 6810): Failure getting entry for 0x7f080395 (t=7 e=917) in packa
ge 0: 0xffffffb5
D/AndroidRuntime( 6810): Shutting down VM
W/dalvikvm( 6810): threadid=3: thread exiting with uncaught exception (group=0x4
0019a68)
E/AndroidRuntime( 6810): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 6810): android.content.res.Resources$NotFoundException: String
resource ID #0x7f080395
E/AndroidRuntime( 6810): at android.content.res.Resources.getText(Resourc
es.java:155)
E/AndroidRuntime( 6810): at android.content.res.Resources.getString(Resou
rces.java:208)
E/AndroidRuntime( 6810): at com.android.settings.SecuritySettings.onPrefe
renceTreeClick(SecuritySettings.java:250)
E/AndroidRuntime( 6810): at android.preference.Preference.performClick(Pr
eference.java:820)
E/AndroidRuntime( 6810): at android.preference.PreferenceScreen.onItemCli
ck(PreferenceScreen.java:182)
E/AndroidRuntime( 6810): at android.widget.AdapterView.performItemClick(A
dapterView.java:283)
E/AndroidRuntime( 6810): at android.widget.ListView.performItemClick(List
View.java:3132)
E/AndroidRuntime( 6810): at android.widget.AbsListView$PerformClick.run(A
bsListView.java:1620)
E/AndroidRuntime( 6810): at android.os.Handler.handleCallback(Handler.jav
a:587)
E/AndroidRuntime( 6810): at android.os.Handler.dispatchMessage(Handler.ja
va:92)
E/AndroidRuntime( 6810): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 6810): at android.app.ActivityThread.main(ActivityThrea
d.java:3948)
E/AndroidRuntime( 6810): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 6810): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 6810): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:782)
E/AndroidRuntime( 6810): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:540)
E/AndroidRuntime( 6810): at dalvik.system.NativeStart.main(Native Method)

I/Process ( 5262): Sending signal. PID: 6810 SIG: 3
I/dalvikvm( 6810): threadid=7: reacting to signal 3
I/dalvikvm( 6810): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 5262): Added state dump to 1 crashes
[G1 Android Development] ThR1LL:
OK so in trying to fix my %d%% battery problem I nuked my phone in every way possible. Reformatted and partitioned my SD, unrooted, installed original spl, rooted again with haykuro's spl, and flashed this rom with a whole bunch of wipes in-between this steps and still have this problem when I'm experiencing low battery.
[G1 Android Development] Kwincy:
Yeah, I tried that, twice. Good thing I had a nandroid backup. I'll just wait until the next release, but man was 3.9.5 fast!
[G1 Android Development] xenio2000:
Same for me when I are on the lock screen instead of the battery image it says Power is at: %d%%, this show after the battery popup alert for 15% battery low, before that there was not any % showing

and Settings > Security & Location > Use Wireless Networks cause a FC

I am running 3.9.6 without any theme.
[G1 Android Development] userfriendlyme:
I dont think you needed to do all of that lol. i mean other people are reporting the same thing..theres obviously and issue on whats being displayed on the lock screen. It hasnt had any effect on the performace but im sure something he he will fix for the next release. Wow you guys let the man sleep some the rom works great so far despite that.
[G1 Android Development] mirox3m:
As I see, there was a quite big code dump into the Master branch 20 hours ago. All changes are marked "merge from Donut" and as usually we have to say thanks to JBQ.

http://android.git.kernel.org/

.....maybe we have to arrange a serious BEER party for Cyan..... :)
[G1 Android Development] andrew richardson:
Log of location F/C

I have the same problem with wireless locations, f/c on select.

I used the log collecter included in the build to try and help with diagnosis of the error. Hope it helps.
[G1 Android Development] ThR1LL:
Lol oh yeah and I erased my boot in fastboot. Anyway I'm perfectly fine with everything. It's such a minor flaw I could care less. I just did everything bc cyan said it might be bc of a theme problem but I wasn't running any themes so I wanted to make sure I flashed it coming from a completely clean G1
[G1 Android Development] Roger3778:
Cyanogen,

I have just installed 3.9.6 and this is the log when I try to enable bluetooth and wifi

Same with 3.9.1

Also if I

adb shell reboot I get

"Reboot returned" and no reboot occurs.

Everything works ok on the 8.1 version

Any ideas would be great

Bluetooth Log

D/BluetoothDeviceService( 3211): Bluetooth state 0 -> 1

E/bluedroid( 3211): open(/sys/class/rfkill/rfkill0/state) for write failed: Permission denied (13)

D/BluetoothDeviceService( 3211): Bluetooth state 1 -> 0

V/BluetoothEventRedirector( 3486): Received android.bluetooth.intent.action.BLTOOTH_STATE_CHAN GED

V/BluetoothEventRedirector( 3486): Received android.bluetooth.intent.action.BLTOOTH_STATE_CHAN GED

Wi Fi Attempt

D/SettingsWifiEnabler( 3486): Received wifi state changed from Disabled to Enabl

ing

E/WifiService( 3211): Failed to load Wi-Fi driver.

D/SettingsWifiEnabler( 3486): Received wifi state changed from Enabling to Unkno
[G1 Android Development] uwonsum:
It looks like ipv6 support was added to this release.
[G1 Android Development] jklong03:
Doc it hurts when I do this: Doc said "Then don't do that!"

Couldn't leave well enough alone! :p

Flashed 3.9.6 without wipe from 3.9.5 with no issues. Everything working fine so thought I would see about the "Use wireless" in Location service and got what everyone else was seeing, FC when I tried to re-enable it!

My % charged shows fine when on USB or charger, but then I am at 73% and I guess the funny display only occurs when in the "red zone"?

Apps all worked except paid app "CarDar" which uses wireless location setting. Interestingly, it caused FC even before I unchecked the "Use Wireless" option.
[G1 Android Development] daveid:
I would just like to put my 2c in on the whole lockscreen battery %. I am not quite sure I understood exactly where this was headed. If you only plan on removing the image, leaving the %, then disregard this. However, if the plan (which is how I read it) was to only have the % show when plugged in, I fail to see the benefit. The only time I don't care what my battery charge is, is when it is plugged in. If this could be made into a toggle, maybe with a warning that states "This option will decrease your battery life, and enabling it means you can not complain about poor battery life ever again!"? Just my opinion...
[G1 Android Development] cyanogen:
If I could punch you in the face across the internet, I would.
[G1 Android Development] JanetPanic:
Cyanogen I love you. I wanted to say the same thing but did not want to start anything.
[G1 Android Development] tricky76:
I have been running 3.9 for the past few hours. Made some calls and sent some SMS's with ChompSMS. No issues so far. Everything seems much faster. Great job!
[G1 Android Development] cyanogen:
Send me your APN and I'll add it to the list.

Both the checkin service and the setup wizard are closed source.
[G1 Android Development] temporizer:
I found that using a swap partition set at 20 swappiness runs smoother for me.
[G1 Android Development] simplyTravis:
Awesome build

I have been running this build with dxtop and it has worked great. At first it was slow and still has the occasional FREEZE moments but it is now fast, fast, fast.

I would like to use the new launcher but it is missing a few things crucial to me.

1. Easy 4 screen access (up, down, left, right gestures) I might reconsider this later on if I can press the home button to get to a main screen with the 5 screen method. Request 2 will have to be added first.

2. The ability to change icons through icon packs on the home screen for apps and folders. :eek:

3. A decent free ram monitoring widget. This has saved me multiple times. I've tried other that are not dxtop only and they aren't that great.
[G1 Android Development] sxfx:
Just flashed 3.9 with no wipe, and no Linux swap flawlessly.

Impressions roms runs quick ass hell, no force closures yet, started me off with three desktops so I switched back to 5 like I had before and it even recovered my icons automatically.

I did however loose a couple widgets that I had before, they completly disappeared off the phone, mainly like the wifi toggle, gps toggle and such but that's no a biggie at all.

Will keep on messing with everything and report in an hour or so. Also I fully charged my phone to 100%, so I will report back on battery life too.
[G1 Android Development] MarcusMaximus04@gmail.com:
Just flashed it, looks pretty good so far, although I'm seeing some graphical glitches when pulling down the app tray occasionally. It gets about 70% of the way down the screen and then flashes being all the way up again and then flashes back down. Oh and I just now found that it moved my middle screen to being on the far right... odd.
[G1 Android Development] ScottGood:
As far as I can tell this current version is like a diesel engine, that is the more it's run the smoother things move, I'm not having any issues, I'm kinda wishing I had something to fix, I'm getting bored with this, nothing is wrong, no lockups, no F/C's, no errors.

Will report back if I find anything unusual

Edit:

I think I may have spoke to soon, I just went into the gallery and I have folders for drawable, drawable-land and drawable-port

Does anybody else get this? if not I'm going to track down the location of the folders and remove them, while hoping nothing gets f-ed up
[G1 Android Development] :
Is there no way to get to the wizard?

Like hook up on a event or something when the wizard is called or closed?

I think there also must be a systemvar(or another way ie check if a dir is empty) so the system knows, if it should bring up the wizard. And this Var can be read on a bootscript, and depending on the value enable or disable the checkinservice.

Or am i wrong? ;)