yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] notverycreative:
That happened to me once. Nope, ya just have to bite the bullet. Small price to pay, in my opinion :)
[Vibrant Android Development] jwilli73:
Page 276. The kang update
[Vibrant Android Development] notverycreative:
This SD card talk reminds me: MicroSD cards don't work for me. Inserting one with the phone running just says it's safe to remove, and inserting one with the phone off just corrupts it and says it needs reformatting. Reformatting it actually reformats the internal SD (luckily, I backed everything up first!) Yes, I am sure this SD card works--I used it for many a Froyo ROM and it served me just fine. I tried formatting it on the phone and PC; the phone only has an option to format the internal SD and formatting it on my PC with FAT and FAT32 both didn't fix anything. I've had this problem since March; does anyone know a fix?
[Vibrant Android Development] cashyftw:
That happen to me before it drove me crazy! Nothing to fix it though.

Sent from my SGH-T959
[Vibrant Android Development] masr1979:
I had that when I first started to flash CM7 on my vibrant. After doing everything that I could think off (Including doing a naked hand stand while performing the format... really I did) I went back to JFD, formatted the sd card there and had no problems when I updated to CM7.

I guess you cold say my motto is "When in doubt, go back to stock"
[Vibrant Android Development] flipper2006:
i dunno if i missed something, but i get better battery then that and I use my phone and bluetooth audio 2 hours a day (driving). I'm currently on 11h 43m on battery.

XiiaLive 42%

Cell Standby 17%

Voice Calls 12%

Display 12%

Phone Idle 7%

Mediaserver 4%

Android Sys 3%

Android OS 3%

Bluetooth 2%

Google Services 2%

I'm at 37% now. This is quite standard for me, people arent getting this much? Now I don't tweet at all but sometimes I use Slingplayer to stream from home (*whch kills battery, but still gets me 12 hours).
[Vibrant Android Development] Hung0702:
Argghh, second time now that I've lost the ability to call/text. I'm on AT&T and have been using the phone with them since August.

First time it happened while I was sleeping (late April). Not sure when it happened 2nd time around, but I haven't been able to resolve this time. Running CM7.1 Kang. I odin'd back to JFD because I was having FC issues. Did not re-partition. It was working ok, and I could intermittently text at first, but now I can't at all.

The first time this happened, I had to odin to JFD and download a beta version of Galaxy S Unlock (I had to relock and unlock my SIM). Tried that again this time and it didn't help. The phone states that it connects to AT&T network (extremely weak signal), but I only get GPRS, not even EDGE. Upon dialing, I don't hear a ring, but a slight buzzing that coincides perfectly with a normal ring's timing.

Anyone got any suggestions? EFS restore did not help either. Is there a KB5 kernel that works with this Kanged CM7?
[Vibrant Android Development] masr1979:
@Hung0702

I lost the ability send text this morning. Everytime I tried I got that little triangle saying the txt could not be sent. I flashed the KA7 radio and so far so good. I'm going to stay on this radio for a few days and see how it works out for me, but it did resolve my other problem.

Why not try reflashing the KA5 radio?
[Vibrant Android Development] Moped_Ryder:
I use a free program called SMS Backup+

It will backup/restore sms messages to your gmail account. You can set the backup freq also. It really works great when you are flashing another ROM.
[Vibrant Android Development] cashyftw:
My backup pro is good for this also.

Sent from my SGH-T959
[Vibrant Android Development] notverycreative:
Okay, I'll just live with it. It's only 1 GB anyway xD
[Vibrant Android Development] Hung0702:
Will do. Are you also using the Kang that atinm posted? If not, I'm afraid I'm too impatient to remain on CM7. Perhaps I'll come back after when more progress is made. Might be stuck on 2.2 for a while :'(

brb. froyo
[Vibrant Android Development] numberoneoppa:
Misread. Disregard.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] masr1979:
@Hung0702

Ok, good luck.

@notverycreative

Ah come on, don't pretend you don't love flashing your phone. LOL! My little sister says I'm the only person she knows that is happy when his phone acts up because it gives me an excuse to take it apart... gotta admit it's not totally frustrating.
[Vibrant Android Development] notverycreative:
Hey, I'm the same way with my lappy! :D
[Vibrant Android Development] fernkomoyo:
all of the eleven updates gives me call bug, it stess me up :(
[Vibrant Android Development] notverycreative:
If you're coming from Kang, you can't flash back to any buildbot nightlies due to a radio and RIL change.
[Vibrant Android Development] shreddintyres:
nightlies 9-11 all have call issues please read back a couple pages at the least, use 8 or prior or use kang on p 260 i believe.
[Vibrant Android Development] hur8111:
Hi atinm any chance for another kang release??
[Vibrant Android Development] Moped_Ryder:
I think we were blessed for the first Kang so dont hold your breath :p

That said the changelog is gettin HUGE! It makes my pants feel funny :eek:
[Vibrant Android Development] fernkomoyo:
Thx Now it is working :P
[Vibrant Android Development] t1h5ta3:
for those with battery issues...

i typicly get 28-30 hours with normal for me usage ( wifi on wether im in range or not, sync on, auto brightnes ) aboutan hour calls, texts, couple hours browsing...

the other day my life droped to about 8 hours, checking system pannel, the only thing diferent is the system process" suspend" it was sitting @ 40%+ cpu useage

even when phone shuld be asleep

.

only thing i can think of that i did diferent was long pressing back to kill/exit apps

today i just kept hitting home instead, and back to 24+ hour life...

side note, ive killed apps in the past with ATM and not had the issue....
[Vibrant Android Development] jzero88:
Great find!
[Vibrant Android Development] krntehknik303:
I hope I'm not repeating anything. But has anyone noticed that the battery percentage skips by 2% sometimes? I go from 100% to 98% idk why. I tried reflashing deleting battery stats and it always does that. Did I miss out on something?
[Vibrant Android Development] cojonesx:
There is no such thing as 100% battery on our phones so there is code to lie to the screen and tell it 100% when its done charging. The quick drop off at high 90% range is just being nice as it drops to its actual %
[Vibrant Android Development] krntehknik303:
OH, I see. Makes sense I suppose. Thanks.
[Vibrant Android Development] atinm:
The bug is fixed, but hasn't been released yet. Next build from buildbot or the one after will have it.
[Vibrant Android Development] atinm:
Actually no - I changed the code.

Battery percentage:

The hardware tells us when the battery is "at max charge" - but reports it as a percentage of actual max. So when it gets to the ~94-96% full range, it reports "at max charge" to prevent overcharge or something. When I see the "at max charge" report, I set a variable to be that number (say 96). Now, from then on - I report the battery as a percentage of that max number that was reported. So, the calculation goes like:

max percentage = 100; (at init time only)
max percentage = current percentage; (when the hardware reports "full")
reported percentage = (current percentage*100)/max percentage; (the rest of the time)

Since the calculations are done in integer math, the values are truncated and so you will see the value getting rounded down.

Also, at each reboot I lose the max percentage number because I don't know what the hardware thinks max is until you recharge back to full. Until that point, I just report what the hardware reports. But once it goes to full again, the percentage number you see is the calculated number.
[Vibrant Android Development] droidfan77:
The change log site seems to be down. Either something went really wrong or this means that we might start seeing nightlies again. Let's hope that nightlies start getting posted soon since the change log was looking really impressive.

http://cm-nightlies.appspot.com/?device=vibrantmtd
[Vibrant Android Development] blahbommer:
Yeah lets hope for nightlies I flashed a miui beta to hold me over but i like the stock lock better im gonna flash the next nightly when it lands
[Vibrant Android Development] zombioptic:
Yeah, I just noticed that too, and came right here to see what's going on. 'Device not supported.' I almost cried at first. Had to calm down a little, realized they wouldn't do that, then got a chubby. :)
[Vibrant Android Development] BigWorldJust:
I just installed this ROM and I can't hear anyone when they call me..and I keep getting the error This feature does not support this system version. I came from Trigger 3.2 FINAL. Someone help =/.
[Vibrant Android Development] pablizzo:
....a little searching and reading would solve all your woes. What build are you on :rolleyes:
[Vibrant Android Development] BigWorldJust:
GRJ22. My home button isn't responding now either, lol.
[Vibrant Android Development] Moped_Ryder:
Ugh

What nightly build # (or kang) are you on?

Edit:

This is not Trigger. Things have work arounds and others don't work. This ROM takes work (IE: reading and learning). Think of the current CM7 as a "beta" version compared to a Trigger "release". You should have read the last 50 pages before flashing this ROM. Trust me the time you spend reading those pages will save you the frustration of a non working ROM.
[Vibrant Android Development] BigWorldJust:
LOOB, I just realized what you meant sorry =/. Haven't rooted my phone in a while. I am running 05252011. And oh so the not hearing people on the other line is something that can't be fixed? MIUI has this fixed right?
[Vibrant Android Development] barribow:
Is it just me or everybody sees the nightly builds stuck on 11?

Much appreciation as a side note to the developers.
[Vibrant Android Development] zombioptic:
The build bot has been down because there aare a lot of changed being made to CM7 in general, I think. I don't think it will be long, though. Keep yer shirt on, bub. :P
[Vibrant Android Development] Moped_Ryder:
I am running 05252011

That is build #11 - it don't work. Build #6, #8 and Kang seem to work best. All still need mute/unmute for to hear to hear you.
[Vibrant Android Development] pablizzo:
BigWorld, look back on the link you used to get the nightly. If it is anything from #9-11 then it has the bug of no audio in calls. Majority of people have reported using build 6 or 8 without issues (minus the mute/unmute bug). I currently running build #8, supposedly the Kanged 7.1 (link is a few pages back) has the call bug fixed for some but not fir others.

Good luck.
[Vibrant Android Development] jzero88:
Man I really wish the dev's would update this forum. If there was an "Update" post which would stay right under the last OP Post would be great. This post could be like a Wiki post. Giving anyone the ability to post updated material, eliminating the same question being asked. These forums actually seem dated...
[Vibrant Android Development] jay661972:
Builld#7 and #8 works for me.
[Vibrant Android Development] atinm:
Eh. That would imply that we're actually trying to do support here . . .
[Vibrant Android Development] cojonesx:
anyone could setup a wiki and put in information about vibrantmtd, let us know when you are done so we can pass a link around, k? thanks!
[Vibrant Android Development] jzero88:
Right! Who wants to do that ;)

I agree, but it would be best to keep it within a single thread, fragmentation is good not.
[Vibrant Android Development] Moped_Ryder:
Kinda what you are looking for:

http://xdaforums.com/showthread.php?t=1061894
[Vibrant Android Development] BigWorldJust:
How would I go from this back to Froyo??
[Vibrant Android Development] jzero88:
You have to use Odin. That is best way.
[Vibrant Android Development] Moped_Ryder:
Go back to JFD then Froyo

http://xdaforums.com/showthread.php?p=13132341#post13132341

Remember to hit the "Thanks" button for s15274n
[Vibrant Android Development] jzero88:
Sort of, but definitely need the ability for users to edit at least one post.
[Vibrant Android Development] cashyftw:
Seriously, this is getting annoying, my text keep force closing, then deleting. It works good for about an hour, then force closes and deletes all of them.

Sorry if I come off as rude, it's just annoying, I can't use mybackup pro after every text..
[Vibrant Android Development] cojonesx:
try deleting your sms data? I haven't seen this issue reported, so honestly no idea
[Vibrant Android Development] jimmyhawk:
My backup pro is cool but to just save texts try sms save. free on market backs up to sd card. Restore anytime. Never had this issue or heard of it b4. I read then delete anyways.
[Vibrant Android Development] jimmyhawk:
Also are you using the cm7 text or a third party text app. If third party app then stop using that app. Try another or just use the stock one. It serves its purpose.
[Vibrant Android Development] notverycreative:
There's an option in CMParts to lock the SMS app in memory to prevent stuff like this from happening. I would try that.
[Vibrant Android Development] vinnydakid:
Try downloading Cache Cleaner NG from the market and run it. I had issues with force closes and that fixed it.
[Vibrant Android Development] junglerumble:
holy **** guys! I have 23% battery left and I'm going to hour 25 right now. everything is also running perfectly. Don't know what happened but I guess my phone took to build 8 kb5 modem better than it did the first time.
[Vibrant Android Development] dasunsrule32:
Wrong, that's for receiving texts, not saving it to non-volotile memory.
[Vibrant Android Development] apollo15rover:
Manage Applications Keeps Force Closing..

Here is dmesg: http://pastebin.com/wMYbcMGq

Any ideas?

(CM7 Issues Tracker seems to be down and I tried searching for similar before posting this)

Attempted usual:

* Reboot

* Battery Pull

* Fix Permissions

* Cache Cleaning

* Reverting to standard system theme

Thanks much!
[Vibrant Android Development] techbeck:
Finally decided to make hte jump from Froyo. Doing backups now but if I am coming from Bionix, I shouldnt have a problem doing the EASY way in the op...right?

thanks
[Vibrant Android Development] timmonss:
I'm having the same issue on SMS.

Oh on a side note, I haven't had to to mute/unmute on the kanged version
[Vibrant Android Development] cashyftw:
It's so annoying isn't it?

Thanks for the tips guys.
[Vibrant Android Development] Jasonhunterx:
Will we ever get hardware acceleration on this rom?
[Vibrant Android Development] VeryCoolAlan:
Wait for the android ice cream sandwich update
[Vibrant Android Development] timmonss:
Pretty annoying I missed a text from a customer. But I guess its not annoying enough for me to switch back to froyo :D
[Vibrant Android Development] TLX317:
This rom is amazing! But I do have one problem...

I'm running on kang, but I've noticed that no matter what build I'm on, the sounds are extremely quiet. Music, ringtones and alarms sound like normal, but the locking and unlocking and the clicks when typing are barely audible and I haven't been able to find any volume setting that is already set to max... anyone else get this? :confused:
[Vibrant Android Development] cal4877:
Welcome to cm7
[Vibrant Android Development] TLX317:
... really?
[Vibrant Android Development] cal4877:
Yes sir I would suggest to install an older version versions 6 and 7 are the best ones.
[Vibrant Android Development] SykesAT:
Thanks for that. I have spent the last hour reading through this thread and I can't quite figure out which version to flash. The audio issues with 8-11 make them a no go. I will try v7 if that is considered one of the better versions.
[Vibrant Android Development] jimmyhawk:
8 is a good version. 9 - 11 are no good. I would recommend the kang version found on page 276 posted by atinm.
[Vibrant Android Development] ugokind:
[REQ] for next rom

in kang and 7 and 8 rel I have a bad audio out.. only mike!

so is important to check with you. I mean: BT in/out is fine. Speaker in/out is fine

Only Voice Out (mic? or??) is bad.. because if I don't speak loudly with the lips INTO the mike.. other people hear noises.. and voice compressed.

I checked volumes.. all is at top level.. and I don't want to use secret codes.. because other 2.3.3 and 2.3.4 roms are fine.. i'm absolutely sure it's a problem in that rom.

wifi:in kang (7 and 8 and .. -> 11 nope) wifi is bad. I cannot connect to router (WPA2) i see that is trying to get IP address. . but never got it. and the icon in the topbar is always grey.

don't ask me to erase data.. cache or not to use titanium. . wasted time.. I did it dozen time before.. are not not those my problems. I started from odin 2.1 tmobile rom.. then applied the kang. stop this test is repeated only 2 times.. but to be sure I'm not writing assthings.. (how do you say cagate?)

eh :|
[Vibrant Android Development] cojonesx:
mute/unmute when using mic, its a known problem thats been around awhile, yes the devs are working on it

I have no issues connecting to a wpa2 router, maybe you should make a logcat and post it for the devs to review?
[Vibrant Android Development] Poser:
Changelog back up...

...and growing

...and growing

...and growing

:)
[Vibrant Android Development] ZeroIsntTheHero:
It's going to be interesting to see how many phones explode when the next nightly is released.
[Vibrant Android Development] ewidtfeldt:
Does anyone know about modems that are compatible with the kang release?
[Vibrant Android Development] ZeroIsntTheHero:
Just the one that comes with it unless Scrizz went through and updated all of the ones in the thread he was maintaining.
[Vibrant Android Development] nextelbuddy:
not quite sure what i did wrong, i was on nightly build 8 and everything was fine. i saw that there was a KANG signed version back a few pages.

downloaded that and placed on root of SD card. rebooted into recovery and i performed a factory wipe/cache and wipe dalvik cache as i always do.

i chose to install the Kang signed rom and it installed. after that was done i also installed the Google apps portion immediateyl after that as i always do.

i rebooted the system, signed in and i was able to login with google credentials but the market wouldnt download ANY apps. i continously received DOWNLOAD UNSUCCESSFUL for every APP.

i performed factory reset and tried again to download APPS ans still no go.

i rebooted back into recovery and flashed build 8 again and now it will not connect or even search for cellular networks.

i cant search for networks or anything so i have to use WIFI to sign in with my google credentials but even after doing so it still can not connect to any networks.

i reflashed Kang signed again and its the same thing.

does anyone have any idea on what i may have done?

i know i can odin back to stock and try again but i would just feel a little better if i could understand if i missed something somewhere or did something wrong so i dont cause this again.
[Vibrant Android Development] Poser:
There is a thread regarding RADIO and CM7 Kang started by "angryattheworld". But it addresses the issue you are currently experiencing (due to new partition layout for modem and/or bad block). Just Search CM7 and baseband and you should find the thread.

edit: link here
[Vibrant Android Development] shreddintyres:
all modems are compatible you just can't flash them you have to extract the modem.bin and push to /radio

use either root explorer or adb to push to the specified directory. ive been running kb5 modem with out flaw for the past few days, that said use at your own risk.
[Vibrant Android Development] droidfan77:
Is there any way that I can push a new modem to my phone by just loading it up on my laptop? I've searched the phone and haven't found the folder that I'm supposed to place the new modem.
[Vibrant Android Development] db3:
you quoted the folder where the modem goes, "/radio". so download your favorite modem (on your laptop). extract the modem.bin file. open a console window and enter: adb push modem.bin /radio. then reboot.

there shouldn't be any more to it (though i haven't bothered with it myself... yet).
[Vibrant Android Development] bigtom624:
What I did was, d/l it to my laptop then I unzipped it using WINRAR. Then I copied it to my phone and from their I moved it to the radio using Root Explorer. Then all you have to do is reboot your phone and your done.
[Vibrant Android Development] ugokind:
2 things:

the mute unmute is for my problem? I don't have a NO audio.. I have a broken audio in out mic ..so only who is talking to me is listening badly

I'm just realized that the adb cannot connect with the device!!!! never happened before! aughhh
[Vibrant Android Development] cojonesx:
1) yes, mute/unmute to fix the crappy audio, the NO audio is on broken builds 9-11 and there is no fix for that other then staying away from those builds

2) another known "problem" use the right drivers

Read the FAQ linked from the first post
[Vibrant Android Development] apollo15rover:
From Latest Changelog..

"Updated kernel for backlight timer shutoff"

Yaaaayyy :D
[Vibrant Android Development] jwilli73:
Use nightly 8 or lower or the kang on page 276 to fix audio. And use the nexus driver mentioned in the OP. All issues can be resolved by reading, friend.
[Vibrant Android Development] Jasonhunterx:
Lord knows when well see that
[Vibrant Android Development] archie53:
We won't.

Sent from my CM7 Powered Vibrant
[Vibrant Android Development] WingCero:
Rom manager doesn't show nightly rom so I downloaded via laptop and.moved it to the SD card.

When in recovery installation gets aborted. Wtf?
[Vibrant Android Development] ugokind:
ok.. tnx.. great
[Vibrant Android Development] jzero88:
Are you flashing the Initial? I think you have to flash the initial, then flash the recovery for Vibrantmtd, then you will see the nightlies. Plus you need Rom Manager Pro
[Vibrant Android Development] wergeld:
You don't need Rom Manager Pro to see the nightly builds - just to download and install them. I use it to check for new builds then go grab my own.

Steps to get a great install:

1) Backup your apps (not system apps) using Titanium Backup (Pro version allows batch operations and I think now DropBox support)

2) Nandroid your existing ROM just in case

3) Download the initial ROM using the First Time instructions in OP and place on your internal SD card

4) ODIN back to stock JFD (bye bye apps! hope your backed em up and nandroided)

5) Install First Time CM7 ROM

6) Let it do its thing

6.5) Install GAPPS (optional)

7) Boot into CM7

8) Open up Rom Manger and choose Install Recovery. It will ask you which one you want. Choose 3.xx (or depending on your ROM version VIBRANTMTD).

9) See what new goodies are in Rom Manger nightly listing

10) Avoid builds 9-11 since they have phone audio issues

11) Profit!

I had a problem with my data partition being nuked. Simple fix was to mount/unmount/mount that partition in recovery fixed it.
[Vibrant Android Development] WingCero:
...damn. Here comes round twenty something. Thanks guys :)
[Vibrant Android Development] Trackstar996:
The hasn't been a new nightly in awhile. Are they taking awhile before sending out the next one or is something going on?

Sent from my...
[Vibrant Android Development] notverycreative:
Go back a few pages. Buildbot's hard drive melted a while ago.
[Vibrant Android Development] Jasonhunterx:
We most likely will as long as there is CM around an this phone is powerful I benches its kind of close to dual cores
[Vibrant Android Development] cashyftw:
Yeah I'm pretty sure we will see ice cream if cm is still around by then.

Sent from my SGH-T959
[Vibrant Android Development] masr1979:
I heard the buildbot was taken in the rapture!!!!!!!!!!!
[Vibrant Android Development] jay661972:
Build# 7 stable for me. No problem at all, with exception of battery life and that's about it.