yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] androidtoy09:
Looks like the nightlies need to update the superuser binary file. My superuser app keeps asking me to update the sf file after I flash each nightlie.
[G2 and Desire Z Android Development] autom8r:
Just flashed 213 over 211 after wiping dalvik cache, now, I have no Google account on my phone and I can't add one.. what the heck?
[G2 and Desire Z Android Development] G1ForFun:
Reflash the latest gapps...Simple.
[G2 and Desire Z Android Development] Fallen Spartan:
As above. Download latest gapps, reboot into recovery and flash ;)

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[G2 and Desire Z Android Development] ChronoReverse:
Also, don't install from ROM manager but straight in Clockwork Recovery instead to avoid this.
[G2 and Desire Z Android Development] .A.J.:
I don't normally use the stock alarm app but I just tested it and the snooze feature worked for me.

I've been using this one for a while.

https://market.android.com/details?id=com.adnfxmobile.wakevoice&feature=search_result

Not much to say except that it works. I usually don't use the voice recognition feature but I have tried it and it worked for me. I also use this

https://market.android.com/details?id=com.googamaphone.typeandspeak&feature=search_result

to make custom alarm messages.
[G2 and Desire Z Android Development] sino8r:
Hahahha! Very funny... the stock alarm will snooze once but it never comes back:confused:
[G2 and Desire Z Android Development] OriginalGabriel:
Happened to me too when flashing 211, not sure what's up.
[G2 and Desire Z Android Development] OriginalGabriel:
Not necessarily; I only use RM for downloads/backups, I flash updates via recovery as I have a few scripts I flash afterwards and I lost my accounts as well with 211
[G2 and Desire Z Android Development] ChronoReverse:
Really? Huh, maybe it's the recovery or some other factor?

I'm on 211 and I didn't lose my gapps when I flashed it using 4ext

Sent from my HTC Vision
[G2 and Desire Z Android Development] J-Hop2o6:
No deleted accounts here flashing the recent nightlies.. and no problems flashing with CWM v5.
[G2 and Desire Z Android Development] OriginalGabriel:
The apps were all there, it's just that all the Google accounts were missing.

What was your process? I wiped cache/dalvik, flashed 211, fixed permissions and flashed Pershoots kernel all via 4ext. To get the accounts back I had to reflash Gapps.
[G2 and Desire Z Android Development] ChronoReverse:
I wiped cache/dalvik, made a backup, flashed 211 and then flashed tiamat kernal all in 4ext.

Weird, doesn't seem like we did anything terribly different =(
[G2 and Desire Z Android Development] Fallen Spartan:
Tbh I always flash gapps after each Nightly

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[G2 and Desire Z Android Development] ptesmoke:
yea i always flash it, numerous times i didnt and id boot up and have no gapps. so now i always flash em.
[G2 and Desire Z Android Development] ihateusernames:
Same here. Been doing this for quite some time.
[G2 and Desire Z Android Development] autom8r:
I concur I flashed this the same as any other nightly....
[G2 and Desire Z Android Development] OriginalGabriel:
Are you using CWM or 4EXT? I'm going to flash tonights nightly without flashing gapps to see if it does it again and pull the recovery log.
[G2 and Desire Z Android Development] autom8r:
Anyone else not able to update apps through the Market now? I go to update, and it sits Loading the next screen view forever... ideas? I am going to reflash gapps and then see if that fixes it. Strange since this is a new flash of gapps already...
[G2 and Desire Z Android Development] nemiroG1:
Have the same issue with Market. Going to try to reflash gapps tonight.
[G2 and Desire Z Android Development] martonikaj:
hmm weird. Never lost GAPPS before.
[G2 and Desire Z Android Development] OriginalGabriel:
That was happening to me earlier today, I think the Market was updating to the latest version as I ended up with a Market newer than what was in gapps.
[G2 and Desire Z Android Development] DJMartini:
I'm having same problem with app updating too
[G2 and Desire Z Android Development] autom8r:
Yea, something funny is up, reflashing gapps was not the answer. I doubt people have encountered this before, I went back to 211 and it is still screwy, dang.
[G2 and Desire Z Android Development] OriginalGabriel:
Delete Market cache and data, launch the Market and associate your account and give it a few; there seems to be an update happening.
[G2 and Desire Z Android Development] J-Hop2o6:
I can't wait for CM8 (aka ICS)!

http://www.engadget.com/2011/09/28/ice-cream-sandwich-gets-a-two-minute-tour-courtesy-of-a-lucky-e/

its also using the 3.0.1 kernel.

and check this out: http://xdaforums.com/showthread.php?p=17962003#post17962003
[G2 and Desire Z Android Development] autom8r:
Worked like a charm! Thanks
[G2 and Desire Z Android Development] antinerd:
I just installed 213, and I can't seem to get my wifi running (ran great on 211)....has anyone else seen this, or did I just get a bad flash?
[G2 and Desire Z Android Development] lawalty:
My next phone will definitely have a front facing camera (ffc) .

Has anyone heard of any G3 Phone to come out?
[G2 and Desire Z Android Development] lawalty:
Im on the latest nightly and I have no wifi issues.
[G2 and Desire Z Android Development] DJMartini:
Found the problem to market with apps not being supported by device. Was reading around and I guess that Market checks DPI settings now, so if you're outside of 240 for LCD Density you might want to change it back do all your updates and than go back to 240. It worked for me.
[G2 and Desire Z Android Development] tronmech:
Anyone else notice a significant "silent" battery drain using wifi calling.

When I enable Wifi calling (because cell coverage in my house seriously blows), I've noticed that the battery consumption on the Nightly is significantly higher than when I leave it off.

On the rooted stock gingerbread ROM I was using before, turning on wifi calling seemed to have no impact on battery life. But wifi calling seems to suck my battery down nearly as fast as it did in stock froyo.

I'll compare yesterday and today. Yesterday, with wifi calling on (and wifi network preferred) I was at 60% battery left after 5-1/2 hours at work (where I actually get cell overage, btw) and the biggest battery user was "Cell Standby", which said that I had been without coverage for 90% of the day.

Today, with only 2 changes: 1) Wifi calling off before I went into the office; 2) set the power control widget to turn off 3G if wifi is enabled. I am at *92%* battery after the same amount of time.

Please note that my battery use with the stock G2 ROMs was somewhere in the middle of those 2 extremes leaving Wifi Calling on. I did use the RIL automatcher to get the right RIL for my .30 radio.
[G2 and Desire Z Android Development] DJMartini:
I've been having the same experience too.
[G2 and Desire Z Android Development] yogi2010:
I Google this every now and then myself! so far, no word... some have said that since this phone can run Gingerbread flawlessly, there was no need for an update. but I am kind of holding out myself, this is my favorite phone ever, and the development here is so awesome!
[G2 and Desire Z Android Development] OriginalGabriel:
Just to verify, are you stating that your Google accounts are missing as well when you flash a nightly when only wiping dalvik? If so, what recovery are you using?
[G2 and Desire Z Android Development] OriginalGabriel:
It seems the missing Google accounts bug (when flashing a nightly, only wiping dalvik, and not flashing gapps) is random. I've flashed the same nightly several times each with both 4ext and CWM and sometimes my accounts were there and sometimes they weren't.

While trying to sort out if it was a CWM bug or a 4ext bug the 4ext dev flashed with both CWM and 4ext and in both cases his Google accounts were missing but everything else was fine.
[G2 and Desire Z Android Development] ThaGeNeCySt:
nvm

Sent from CM7
[G2 and Desire Z Android Development] SteveRiley:
Where's the setting for that?
[G2 and Desire Z Android Development] ohcanada:
I saw an opened commit said "Use GCC visibility to reduce the size of libdvm by 11%". What is this mean? Looks like the dvm using less ram?
[G2 and Desire Z Android Development] sino8r:
When you create a new power widget... scroll all the way towards the bottom in options.

---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------

Looks like dalvik virtual memory will hog less ram. Yeah by 11% allegedly. Nice find! Hopefully, they will approve this commit soon!
[G2 and Desire Z Android Development] martonikaj:
Your data should automatically be turned to "2G only" when you turn on WiFi. That's how it is on mine anyways.
[G2 and Desire Z Android Development] csolanol:
What happened to the nightlies for vision?. No new one since 2011/09/28. Nightlies for all devices are built daily but not vision one...
[G2 and Desire Z Android Development] rkwhyte2:
Relax it's only been a couple of days I'm sure we will see a new nightly real soon. :)
[G2 and Desire Z Android Development] ltlgod:
what's the font of this ROM? (type, the font that I can see in whatsapp messenger)
[G2 and Desire Z Android Development] SomEngangVar:
Droid sans I think.
[G2 and Desire Z Android Development] churchmice:
I have figured out the problem, you need to give permission to shootme.

A quick fix for the lazy guy is :

chmod a+r /dev/graphics/fb0

You can wrote this in the init script.
[G2 and Desire Z Android Development] EdWRX:
What kind of trouble has it made you suffer?
[G2 and Desire Z Android Development] pawel_podgorski:
please read last 3 maybe 4 pages
[G2 and Desire Z Android Development] elracing21:
Well number 11 was smoother for me 2. I never had the screen wake issues. Even with screen on/off animation it was smooth as butter. I'm not even underclocked to the minimum. So I reverted back to 11 until 13 comes.

Sent from my gSpot2
[G2 and Desire Z Android Development] tvdang7:
i am on 10 right now and it is super laggy. it wasn't the first day i used it.

The auto tilt screen has about a 3 second delay until it tilts. even occasionally the screen unlock lags. I am left wondering how everyone else is running it so smooth.

About to flash #12

EDIT

Same problems with #12.
[G2 and Desire Z Android Development] pawel_podgorski:
will come today ? next fiew hours ?? this buildbot make me confused
[G2 and Desire Z Android Development] pawel_podgorski:
#10 is realy slow, #12 is buggy best on for me and for now was 11

am waiting for 13... should shows up for next hour or two
[G2 and Desire Z Android Development] Hot_Hands:
#12 works fine for me. They've all been fine. There have been no commits merged today according to review.cyanogenmod.com so I wouldn't expect anything different to be in #13. The buildbot builds every night regardless if there have been changes or not.
[G2 and Desire Z Android Development] olearyp:
(I feel like I'm repeating myself here.) Builds start at midnight UTC (0000Z); according to your sidebar you're in Chicago, so that's 6 PM this time of year. There's a lot of builds to get through, and vision is near the end, so it takes a few hours to get there. I've seen them showing up between 10 PM and 11:30 PM CST, depending on whether both buildslaves are connected, but basically It's Done When It's Done.

As it happens, that will be soon. But since cyanogen's off snowboarding in Breckenridge, nothing's been committed since the last build, so #13 == #12, barring any interesting changes in upstream repositories.
[G2 and Desire Z Android Development] pawel_podgorski:
finally somebody give me some idea how the buildbot thing is working

THX

Nihil novi in that case so :(
[G2 and Desire Z Android Development] luis86dr:
13 out..

[G2/HTC Vision]
[G2 and Desire Z Android Development] mbush78:
Up and running 13 w/o issue so far
[G2 and Desire Z Android Development] Vandam500:
Nice to know feedback from 12 minutes of use...
[G2 and Desire Z Android Development] rmcsc:
It's kinda freaky how we know where our favorite modders are. :eek:

Downloading #13, since I didn't do anything to it since 10. Or was it 11?
[G2 and Desire Z Android Development] olearyp:
LOL, yeah, well, that's why I'm pretty much a read-only user on Twitter. :)
[G2 and Desire Z Android Development] tvdang7:
updated to 13 same thing. is there a way to calibrate the g-sensor? I dont know what else that can be causing this. I did fix permissions for the hell of it too.
[G2 and Desire Z Android Development] pawel_podgorski:
bluetooth and FM

I wonder if we can use bluetooth as fm receiver why not us as transmitter ? bluetooth can send and receive so for example it will be very good for older cars without bluetooth radio as speaker phone. Let's say i step in my truck, press button on phone and i have connected via fm to my stereo.

what U think it will be possible to program something like that ?
[G2 and Desire Z Android Development] pawel_podgorski:
#13 = #12

READ FORUM 5 maybe 6 posts UP
[G2 and Desire Z Android Development] gravis86:
It doesn't use bluetooth for the FM receiver...

The FM transceiver is on the same chip as bluetooth and since HTC won't share how to run on only the FM transceiver, we have to power up the whole chip to get it to work.

However the FM chip in our phone is a transceiver so it technically should be capable of transmitting FM signal but that's a lot of work to figure it out and there are many more important things that the devs are working on.
[G2 and Desire Z Android Development] illithid:
Just wondering why the kernel version for this is 2.6.32.28 instead of 2.6.35?
[G2 and Desire Z Android Development] primatage:
Huge chunks have been back-ported from the .35 source, it's just taking them a lot longer to get the rest of it sorted.
[G2 and Desire Z Android Development] ltlgod:
thank ya! :)
[G2 and Desire Z Android Development] Nospin:
I was hoping the CM team would get a little break between releases, but they are running right up on the Ice Cream Sandwich announcement.
[G2 and Desire Z Android Development] DJMartini:
Where you reading this at?
[G2 and Desire Z Android Development] hamish909:
I'm on 213 nightly atm, but I have noticed I had this same problem in earlier builds like even back to like 140 etc.

When I press End call on the screen, there is always a long delay before it responds meaning calls can't hang up when I want it to. This happens if only after the screen has blanked at least once due to proximity sensor. If the screen has not blanked since I called, I press End call and it responds straight away.

What's up?
[G2 and Desire Z Android Development] SteveRiley:
Ah, thanks. I was looking in the CyanogenMod settings for the notification power widget. That one doesn't have as many configuration options as the power widget you can place on the screen.
[G2 and Desire Z Android Development] Nospin:
Well the Samsung event is October 11th, where they are Co-announcing something with google about the future of Android, right smack dab in the middle of the ICS rumored release. Smells like Nexus Prime to me.
[G2 and Desire Z Android Development] sino8r:
Try call delay patch from market. It fixes it for the most part. A full wipe fixes it too though...
[G2 and Desire Z Android Development] androidtoy09:
Please if possible, someone add an option for switching from solid black to transparent status bar :) in CM7 Nightlies.

I've been trying to create a transparent status bar (not pulldown notification) but nothign worked.
[G2 and Desire Z Android Development] lawalty:
Hey guys. Has anyone heard if we're able to flash a new nightly tonight?

I really appreciate all the hard work the CM7 team Vision been doing. :)
[G2 and Desire Z Android Development] damngood98:
radio issue?

hi guys & gals, made a post a few days ago about my wife's g2 having issues dropping calls frequently. doesn't appear to be a common issue. originally i had left the .15 radio on her phone from doing the downgrade, then i changed it to the .30 radio. i suppose i'll try the .26 one now but i can't seem to get rid of this off her phone.

has anyone else been running into this? can anyone point me in another direction to squash this? :confused:

appreciate it everyone, thanks

Edit: suppose the latest nightly won't hurt either. can't wait for the sensation to have nightlies. kinda jealous....
[G2 and Desire Z Android Development] nemiroG1:
I am, and have been having the same exact issue. I have tried all of the radios. So far, .17 and .26 work the best, but even then I am always losing signal. My Wife's 'ancient' Motorola V3 will sometimes have 2-3 bars, when my G2 has none. Very frustrating!
[G2 and Desire Z Android Development] OriginalGabriel:
216 is up so, I'd say that's a yess :P
[G2 and Desire Z Android Development] gravis86:
Keyan Mobli is the maintainer for the Sensation and has been posting selfkangs (basically his own homemade nightlies) for the Sensation for a while. Check him out on Google Plus to get them.

EDIT:

Or go here http://xdaforums.com/showthread.php?p=17470111
[G2 and Desire Z Android Development] djfoo000:
On nightly #216. Entering video recording mode hangs the camera app, and stays hung until I manually FC it. Repeats itself whenever entering video recording mode.

ShootMe still refuses to work.

EDIT: Silly me. Video recording works after a reboot. Liking the new camera background and how it turns transparent when in video mode.

EDIT2: Hrmm... Apparently if you record a video, and proceed to delete that video, the next time you try switch to video recording mode, the camera hangs and then FCs.

LOL @ me reporting this. Nightlies, yeah. Expect bugs.
[G2 and Desire Z Android Development] mralexsays:
NemiroG1,

I was in the very same situation as you, except I had problems with GPS on all radios except .26, so I ran .26 for a long time. About 5 days ago, I found the thread:

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

(and, for reference, the efs wipe thread)

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

and I am finally able to run the .03 radio and it is absolutely wonderful! The thread I mentioned contains .zip files that you must flash immediately after flashing a nightly. The other key to successfully changing radios to do flash the efs wipe (also linked to in that thread) before flashing the PC10IMG.zip for your radio. Here is what worked for me:

1. Download the .03 fix zip from the above thread, the .03 PC10IMG.zip from the radio thread, the efswipe zip and the desired nightly.

2. Reboot into recovery. (I now use 4ext recovery since it has an option to boot into bootloader from recovery.)

3. Flash the efswipe zip.

4. Wipe cache and dalvik cache.

5. Flash the nightly, then select 'reboot into bootloader' from the power menu in 4ext.

6. Let the bootloader install the .03 radio, then reboot.

7. Once rebooted, open maps. It'll take a long time to get a GPS fix the first time (like 5 minutes) then it'll be fast every time after that.

8. Remember to flash the .03 fix zip after you flash a new nightly.

That's what worked for me. I know you are having signal issues, not GPS, but I suspect that the efswipe is what you really need to fix your particular issue. Some people say to efswipe before installing a new PC10IMG.zip, some say after, and some say do both. It doesn't make sense to me to efswipe after flashing the PC10IMG.zip because the new radio might install something to the efs partitions, and running efswipe only before flashing the PC10IMG.zip worked great for me. Hope this helps.
[G2 and Desire Z Android Development] PooN_HeaD:
would wiping the dalvik cache do anything wrong to the rom? dont plan on updating soon, but dont wanna break it either.

HTC Vision (G2)

Android 2.3.5

CM7 Nightly #213
[G2 and Desire Z Android Development] mralexsays:
Wiping dalvik cache and 'regular cache' hurts nothing. In fact, it is recommended to do so every time you flash a ROM.
[G2 and Desire Z Android Development] damngood98:
.03 radio? what is WWE? i'm a tmobile usa user if that makes a difference.

and by the way, i was using the efs wipe too. thanks for pointing that out though
[G2 and Desire Z Android Development] mralexsays:
If you are responding to my post a few posts back, by .03 radio I mean "26.10.04.03". WWE means "World Wide Edition", so I assume that means it'd work internationally if you travel a lot and I'm on t-mobile usa also and the 26.10.04.03 radio is working great for me (in Atlanta.)
[G2 and Desire Z Android Development] PooN_HeaD:
what if i do it in the middle of a rom?

HTC Vision (G2)

Android 2.3.5

CM7 Nightly #213
[G2 and Desire Z Android Development] mralexsays:
You can wipe the dalvik cache and regular cache at any time. The dalvik cache will have to rebuild once it is wiped, so the first boot after a dalvik wipe will take longer than normal. The regular cache will have to rebuild also after it is wiped, so applications that use the regular cache will take longer the first time they are run since they have to reload their data in the cache.
[G2 and Desire Z Android Development] damngood98:
Were you ever having your calls dropped before? Just curious, worst case scenario I flash.03, it doesn't work, & I have to try another one. Does anyone else think it could be something besides the radio?. Her phone was fully wiped as its barely been a week since I rooted it.
[G2 and Desire Z Android Development] mralexsays:
The only time I had dropped calls was on the 12.57.60.25_26.10.04.12 radio - that radio was really, really bad for me. The 12.56.60.25_26.10.04.03 radio has been great the past 5 days or so which includes stationary use inside house and office building as well as use in the car (through bluetooth hands-free of course.)
[G2 and Desire Z Android Development] gtmaster303:
Will CM start porting ICS as soon as they can, or will they polish out GB first before moving on?

Just wondering... Never been on android in the middle of a major release.

Excited all the same :D
[G2 and Desire Z Android Development] tsubus:
If I remember correctly, when they went from froyo to gingerbread, they made a final release for cm6 and then they started rolling out cm7 nightlies and stopped developing for cm6.
[G2 and Desire Z Android Development] steviewevie:
I am a bit suprised we haven't had at least an RC2 yet for 7.1. At this rate we won't have a stable 7.1 before ICS is released. Of course the problems at kernel.org haven't helped.

Not criticising in the least here, I love the work of the CM team. Just an observation.
[G2 and Desire Z Android Development] aegentirony:
This ^..... I think we should expect 7.1 final instead of rc2 at this time....The ics source wouldnt be released until the 11th earliest correct? Either way...CM and team you guys rock and make my g2 top most brand new phones out there still to this day...Kudos! :D
[G2 and Desire Z Android Development] gtmaster303:
has anyone found a way to remove the extra languages? I've looked everywhere I can't find an answer
[G2 and Desire Z Android Development] hispeedworm:
CM 7.1 is coming in a day or 2..... this was told in the cyanogenmod event at android BBQ.....
[G2 and Desire Z Android Development] steviewevie:
Excellent ! Thanks for the news :)
[G2 and Desire Z Android Development] Fallen Spartan:
Interesting, must ask the mods who are at the event to confirm this

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[G2 and Desire Z Android Development] Nospin:
Confirmed via Android central, they are attending the event.
[G2 and Desire Z Android Development] OriginalGabriel:
Yeah, bugs are to be expected but you're correct in reporting nightly bugs here (and not in the bug tracker which is for RCs and stable); those that flash nightlies are "used" to test new features and find bugs.

I'll see if I can reproduce your video bug once I wake up a bit more.