yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] geoffcorey:
The only source requires by anyone other than Google is kernel source. However, some phone manufacturers don't do stupid deviations from aosp code in the radio ans GPS like Samsung chooses to do.

You will never get full source from anyone other than Google.
[Vibrant Android Development] Phateless:
I would have to agree with this.
[Vibrant Android Development] Phateless:
This too.
[Vibrant Android Development] }{Alienz}{:
dumdidum just tweeted "looks like #gps is fixed now."

Do you think that is for the Vibrant CM7?
[Vibrant Android Development] inrelief:
Looks like that was a joke, dude.

We was replying to this from KMobs http://twitpic.com/5lmnpm
[Vibrant Android Development] masr1979:
That's obvious, I was just curious about the mention of hardware as adyscorpius stated. The way atinm posted it's like our phones are not capable of doing it due to hardware limitations. Not that's it's a big deal... I take about 5 pics a month at most, just looking for clarification.
[Vibrant Android Development] Droidicus:


As would I.
[Vibrant Android Development] Droidicus:
And who can forget this oldie but goodie?!?

http://www.droiddog.com/android-blo...or-massive-gingerbread-rollout/#dsq-form-area

Ah, source. The bell tolls for thee.

Atinm - Samsung seems to like you, or at least like you developing the best software for their phones for free. What do they tell you of source code gingerbread for the vibrant?
[Vibrant Android Development] SuperJMN:
External SD Card not mounting

Under Settings->Storage I cannot see the ext sd card.

Additional storage: /mnt/emmc. None available.

I insert/remove the sd card physically, but no action, events are shown :S

Is that normal?
[Vibrant Android Development] geoffcorey:
are you running with gb bootloaders?

if so, flash back to froyo bootloaders.
[Vibrant Android Development] SuperJMN:
Yes, I flashed Vibrant_GB.tar.md5 with Odin.

Well, I tried to flash this Froyo bootloader vibrant_froyo.tar.md5

... but doing so, my device boots into Recovery once and again. I had to put it in Download mode again and reflash the GB bootloader for it to boot!
[Vibrant Android Development] geoffcorey:
when using the gb bootloaders, there is something weird that makes it so you can't use the external sdcard on cm7.

also, AFAIK, teamhacksung only support froyo bootloaders.
[Vibrant Android Development] Argusi:
Ruh Roh... Has anyone tried a Nandroid restore from build 45? CMR v4.0.0.5 in particular? It passes MD5 gets to restore system, sits for a second then goes back to recovery trashing the part. I've tried 3 different backups and they all fail the same way. Also, tried to restore only data and same issue. And, even Odined back to JFD and came back to 45 just to be sure.

Last I read, there was an issue a couple weeks ago which was fixed. Anyone get a successful restore on CMR v4.0.0.5?
[Vibrant Android Development] Phateless:
My external sdcard works fine and I restored a nandroid when I swapped to a new warranty phone.

Dunno what's up with you guys, lol.
[Vibrant Android Development] Argusi:
My sdcard is fine. I can see the backups in recovery, therefore, my sdcard is fine (yes, I repeated myself). I just finished extracting the .img's now to manually put some newer stuff back that TB didn't get last night.

Like I said and to add, when I do the restore from recovery, it passes MD5, restores the boot.img and then I think recovery. It then starts system and fails, as does a custom restore of data only, on 3 separate backups. The .img files seem fine, I just extracted data and datadata and am going to push some newer stuff back out to the phone after TB finishes. Sorry, not an sd issue... I'm running the Froyo SBL, so I don't have the GB SBL issue that some are seeing. Besides, that affects the external SD, all my files are on the internal sd.

Make sense? I'll get my data back, it's just taking some work. I just don't think it's my phone in particular since I went back to stock and did a fresh install of nightly 45. I just want to make sure it's not just me because some other people may not know how to extract the .img files and get their data back and besides, it's a PITA. :)
[Vibrant Android Development] geoffcorey:
hey atinm, there is a problem with the extract-files.sh script when getting the latest code from github for vibrantmtd. it doesn't grab gps.aries.so and so when you build, it errors out on not finding it.

With this, i went into the #cmsgs channel to get some help, and someone diff'd it against the galaxysmtd, and these were the only difference found:

adb pull /system/etc/gps.conf ../../../vendor/$MANUFACTURER/$DEVICE/proprietary
adb pull /system/vendor/bin/gpsd ../../../vendor/$MANUFACTURER/$DEVICE/proprietary
adb pull /system/vendor/etc/gps.xml ../../../vendor/$MANUFACTURER/$DEVICE/proprietary
adb pull /system/vendor/lib/hw/gps.aries.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary

So i manually pulled the gps.aries.so and am currently building. will update if i run into any more errors about missing proprietary .so files.
[Vibrant Android Development] adyscorpius:
If you flas bootloaders when on MTD like on CM7, you would end up in recovery... On solution is to flaah back yo JFD and then reinstall CM7...

Do no flash bootloaders after flashing and AOSP ROMs based on MTD partitioning...
[Vibrant Android Development] ArcaneMethods:
NOOB ALERT!!

Can you please explain to a (relative) noob how to do that part of it?

Thanks
[Vibrant Android Development] krazie1:
Everything you need is here. Just follow the instructions carefully.

http://xdaforums.com/showpost.php?p=14588896&postcount=1
[Vibrant Android Development] SuperJMN:
Well... so the extenal SD Card is probably not mounting under Gingerbread because I'm using a GB bootloader. But the only way to go back is going back to JFD and reinstall CM7 from there. Am I right?

Thanks :)
[Vibrant Android Development] krazie1:
Change your bootloader back to the froyo one, then odin back to Stock JFD. After that install the latest nightly......you know the rest.
[Vibrant Android Development] FATEOWNZYOU:
I wanted to save battery. So under wireless and network settings I switched to "2g only"..and now its stuck there. Can't get back into 3g.. tried on build 44-45-46..
[Vibrant Android Development] nedlog:
Just flashed to #46; and everything seems to be fine, checking my apps now. Really like the screenshots feature from the night before...CM7 just keeps getting better and better..Thanks. :o
[Vibrant Android Development] cwalker29:
Go into mobile network. Uncheck data. Uncheck 2g only. Turn data back on. Problem solved
[Vibrant Android Development] cwalker29:
Just wondering, have anybody got chainfire 3d working good with cm7?

never mind got it to work!!!
[Vibrant Android Development] Poser:
atinm merged it this morning :)
[Vibrant Android Development] xriderx66:
I'm still on #39, I think its time for me to move on because I want the screenshot feature.

GODDDDDDDDDDDd i don twanna leave 39's battery life.
[Vibrant Android Development] FATEOWNZYOU:
Didn't work
[Vibrant Android Development] Phateless:
Is your wifi on?
[Vibrant Android Development] apollo15rover:
Try that again but between each step wait 10 seconds, lock & unlock screen, and wait another 10 seconds before proceeding to the next step.

So in settings..

Disable data...

10 seconds

Lock&Unlock

10 seconds

Uncheck 2g

10 seconds

Lock&Unlock

10seconds

Lock&Unlock

Hopefully you will now be running..
[Vibrant Android Development] Jasonhunterx:
Works flawless
[Vibrant Android Development] andrewxu:
When I upgrade nightlies do I lose my old apps and data from previous nightly? And also should I check any of the boxes when it says clear davlik cache etc? Thanks I'm new to this! But its all so awesome I love my phone now!!!
[Vibrant Android Development] geoffcorey:
You will lose you apps if you tell it to wipe data. It might be a good thing though if you wipe dalvik, just to eliminate a source of bugs that you might experience.
[Vibrant Android Development] andrewxu:
So wipe davlik but not data?
[Vibrant Android Development] xriderx66:
No it does not.

Do this-

Download ROM ( i do it manually , i don't have prem. Rom Manager)

Go to CWR

wipe cache partition

Advanced > Wipe dalvik cache

flash rom

it will reboot

and let it load.

Even after the actual screen comes on- leave it there for 5 minutes - 10 minutes

reboot

I always do that to ensure something isn't wrong.

a reboot usually fixes any temp. problems
[Vibrant Android Development] quadratic:
Anyone know what this is all about?
[Vibrant Android Development] Phateless:
I REALLY hope that means what I think it might.
[Vibrant Android Development] malevolent000:
More battery drain? Jk......jk...
[Vibrant Android Development] geoffcorey:
it literally is nothing more than fixing a bug in the extract-files.sh script that pulls proprietary .so files.

I went through the process of setting everything up yesterday to build CM7 for vibrantmtd from source, and the script didn't pull gps.aries.so, so the build failed and i notified atinm about it (my post is a page or two back explaining the bug).

my post about the bug in the script:
[Vibrant Android Development] }{Alienz}{:
I hope it doesn't mean more battery drain. :/
[Vibrant Android Development] geoffcorey:
It is nothing more than a script overlook. it's nothing new guys.
[Vibrant Android Development] Poser:
which win 7 theme is that... pretty slick
[Vibrant Android Development] andrewxu:
Thanks a dozen, how long should it take to flash? It says it worked but only took like 1 min to flash the new nightly, when usually it takes 10 min to flash a rom.! Thanks again
[Vibrant Android Development] Phateless:
Ah yes, I remember that. I got all hot and bothered thinking we might have GPS. :(
[Vibrant Android Development] KarlHegbloom:
I just built it also... and my build has working GPS!

I had to add the gps.aries.so, and then modify the /init.aries.rc as described in the Gingerbread GPS thread. It works now.
[Vibrant Android Development] cashyftw:
Wait what?!

Sent from my GT-I9000
[Vibrant Android Development] archie53:
Exactly. What?
[Vibrant Android Development] bdubs4200:
Yeah, WHAAAT?
[Vibrant Android Development] Nabeel10:
Okay, so WHAAAT???????!?!?!?!?!!?
[Vibrant Android Development] movieaddict:
troll??????????

or hes serious?
[Vibrant Android Development] }{Alienz}{:
troll
[Vibrant Android Development] nedlog:
Noticed gps.aries.so in the change log, is this for real? I mean is this a real fix?
[Vibrant Android Development] geoffcorey:
No, the extract-files.sh script that copies over proprietary blobs was missing on of the .so files, (gps.aries.so) which is required to build CM7 for the vibrant from source. I notified atinm about it, and he fixed the script. If you check back to tgw last page, you'll see me quoting myself from two more pages back about it.

You guys don't like to read do you?
[Vibrant Android Development] Phateless:
Lol, get used to it. The GPS thing was amusing to read though.
[Vibrant Android Development] nedlog:
Actually reading the thread is one of my favorite things about my phone, the answers sometimes get convoluted. Your answer here helped clarify. Since it appears you don't like to answer questions that already have been answered please ignore my questions in the future, don't want to waste time.
[Vibrant Android Development] Poser:
Wow!!!!

Can you use it to locate what bridge you live under?

I kid, I kid... (sorta)
[Vibrant Android Development] xriderx66:
I'm gonna slap you with my **** freaking troll
[Vibrant Android Development] Phateless:
Lol...
[Vibrant Android Development] geoffcorey:
The reading thing wasn't necessarily aimed at you, it was aimed at everyone who kept on saying about how gps might have been fixed after I had posted 3(?) times about that gps thing and yet people kept saying that gps might be working now.
[Vibrant Android Development] geoffcorey:
Edit: not sure what happened, but I double posted somehow.
[Vibrant Android Development] nedlog:
Understood just don't want to be one of "those" individuals. Happy to have CM7 my phone rocks:)
[Vibrant Android Development] gamikzone:
im not sure why but this problem is reoccuring with me sometimes on cm7 my external sd can be read but sometimes it cant im not sure why i tried to odin to jfd and followed the install instructions but when i look in mnt/emmc or emmc it shows empty anyone know how to solve this problem?
[Vibrant Android Development] Phateless:
I just look under /emmc and I never have a problem reading my sdcard.
[Vibrant Android Development] cwalker29:
+1
[Vibrant Android Development] geoffcorey:
Did you flash the gb bootloaders?

If so, flash back to the froyo bootloaders.
[Vibrant Android Development] jaysix79:
Been using cm7 for two week from build 35 to 40. I been getting random reboot and it goes in boot loop any recomendation. Been getting reboot it ever build 35 to 40
[Vibrant Android Development] shreddintyres:
I have had the emmc dissappear on me before, but i used an app called SD rescan and all was well. If you are still having issues you may want to try wiping the dalvic and cache partitions but not the data partition from recovery.
[Vibrant Android Development] ArcaneMethods:
Does this Vibrant version include Anitta Lankila's DSP Manager (dspmanager.apk running with his libaudioflinger.so). If so, does it work?

Ref:

http://bel.fi/~alankila/android-dsp/

https://github.com/CyanogenMod/android_packages_apps_DSPManager

http://xdaforums.com/showthread.php?t=783737
[Vibrant Android Development] numberoneoppa:
When you flash an update, flash it twice before rebooting the phone. Srsly.

On another note, I am very very happy with 46 thus far. :) Loving the screenshot capabilities. For some reason I can't upload said screenshots using the xda app, though. Ideas?

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] xeku:
has anyone tried flashing the 2.3 wifi calling app and had any luck with it and the latest nightly build?
[Vibrant Android Development] geoffcorey:
That only works on a Samsung rom, specifically jvp.
[Vibrant Android Development] krazie1:
Nightly #47 is UP and Posted!

EDIT: I posted a ? Mark instead of the ! Mark.
[Vibrant Android Development] movieaddict:
47 is up now!!!

someone try it and let me know...ty
[Vibrant Android Development] Duntkno:
is there an option within to make it so you can stop sounding like your talking from far away? Ive done about 3 fresh from odin installs, and I keep coming up with the same problem.

From what I've been reading its not reproducible, anyone have any idea what it could be? thanks
[Vibrant Android Development] adyscorpius:
Thats a known bug... Mute/unmute on the incoming call... Outgoing ones are fine...
[Vibrant Android Development] numberoneoppa:
Don't see anything in 47 that would convince me to upgrade right now from 46. Anybody concur or disagree?
[Vibrant Android Development] Romanbb:
Can someone please test this out and tell me if the mute/unmute bug is still present

might need to reboot after pushing it
[Vibrant Android Development] numberoneoppa:
Would if i was in the US. Don't want to bother anybody this time of night in korea, though.

SOMEBODY TEST THIS MAN'S APK!
[Vibrant Android Development] Romanbb:
that's it, i'm quitting if someone doesn't test this one in 5 minutes
[Vibrant Android Development] Phateless:
I've never had this bug in the first place.
[Vibrant Android Development] ewidtfeldt:
Tried the apk birgir posted. First call from my brother whom I always have to mute shows a positive result. I sounded fine. Will edit my post later with more results. Off to work.

Where is this apk from any way?
[Vibrant Android Development] shreddintyres:
gonna test shortly, tho i am not on the most current build, on build 39.
[Vibrant Android Development] Romanbb:
Me, lol
[Vibrant Android Development] shreddintyres:
Results in fc then after reboot no service on build 39, likely due to the fact that its a older build
[Vibrant Android Development] ewidtfeldt:
Sorry dumb question...

Thanks a lot for your contribution! Like I said so far so good for me but I can't really test at work until later in the afternoon.
[Vibrant Android Development] ewidtfeldt:
I did it like this:

1. use root explorer to copy to /system/app overwrite the original (fc starts right away)

2. Reboot into recovery with three finger method

3. Go to advanced and fix permissions then reboot

4. Bask in the glow of a possible solution!
[Vibrant Android Development] Romanbb:
The second one I posted may have more potential for an fc, not sure if you used that one or not
[Vibrant Android Development] shreddintyres:
I didnt think of fixing permissions, ill give that a shot, out of curiousity what build are you on?
[Vibrant Android Development] ewidtfeldt:
I used the first. Wasn't aware that they were different
[Vibrant Android Development] ewidtfeldt:
45
[Vibrant Android Development] apollo15rover:
Wipe data/factory reset.
[Vibrant Android Development] tbrar:
I am currently on build #40. Tested the apk but got no signal after reboot. Had to reinstall the build as due to some unknown reason my backup of phone.apk was unable to restore the signal. Thanks for the try. If you think that my old build could be a problem I can update to the latest build.
[Vibrant Android Development] Romanbb:
Permissions need to be fixed after using the new one. I'll do more experimenting later today.
[Vibrant Android Development] shreddintyres:
@Roman/Birg, using the second one you posted after fixing permissions all seems well, will be able to test more through out the day but so far so good on test 39.

So for those of you like me using nightly 39 for battery life this should work just reboot into recovery and fix persmissions like ewidtfeldt said.

Thank you Birg/Roman
[Vibrant Android Development] numberoneoppa:
FYI the battery on 46 is just as good for me as it was on 39.
[Vibrant Android Development] s15274n:
Roman, I made the permissions identical to the phone.apk in CM7... then rebooted... tested one incoming and one outgoing... the person said I sounded perfect.

Thank you man.

Permissions (X being checks)

X.X.O

X.O.O

X.O.O
[Vibrant Android Development] uurrnn:
My battery has been absolutely atrocious recently. I'm on 46, I calibrated using the battery calibration app, and I even UCd to 800mhz through cm settings to help.

I have pretty heavy data usage throughout the work day, frequently reading news, checking forums, etc. My battery will drop 25% in 1-2 hours sometimes.

I'm going to try using 2g only and see if that helps.

I also have two extra batteries at home, so tonight I'm going to switch to one of them and test more.
[Vibrant Android Development] shaiu22:
I can verify after a call of 2 minutes that the mute/unmute bug is gone!! Thank you!!

Are you going to give the CM7 team the solution in order to put it in the next nightly builds?
[Vibrant Android Development] andrewxu:
Which battery is better, latest or 39 and why?
[Vibrant Android Development] Mannymal:
Lets not get ahead of ourselves, more people need to test the mute/unmute thing, repeatedly, before we can call it fixed.
[Vibrant Android Development] gatorbob:
Have not been able to try yet personally, but wanted to say THANKS for working on this bug!
[Vibrant Android Development] Romanbb:
Fixed or not it's only a temporary solution. More of a hack than a solution. In the second one posted, I literally have it toggle mute on an incoming call.

As I said, more of a hack.
[Vibrant Android Development] bigtom624:
I used the first one and got a f/c as soon as I pushed it. I rebooted and fixed permissions and called my phone from my work phone and it worked for me. I always have to mute/unmute on every call, so this is great that it worked. Thanks Birg.
[Vibrant Android Development] shaiu22:
First call after installation was good. No mute/unmute bug. But after that each call got the bug again. Anyone else got this too?
[Vibrant Android Development] movieaddict:
so its like its resetting itself after each phone call? so it works once and then resets itself? Ty for ur hard work on this!
[Vibrant Android Development] jaysix79:
Imma give this one a shot before I do a factory wipe. I hope flashing twice will solve my problem cause this is my gf's phone and she hare's it but she wont go back to stock
[Vibrant Android Development] bigtom624:
It worked for me on 2 calls so far. No problems yet.
[Vibrant Android Development] apollo15rover:
I just did the wipe going to 47. I try to do so every 4-5 flashes .. if I go too long I get FCs..

Between Google Accounts and Titanium BU Pro the reset/wipe is reduced to a minor annoyance now..
[Vibrant Android Development] diaa08:
deleted post
[Vibrant Android Development] AgentFour20:
Thanks for the phone. Apk
[Vibrant Android Development] adyscorpius:
Did you test it well? And the first one or the second..??
[Vibrant Android Development] AgentFour20:
Just tested works great for me. Caller said I was crystal clear.
[Vibrant Android Development] brnagndan:
It's been like since I started using CM7 but I always have to go into recovery and manually flash. Pushing the button in Rom manager to have it install never works and I also get an error that it can't read sd-ext. Any ideas that don't start and end with "Odin back to stock"?
[Vibrant Android Development] gatorbob:
Do you have Rom Manager set to the 3.x version for the vibrant? When you install CM7 initially you set it to the 2.x version
[Vibrant Android Development] brnagndan:
Ah, I didn't. Hopefully the next nightly works fine. Thanks man.
[Vibrant Android Development] snapemiken:
Worked once the 1st time. Bugs still there on 2nd to 7th call. Running RC1

Really appreciate the time and work :)
[Vibrant Android Development] Orwell83:
Birgs hack work for my last two incoming calls!
[Vibrant Android Development] nedlog:
Running #47 and pushed/tested this fix, got one call and sounded clear. Rock and roll...thanks for your efforts.:D
[Vibrant Android Development] granduke:
phone fix appears to work on #46. thanks
[Vibrant Android Development] cashyftw:
Phone fix works on miui also!
[Vibrant Android Development] krazie1:
I used the second phone.apk birgertime posted on Nightly #46 and all calls are clear and perfect. Hopefully this hack can be implemented into CM7.
[Vibrant Android Development] moonfire711:
If I'm gonna download the latest nightly and implement this mute/unmute fix (hack), is there a way to just put it in the rom before I flash it? Unzip and rezip? If so, what settings should I use in 7zip to zip it back up? Thanks. I'm just more of a fool than a noob.:eek:

Edit: Just did a drag and drop into 7zip in the correct folder. We'll see if that is all it took after I get done flashing.
[Vibrant Android Development] hitman818:
Can anyone comment if the wifi disconnecting and reconnecting issue is fixed? For example when I download a file or watch youtube its unsuccessful or has an error. Then the wifi sign turns grey then back to green.
[Vibrant Android Development] adyscorpius:
Didn't it cause the apk to crash or change in look from the Stock MIUI look ???
[Vibrant Android Development] cashyftw:
Yep it did, but I rebooted into recovery, fixed permissions, and everything was well.
[Vibrant Android Development] adyscorpius:
And what about the theme and look of Phone.apk ?? Its stock Cyanogen now ??
[Vibrant Android Development] xriderx66:
WHATS GOING ON WITH THE PHONE.APK1!!+!$#@%

is it going to be included in the new nightly?
[Vibrant Android Development] masr1979:
I don't think it should. Works fine for me, but there's some people that don't have the problem. I don't think it's too much to ask to push the file, after every flash.... I already push the libcamera.so to enable my FFC, so pushing another file isn't going to kill me.

Then again, that's just me... and it's not like I can judge how others are using their time.