yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] manjish:
yes graphics is indeed bad

yes graphics performance i horribly low in games in cm 10 and cm10.1......and i don't think its because of phone being too old(slow) for jb...i remember vibrant has some good power vr graphics capable of lot more than that.....

and its not like a bit laggy.....even basic games like subway surfer and temple run brave struggles to be in playable smoothness whenever the scene gets intense. and as the other user said....nothing changes even if i change the graphics settings in dev options.

But i may be wrong and the phone itself might have some bottelneck .i just wrote it today after seeing another user specifying it too.and i hope its some software problem rather than a hardware bottelneck(ya sometime i think vibrant has very less ram)....but yes i have played intense games from gameloft easily but dont remember if it was in bionix era or cm7 era....

i am not complaining and i love CM and have been using cm7 cm9 cm10 and cm10.1 (using cm10.1 as daily driver now too) . i appericiate FE and all involved for what they do . :good: a cool and fresh greeting from nepal to them.
[Vibrant Android Development] Viperatom:
yeah seems to work fine with nova, apex, or ADW but i like running trebuchet. guess ill deal with it for now though.
[Vibrant Android Development] Crossrocker:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

Why isn't this rom recommend as a daily driver? It runs buttery smooth on my friends new vibrant! I was amazed. My evo can't handle cm10 for crap! You guys are lucky.
[Vibrant Android Development] gunks:
The 911 issue(s).
[Vibrant Android Development] FaultException:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

That's assumed fixed (assuming the gps issues do not interfere)
[Vibrant Android Development] skinzy98:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

I have been having some major battery drain like nothing on except for the phone itself and when I get out of school its like 30% and I have a bigger battery and everything I think I'll be switching back to xm10
[Vibrant Android Development] manjish:
@faultexception

if there is no changes mentioned in http://changelog.bbqdroid.org/#vibrantmtd/cm10/next is it worth it to upgrade?? i see file size changes though there ae no changes in changelog....
[Vibrant Android Development] hendykhanh:
Changelog for CM10.1 not CM10 .

http://changelog.bbqdroid.org/#vibrantmtd/cm10.1/next
[Vibrant Android Development] edmc:
I am seeing my homescreen icons for installed programs with the names listed as the package name rather than application name... anyone else seeing this? This behavior seemed to begin with the 1/18 nightly. It's innocuous as simply deleting the icon and re-installing it (not the program/package, just the icon) returns the preferred behavior.

Anyone else seeing this?
[Vibrant Android Development] caubecari:
wifi tether work with this Rom?
[Vibrant Android Development] CTown:
Yes, you also have options for usb and bluetooth tethering. You can find the tethering option by holding the usb or wifi tethering tiles or by going to:

Settings-> Wireless and Networks -> More -> Tethering and portable hotspot
[Vibrant Android Development] Homeless2:
Does anyone have an issue where the backlight will be at like 1% after waking up the screen? Adjusting the backlight level doesn't do anything once it happens. Rebooting the phone seems to work until it happens again
[Vibrant Android Development] deus_:
Happens to me about twice a day. Please let me know if you find a solution.
[Vibrant Android Development] edmc:
Hmm... no response. Strange...

Let me update:

A byproduct of homescreen applications having been moved to the SDCard (TitaniumUpdate method)

Appears following reboot

Can be "corrected" by deleting icons and re-creating them

Can also be "corrected" by "hiding" icon labels and unhiding them (System settings->Launcher->Homescreen->Hide icon labels)

Caveat of hide/unhide is that the SDCard should be completely mounted/available (some time after reboot)
[Vibrant Android Development] Dave08:
I was seeing this with just one app -- Aldiko. It would re-occur after every reboot. I'd originally restored Aldiko with Titanium when I flashed this rom. I seem to have fixed the problem after backing up its data, uninstalling the app, re-installing it from Play, and then restoring only the data. I'll post an update if anything changes.
[Vibrant Android Development] renegadedj:
My two vibrant phones both on the latest nightly, 4.2.1 android version, Odin does not see either.

I want to flash back to stock. Do I have to go through some extra steps of downgrading before I can flash back to stock?

Thank you in advance for any help.
[Vibrant Android Development] CTown:
Do you still have this problem? I once had this problem but forgot how I solved it. But since the forums have been quite slow, here are some of the things I tried:

1)Use different combinations of usb cables and ports. (It helps to open Odin after everything you get in Download Mode).

2)Attach the USB cable to the PC (but not the phone), take out the battery, stick in the other end of the USB cable, hold the volume keys while putting the battery back in. Then open Odin.

3)If that doesn't work try to reinstall the Samsung drivers (remove the driver, reboot, install the driver again, then reboot once more).

4)Another solution is to use Heimdall (use version 1.3.1, I don't know if the regression in 1.3.2 affects us) and the driver it comes with.

5)if you don't want to bother with Heimdall on Windows, use a Live Linux CD (You can find the Debian binaries which will work on distributions such as Debian, Ubuntu, and Linux Mint on its website)
[Vibrant Android Development] gdpaull:
I believe I had a similar issue at one point, and it was related to not having the proper drivers installed on the PC. It's worth a try...Here's the link.

http://xdaforums.com/showthread.php?t=728929
[Vibrant Android Development] anilo:
I have a problem with Wi-Fi but it might be related to my particular device and not ROM (especially CM) related. I have the latest nightly installed. Anyway, here it goes:

Whenever I connect to wireless networks, whether at home, work or the coffee shop, the signal bar goes gray and then blue as it is supposed to to indicate that it connects to Google services. However, 10 out of 10 times, it disconnects from the Google servers (signal bar turns gray) after a short while, therefore, losing the connection to send/receive data. I have to turn the Wi-Fi off and on again in order to establish a connection. Does anybody else have this problem? Any solutions?

Note: I keep Wi-Fi on during sleep setting at "Always" and did not check "Avoid poor connections".

Thanks.
[Vibrant Android Development] cricketz66:
wifi loss

[QUOTEo;37283485]I have a problem with Wi-Fi but it might be related to my particular device and not ROM (especially CM) related. I have the latest nightly installed. Anyway, here it goes:

Whenever I connect to wireless networks, whether at home, work or the coffee shop, the signal bar goes gray and then blue as it is supposed to to indicate that it connects to Google services. However, 10 out of 10 times, it disconnects from the Google servers (signal bar turns gray) after a short while, therefore, losing the connection to send/receive data. I have to turn the Wi-Fi off and on again in order to establish a connection. Does anybody else have this problem? Any solutions?

Note: I keep Wi-Fi on during sleep setting at "Always" and did not check "Avoid poor connections".

Thanks.[/QUOTE]

I was also having this issue. I believe it has something to do with the WiFi optimize option after un checking it it seems to have went back to normal

Note: same settings as you
[Vibrant Android Development] Martezgarki:
I had a slightly different problem last time where my connection to the WIFI will be disconnected when the phone idles for some time. I went into WIFI advanced settings and disabled settings that seems to reduce the functionality of WIFI to conserve battery, set it to ALWAYS too like what you did and the problem's gone, just thought it might help.
[Vibrant Android Development] cricketz66:
chronos

does anybody know how to change the Celsius to Fahrenheit on the Cronus widget on home screen
[Vibrant Android Development] davidgs:
I'm having an issue in my wife Vibrant, she changes batteries for charged ones because her USB isn't working, but every time she changes it and restart the phone, her selected ringtone don't stay, it changes (probably) for the default and it shows "unknown ringtone", or something like that, same for the notification tone. We both have vibrants and are using CM-10.1-20130124 and I don't seem to have that problem. The only difference with mine is that I have GB Bootloaders and she still has Froyo's, can this be the problem? does anyone have a suggestion?

Thanks!
[Vibrant Android Development] dasunsrule32:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

You need to be on the GB bootloader
[Vibrant Android Development] Dougfresh:
Sounds like you're using ringtones from your SD card. Happens to me on Slim. If they're .ogg then you can move them to System/Media/Ringtone and set proper permissions and reboot.
[Vibrant Android Development] CTown:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

Just disable the "use metric" check box found at: Settings -> System -> Clock Widget -> Weather Panel
[Vibrant Android Development] edmc:
Not sure what the root cause is but I've narrowed the problem down to apps that have been moved (by Titanium Backup) to the SD Card. I can cause Trebuchet to reload the app names by selecting Settings->Launcher->Homescreen and checking the Hide icon labels checkbox, then exit to the Homescreen, then going back and un-checking this checkbox. This seems to also reset the fetching of the app names in folders on the Homescreen as well (note: the app names in folders are not hidden by the above checkbox however).

Perhaps I'm one of the few that places apps on the SD Card... so as am unusually affected by this apparent timing issue :confused:
[Vibrant Android Development] samsgun357:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

FYI, GB boots aren't required and have absolutely no effect on a ringtone. I have flashed every single jb41 and jb42 ROM for the vibrant without GB boots.
[Vibrant Android Development] edmc:
I just verified my suspicion. Moving all apps that are on my Homescreen and/or in a Folder back to "internal memory" (using Titanium Backup) removes the problem. Immediately after boot, the names under each icon/app are correct.

I should have mentioned this earlier... when they were not correct, what I'd see is the name of the package rather than the app name. The icons would be correct however.
[Vibrant Android Development] DonutYankee:
It's been ages since I've flashed a phone with an old stock rom. Anywhoo, I have a friend's phone that has an old KA7 ROM on it with <3e> recovery. If I remember correctly, that one only takes signed ROMs, no? Any advice on getting CM on that one?

EDIT: I should clarify: what I really need is the go-ahead from someone who knows for sure, so that I can go ahead and put the GB bootloader and then go Stock -> CM. I've done that on my phone a long time ago, but am not sure if doing the usual will work with this one due to its recovery. Thanks for any help.

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

I've been on GB bootloader for ages, I also had that issue with some CM ROMs.
[Vibrant Android Development] CTown:
Use Odin or Heimdall to go back to JFD. Then, you will have two options:

(1) Just rename the latest nightly to update.zip and flash from recovery or

(2) Rename ClockWorkMod2 (CWM2) to update.zip and keep trying to flash CWM2 untill you have the green recovery. Then flash the latest nightly.

Also, unless you want to use a TouchWiz3 based GB ROM (even though CM7 is a much better GB ROM) the GB bootloaders are pointless... all that will change is you don't have to hold both volume buttons when going into recovery mode.
[Vibrant Android Development] DonutYankee:
Thanks a ton for the reply. As for the GB bootloaders, I thought way back that even CM needed them for its 2.3+ ROMs on the Vibrant. Guess I just forgot about the details on that.
[Vibrant Android Development] Dougfresh:
Guys, just blast GB BL's, and never turn back. It takes 5 seconds
[Vibrant Android Development] DonutYankee:
The person I'm flashing this for will not care and never worry about which BL. This phone made it just fine to CM, and that's all they need.
[Vibrant Android Development] CTown:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

I get that it is very fast to flash the boot loaders but it doesn't do much if you want an AOSP ROM and flashing the BLs is pretty much the only way you're ever going to brick your phone. Also, the boot loader says "i9000" when flashing back to JFD (though I haven't been on JFD in a while). I'd put the BLs in the same category as the GPS fixes at this point: pointless and potentially dangerous (which is the point of this post).

I understand that I sound like a killjoy at this point (I don't mean to put you on the spot), so I'll conclude with this: Everyone is free to flash (or not flash) anything he or she wants. After all, we are here to make the devices we bought "ours"!
[Vibrant Android Development] Dougfresh:
Cool!! i does say I9000 after returning to JFD. I re-flash BLers afterwards again so i reverts to the 959 shizz. if you ask me how many times I've blasted GB BLers, my estimate is about give or take, 227 times

:p follow instructions and everyone will be OK. also its so much easier to go into recovery and DL mode imho

Sent from Jawz
[Vibrant Android Development] edmc:
This bug is tracked in the Issues Log here
[Vibrant Android Development] Moronig:
My only issue with the rom is that if I leave GPS enabled, after a while cpu usage goes to 100%, phone slows down, and the battery drains fast. I need to reboot when that happens.

Opened a new issue in the tracker.
[Vibrant Android Development] renegadedj:
Question! In the latest nightlies, is there any way to change the lockscreen to a simple single screen unlock screen? Not the slide screens where I can accidently hit the camera screen or the other widget screen? I dont want that! haha!
[Vibrant Android Development] Dougfresh:
Lockscreen Policy from the play store and follow the instructions ;)
[Vibrant Android Development] dE.fUsEd:
So, I've been on 10.1 for a while, and ever since, I can not Reboot to Recovery using normal options, the phone just reboots normal.

The only way I can get in to recovery is to open Rom Manager, flash recovery, then reboot recovery from INSIDE Rom Manager.

No other way works.

It's kind of annoying. I decided today to flash back to stock using ODIN and start fresh again.

From stock, I install CM7. I can reboot to recovery using CM7 no problem.

From CM7, I install CM10.1 nightly (the latest), and after the phone finally gets in to 10.1, I can no longer reboot to recovery from the reboot menu.

I have to install Rom Manager, then flash recovery from it, then reboot from it.

I have to do this process EVERY time I want to reboot recovery.

Any other way I try, it just reboots normally and not in to recovery.

What gives? Anyone else with this problem?

Thanks.
[Vibrant Android Development] samsgun357:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

Download ROM toolbox pro, it has Rebooter included. I know this doesn't completely fix your issue.

Have you tried different button combo? Just vol+ and power, or vol- and power

Good luck

Id est quod est
[Vibrant Android Development] richwright:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

In system settings select system, power menu. Enable reboot menu. This will give you the option to reboot. When you press your power button you will have the option to reboot. Select reboot you will be presented with the option to reboot or recovery.
[Vibrant Android Development] dE.fUsEd:
No, the option is there to reboot to recovery. It just DOESN'T reboot to recovery. It reboots normal. No matter what I do.
[Vibrant Android Development] richwright:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

Works as it should. Just used reboot into recovery to confirm. CWM-based Recovery v6.0.2.3

I am running Nightly 2/11/2013

What version are you running? Are you using a different Kernel? Also have you done a wipe/reset since moving to 10.1?
[Vibrant Android Development] hendykhanh:
Up 4.2.2 :)
[Vibrant Android Development] larrisa12002:
Steps:

1.Power off.

2. When its off, press volume+, volume- and power at the same time and just hold.

3. When you see Vibrant boot splash, let go immediately and wait for it to boot into recovery. If what appears is "unknown upload mode", remove the battery.

4. Put back battery and repeat step one if step 3 fails.
[Vibrant Android Development] alkaid14:
if theirs an update for this 10.1 how do I flash it? boot to CWM and flash to new release? by the way im using 10.1-20130131
[Vibrant Android Development] gun:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

Go to settings/ about phone /updates
[Vibrant Android Development] alkaid14:
ok thanks!
[Vibrant Android Development] protohamster:
This rom seems very stable to me now. Even GPS works well. Any chance it will shed the BETA tag soon?
[Vibrant Android Development] flapane:
I'd like to upgrade from 10 to 10.1.

Is the partition layout identical? In other words, may I backup apps and data using Titanium Backup and then safely restore all the NON-System apps?

Any feedbacks other than the tips in the first post of this thread?
[Vibrant Android Development] gdpaull:
I just updated to 20130219, and I'm having a similar issue--except with me there is no option to reboot into recovery...only reboot. Even when I power off, hold down power, volume up, and volume down at the same time, I am still not able to boot into recovery.

EDIT: I reverted back to 20130218, and my recovery is back as it should be.

Anybody else experience the same thing?
[Vibrant Android Development] Virtuososteve:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

What kernel do you guys use and are you doing anything special to get gps working?
[Vibrant Android Development] jrafael:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

For extended reboot menu, you need to select the option in the developer menu.
[Vibrant Android Development] jrongi1:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

You follow that and you should be fine.

PA_Vibrant 360° Productions
[Vibrant Android Development] gdpaull:
Thanks...is this a new thing? I never had to do that before, unless somehow it was a default setting that disappeared with the update.
[Vibrant Android Development] gunks:
Yes it is new as of a couple days ago... CM implemented it for people who have others using their phone often as a security measure.

Source: https://plus.google.com/117962666888533781522/posts/iWRWc4bdXJb
[Vibrant Android Development] CTown:
You can keep up with CyanogenMod development and the decision behind many of the CM team's on their Google+ Page.

The idea behind it was that the reboot to recovery option was a huge security flaw that made it way to easy for someone to get to recovery mode and have full control over your device. Also, for the same reasons, the reboot to recovery option will be hidden from the power menu until you unlock your device.
[Vibrant Android Development] gdpaull:
Recently, I took the tethering portion off of my bill so that I could get unlimited data. This ROM makes it so that I can still tether for free, correct?
[Vibrant Android Development] CTown:
Yeah, just enable tethering using the tile or just go to the settings menu. No special plan required.
[Vibrant Android Development] gdpaull:
deleted
[Vibrant Android Development] alkaid14:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

deleted
[Vibrant Android Development] frankdrey:
I'm setting up a Vibrant for a friend. I need something ICS+ and am wondering what is the MOST stable? It's for his mom, so it needs to be completely bug-free.

I see that there's a CM10 stable but I hear battery life is terrible and GPS does not work well. What about CM10.1?
[Vibrant Android Development] flapane:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

I'm on cm10 nightly (see the signature). The battery duration is the same as on cm7 and I haven't discovered any bug so far.
[Vibrant Android Development] mrbradeli:
Just installed the latest nightly, and I noticed that my music is skipping. They're just regular q6 vorbis files, and I'm pretty sure there was no skipping on the last nightly I was using since December.
[Vibrant Android Development] Sdobron:
Last few nightly builds seem to have broken something with wakelocks...battery has been draining due to GPS constantly looking for signal (and no it's not an app, GPS is even completely disabled in location settings). Additionally, Better Battery Stats shows another wake lock for audio out...there is no media being played on the phone at all.

Anyone else experience this? Or...is it time for a data wipe? Running 4.2.2 Gapps from Goo.Im also.
[Vibrant Android Development] gunks:
Maybe try wiping caches and fixing permissions...
[Vibrant Android Development] sada23:
I think I agree with you on some of these issues. I do see a drain in battery.
[Vibrant Android Development] tbrar:
Phone is slow

Hi,

My phone is very slow. Scrolling in the app drawer etc is fine but actions like opening applications, playing games is very slow. Opening and loading messages in messaging app takes a lot of time. Gameplay in games like temple run is stuttery and slow. I am on latest nightly. I have wiped data and system and reinstalled but lag is still there. Overclocking to 1.2 Ghz results in phone hanging. Can somebody suggest a kernel or some settings by which I can make the phone usable.

Thanks
[Vibrant Android Development] gunks:
Probably need to wipe data if you havent in a while... Also, use the latest Semaphore kernel.
[Vibrant Android Development] tbrar:
I have already tried wiping data. I will try the semaphore kernel.

Thanks
[Vibrant Android Development] gunks:
I'm on the latest nightly and everything is running very smooth and up to speed for me.

Live OC @ 110

Ondemand gov

Bigmem enabled

Purging of assests enabled

Other than that you can go to Apps in Settings and see whats running and slowing you down. Also, BetterBatteryStats works wonders.
[Vibrant Android Development] Stevethegreat:
So M2 was released today and every other galaxy s device was supported apart from ours. FE can you explain why is it so?
[Vibrant Android Development] jrafael:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

It's just a label... :rolleyes:
[Vibrant Android Development] dasunsrule32:
Re: [ROM][OFFICIAL][4.2.1] CyanogenMod 10.1 Nightly Builds for the Samsung Vibrant

Well, technically, a tag :P
[Vibrant Android Development] flapane:
Not in the list... http://www.cyanogenmod.org/blog/cyanogenmod-10-1-m2-release

I guess it's because of GPS, I can't see any other reasons.

Is FE still around, by the way?
[Vibrant Android Development] FaultException:
Nobody here but us chickens.

I haven't really contributed code lately, but I'm alive. I just marked the Vibrant for future 10.1 M releases.
[Vibrant Android Development] ZUBAIR1291:
update problem....

my vibrant do not update from the update app it just boot do not go into recovery i am on latest nightly......it is from almost 2 weeks..