yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] samsgun357:
When it gets to about 98% it will stop charging. Unplug it and plug it back in(phone end, not ac plug). It should start charging again but I've noticed when the screen turns off, it will stop charging so you might have to keep screen on to get to 100%.

I read that continuing to charge once at 100% isn't good for the battery and that it does this as a protection measure.

I am Jack's complete lack of surprise.
[Vibrant Android Development] Panamon:
Unfortunately, still a no-go.

Rebooted and let the phone deep sleep w/o 1st locking GPS.

Started GPS Test and got blinking Icon, but no sats showed up.

I happened to notice this time that all it took for the icon to disappear was for the screen to turn off.

I hit the power button to turn the screen back on immediately but icon was gone.

I killed GPS Test and restarted it but icon never came back.

(I continue having success auto-starting GPS Test on boot though.)
[Vibrant Android Development] hendykhanh:
I think AGPS for vibrant use good with network . I test with wifi or 3G work fine. after DS or overday it will work when i open GPS and network together . ( i don't have reboot )
[Vibrant Android Development] Panamon:
I don't have to reboot either. I just have to start gps before DS and I can lock from then on even after subsequent deep sleeps.
[Vibrant Android Development] FaultException:
Another GPS test kernel:

http://d-h.st/8O8
[Vibrant Android Development] closedcircuit:
GPS Lock before DS - Yes.

GPS Lock after DS - No.

Notes:

1. Initial GPS Lock @ ~5 minutes.

2. After DS, 13 sats in view with no signal except for a single blip on 1 transponder for < 3 seconds @ around the 2 minute mark.

3. DS was for 1 hour 20 minutes prior to trying GPS lock again.

4. GPS icon remains blinking after DS attempting to get a lock for at least 15 minutes. Did not test duration for any longer.

Can record logcat's on future tests upon request via PM.
[Vibrant Android Development] FaultException:
If you close GPS app and reopen after DS does the icon reappear?
[Vibrant Android Development] closedcircuit:
Yes the icon does reappear.

But now after rebooting, GPS apps all show the same symptoms of seeing "In View" sats's but not getting any dB from the transponders.

I also forgot to mention I'm using cm10 stable.
[Vibrant Android Development] FaultException:
It shouldn't reappear if it failed, it not appearing is indicative of the gps daemon crashing... Could you get me a logcat?
[Vibrant Android Development] closedcircuit:
The GPS "circle" is always present and blinking in the upper left hand corner, while 13 sats are in view but 0 are in use with 0 dB across the board. The GPS Circle never stopped showing up I just reverted to a stock cm10 nandroid to see if GPS will still lock. I will do the stock GPS test 1st then nandroid back to the test kernel and get you a logcat.

Edit 1: Any preferable settings/format(html) for the logcat other than verbose?
[Vibrant Android Development] FaultException:
Normal is fine
[Vibrant Android Development] mohamobo:
GpsTestKernel-LOC1

GpsTestKernel-LOC1

Same result as all previous test kernel. Death after DS.

GPS fine if start before DS then after DS also fine.

My GPS crash is same with Panamon.

GPS icon will show and blinking with no bird show then reopen back or lock screen no GPS icon show.

Last - Why your test kernel is Linux version 3.0.52 but stock kernel is version 3.0.31?
[Vibrant Android Development] hendykhanh:
Yup . GpsTestKernel-LOC1 work well .

I try it morning . and now i test it after DS it still work fine .

Thanks FaultException hard-work .
[Vibrant Android Development] FaultException:
Uhh... Maybe my kernel tree still has the 4.2 version. I'll have to check.
[Vibrant Android Development] grose65:
Every time I use my phone for a long call or play Pandora for a while my cpu gets stuck at 1000 in CPU usage. I am on nightly 11/30 stock build. Any help.
[Vibrant Android Development] Panamon:
LOC1 - does not survive DS w/o start up lock.

Icon appears but disappears if screen goes off like before.

I left it up for 15 mins. and never saw any sats.

FE, (a wild guess), but it almost feels like the initial lock caches data that must already exist prior to DS. If this is somewhat true would it be possible to spoof that data on boot?

I keep thinking that a hack is the only way but only because no real drivers exist that would allow actual solutions to be built.

Again, just thinking out loud.
[Vibrant Android Development] closedcircuit:
Are you getting any sats "In view"? Or are you just not getting any sats "In use"?

Edit: Followup Test

Test conditions:

1. Using GpsTestKernel-LOC1 & CM 10.0.0 Stable

2. Acquire Initial Lock (IL) before DS - No

3. GPS lock after DS - Yes

Notes:

1. 1st Lock after DS "In view" sats slowly went from 0 to 10 sats instead of the normal instant viewing of 12 sats.

2. 1st Lock after DS took ~ 4 minutes.

3. Subsequent GPS locks occurred much faster.

4. After letting the phone go back into DS phone still acquires lock avg 70 seconds.

5. Trying to break GPS daemon "Circle" unsuccessful by way of quickly opening and closing multiple GPS apps successively.

This test session's logcat available upon request via PM.
[Vibrant Android Development] FaultException:
Another GPS test kernel:

http://d-h.st/l1y

EDIT:

Another:

http://d-h.st/xfm
[Vibrant Android Development] ioancr:
I remember this happening on RemICS, I always got instant in view sats on reboot (it was much like a lock after DS).
[Vibrant Android Development] Panamon:
won't be able to try this until later tonight.

(@closedcircuit, on LOC1 I saw only blinking icon. No sats in view at all.)
[Vibrant Android Development] Richcar:
Same old problem with frist test kernel lock before and after DS, allow to DS without locking after reboot no icon and nothing after DS you must lock after reboot to get a lock after DS.
[Vibrant Android Development] mohamobo:
RLS.

this kernel totally death no icon at all.

CRG

reboot, gps, ds, gps = ok

reboot, ds, gps = death
[Vibrant Android Development] FaultException:
Using an alternate CPU governor?
[Vibrant Android Development] hendykhanh:
Work well than LOC1 .

Before or After DS work well don't need network !

Next build we have new GPS on rom ??? i see changlog show it ?

Changes in next cm10 nightly for vibrantmtd

Merge "vibrantmtd: Simplify GPS rc" into jellybean

MERGED ON DEC 02ND AT 13:42:37 IN ANDROID_DEVICE_SAMSUNG_VIBRANTMTD

vibrantmtd: Simplify GPS rc

MERGED ON DEC 02ND AT 05:18:29 IN ANDROID_DEVICE_SAMSUNG_VIBRANTMTD

I think kernel CRG work well .
[Vibrant Android Development] taurus193:
FE .will you update to 4.2.1?
[Vibrant Android Development] closedcircuit:
Test 1 conditions:

1. Using GpsTestKernel-RLS & CM 10.0.0 Stable

2. Acquire Initial Lock (IL) before DS - NO

3. GPS lock after DS - NO

Notes:

1. GPS Daemon Icon/service seems broken.

2. 0 In View, 0 In Use

Test 2 conditions:

1. Using GpsTestKernel-RLS & CM 10.0.0 Stable

2. Acquire Initial Lock (IL) before DS - No

3. GPS lock after DS - No

Notes:

1. No GPS Daemon Icon present.

2. Phone never actually goes into DS, All CPU states from 1200 Mhz down to 100 Mhz are used except DS.

Test 3 conditions:

1. Using GpsTestKernel-CRG & CM 10.0.0 Stable

2. Acquire Initial Lock (IL) before DS -No

3. GPS lock after DS - No

Notes:

1. 14 Sats in View with 2 showing 19-21 db, 0 Sats In Use after 15 minutes.

2. GPS Daemon seems active as indicated by the blinking icon. Doesn't break when switching from app to app.
[Vibrant Android Development] zhuzf:
Has anyone tried V6 Supercharger script on CM10 roms?

links here: http://xdaforums.com/showthread.php?t=991276/

It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.

Really?
[Vibrant Android Development] mohamobo:
FE, I'm having more battery life with your test kernel (Linux 3.0.52). It is possible to update stock kernel to Linux 3.0.52?
[Vibrant Android Development] mrbradeli:
Any idea why I'm having trouble installing Google Apps? The latest nightly seems to be working well enough, but I can't install the latest Google Apps zip. Should I be doing it from somewhere else that isn't recovery?
[Vibrant Android Development] closedcircuit:
Try and verify the gapps you downloaded has the correct md5 checksum. I've been noticing that I've been getting higher occurrences of corrupted downloads from a lot of the android file repositories lately. Gapps should definitely be installed from within CWMR.
[Vibrant Android Development] skinzy98:
I haven't been following following this thread recently and I known this is now official so are all nightly official or are certain ones meant for stable use. I have been using this one but I didn't think I would be flashing anytime soon

Edit: Nevermind I just checked and I'm on the latest stable build
[Vibrant Android Development] blizzardproof:
Has anyone tried using devil's kernel with some of the newer stable builds
[Vibrant Android Development] Globespy:
FE/others.... you guys have to be commended for your ongoing refusal to bed content with the GPS lock issues. I'm just as passionate about findinga fix for this ASD you are as I've always relied heavily on my vibrant's GPS availability. I was excited by the post a few pages back that said that they were getting constant icon blinking even after no initial lock on boot and then opening and closing the GPSTest app. I have a feeling that a hack is the solution as someone else recently pointed out. Not as elegant as a driver based solution, but if it resolves the need for locking on boot, then it's a win.

Keep at it guys!
[Vibrant Android Development] Panamon:
That was the point I was trying to make when I suggested the possibility of addressing this pesky issue with a hack.

IMHO when you combine the Vibrant's wonky GPS and the lack of an official kernel and drivers beyond Froyo, Samsung leaves no other solutions but work arounds.

The GPS before DS technique seems to work for most. I just wish someone with the knowledge would polish it up and make an automatic and more transparent solution.
[Vibrant Android Development] samsgun357:
I mean no offense and am grateful for the strides that have been made with the vibe GPS and JB but if you truly depend on GPS, get a different device.

I am Jack's smirking revenge.
[Vibrant Android Development] jrongi1:
I have to disagree with you on this one, I successfully use my vibrant for gps daily (work navigation).

PA_Vibrant 360° Productions
[Vibrant Android Development] samsgun357:
That's awesome, your 360 version with ICS GPS files works awesome for me but for crack flashers you never know if GPS will work on the next ROM. I personally wouldn't depend on my vibe for work related GPS.

J, you are the man so I'm sure yours is solid!

I am Jack's smirking revenge.
[Vibrant Android Development] jrongi1:
Actually it is the open 360 release (stock files) but I have a vibrant that has unusually good gps if it works at all it works for me.

PA_Vibrant 360° Productions
[Vibrant Android Development] L1LK1LLERZ:
I'm stuck in the boot after changing the DPI. Any solution?
[Vibrant Android Development] Dougfresh:
dirty flash again, wipe cache and dalvik and rip it....
[Vibrant Android Development] FaultException:
Did you reset the correct build.prop permissions? JB is more picky about permissions.
[Vibrant Android Development] L1LK1LLERZ:
I used an app called LCD Density Pro to change it. I usually do it manually, but I heard someone say it's better, so I got it.

So, next time I wanna change it. I just do it manually, and check permissions, then restart? Let me know if there are other ways to change it.

Also, does anyone know how to fix the play store compatibility issues with 210 DPI?

Thanks.

---------- Post added at 11:23 AM ---------- Previous post was at 11:22 AM ----------

That's what I did. Currently on stock DPI, which I hate! :mad:
[Vibrant Android Development] akfelipe:
Anyone else having gallery force closing(launcher as well but then restarts immediately) problems? im on 'cm10 stable'.

Trying to upload pics to facebook or just plain browse pics in the gallery app recreates it. no typical force close notification appears, it just closes..

I deleted gallery cache and force stopped it, and restarted my phone etc.. but still there

i never had this problem on previous nightlies..bad flash?
[Vibrant Android Development] FaultException:
Right. You can still use an app just make sure the permissions are exactly what they were before.
[Vibrant Android Development] flapane:
Can I safely delete Gallery apk (actually I see two gallery apk's in /system/app)?

I've never used it, I prefer Quickpic.
[Vibrant Android Development] FaultException:
Camera is packed into the Gallery apk, so not unless you use another Camera app as well.

What do you mean by two Gallery apk's though?
[Vibrant Android Development] flapane:
My bad, I confused Galaxy2.apk with "Gallery2.apk"...

However a more serious problem showed up: I can't enable wifi while in airplane mode. The switch remains stuck on: ACTIVATING WIFI.

The same happened on CM9 months ago, while it works well on CM7.

Dmesg and logcat show just a few lines and nothing regarding wpa/wifi.
[Vibrant Android Development] testomat:
Deleted
[Vibrant Android Development] dE.fUsEd:
Latest nightly on my vibrant, can't connect to market, also getting a bunch of things crashing.

Android Keybord AOSP crashes every time I go in to anything that uses text.
[Vibrant Android Development] gunks:
Try a clean install.
[Vibrant Android Development] Dougfresh:
I believe you must've flashed the 4.2 gapps instead of 4.1.2 gapps.
[Vibrant Android Development] dE.fUsEd:
Hmm, this is possible.

Let me try a different one.
[Vibrant Android Development] Globespy:
Ditto! Still rocking PA 2.5.4 360 with Semaphore 2.5.0!

After doing the hardcore hardware fix (I actually soldered a direct connection between the circuit board GPS antenna and the case), I am consistently in the sub 20ft range (normally around 15ft) so using GPS navigation is better than my aging Garmin which doesn't have many of the new streets/developments because of old maps.

I'm awaiting delivery of my Nexus 4, I can only hope the GPS works as well as my Vibrant (yes I just said that!!!).
[Vibrant Android Development] flapane:
Trebuchet launcher doesn't save the second icon in the dock (on a classical 5 icons layout) starting from the left.

Everytime the app reboots (and we know it happens quite often due to low RAM memory) I get an empty space between the first and the third icon.

edit: by the way, I wonder if this launcher is still supported/developerd (is v0.2 recent?) and, in case it doesn't, whether CM should still include it.
[Vibrant Android Development] FaultException:
Repurposed thread for CM10.1 nightlies.
[Vibrant Android Development] zhuzf:
Great! When will the first CM10.1 nightly be uploaded?
[Vibrant Android Development] larrisa12002:
FE, how does this differ from your CM10.1 Alpha thread?
[Vibrant Android Development] hendykhanh:
Where link download Nightly 10.1 ???
[Vibrant Android Development] josh2020glacier:
I see the change log I think its being built maybe it will be done tomorrow. Trust me when i day i can't wait either.
[Vibrant Android Development] zhuzf:
FE, will you continue to update cm10 nightlies after the cm10.1 debut?
[Vibrant Android Development] mohamobo:
FE, I can confirm that this http://review.cyanogenmod.org/#/c/27384/ work with cm-10.1
[Vibrant Android Development] FaultException:
This is for the nightlies, the other is for the alpha builds.

Thanks.
[Vibrant Android Development] flapane:
Did anybody notice that Adobe flash player is awfully slow (like 1-2fps), or it's just my case? (well, actually it's not supported anymore by Adobe, but you still can install the apk)

It worked great with GB.
[Vibrant Android Development] te_quiero_forever_girl:
I flashed the stable version of cm10 (coming from cm9 nightly with FULL WIPE). When it finished and I hit reboot system now, it keeps rebooting into recovery. Any suggestion ?
[Vibrant Android Development] flapane:
I'd re-flash because of new partition layout, I guess.
[Vibrant Android Development] imilleson:
I miss my vibrant a little
[Vibrant Android Development] josh2020glacier:
Why downloads say cm10 but the change log says cm10.1?

Where is the downloads for cm10.1???

??????
[Vibrant Android Development] zhuzf:
Be patient！Might have problems with Vibrant porting.
[Vibrant Android Development] jpchopper:
I downloaded no problems. It gave signature unverified but just installed anyway. It's 4.2.1
[Vibrant Android Development] FaultException:
They're not up yet.. are you sure it's not 4.1.2?
[Vibrant Android Development] jpchopper:
My mistake! I had downloaded CM101220 and CM10.11220(skankwich)

The latter is what I had installed and works. Tried going back and installing the other, got boot loop. So back to waiting!
[Vibrant Android Development] bill_kevin:
i install this cm-10-20121219-NIGHTLY-vibrantmtd.zip and gapps-jb-20121212-signed.zip when start always say me Unfortunately, Android Keyboard (AOSP) has stopped. how fix the problem thanks.
[Vibrant Android Development] zhuzf:
That gapps is for cm10.1, not cm10.
[Vibrant Android Development] New_Guy777:
Battery Life...

To those asking about battery life...we can't answer yet.

It takes about 4-5 complete discharges and full recharges after flashing a new ROM to really get an appreciation for the battery life. The ROM's only been in nightly status since the 18th, and anyone who flashed one of the updates has had even less time to evaluate.

Overall, it seems to react like my ICS ROM's when I was first setting them up. However, only time will tell if it will actually get me the 1.5-2 day battery life that I came to enjoy with those (original stock battery).
[Vibrant Android Development] CTown:
I believe next nightly!: http://review.cyanogenmod.com/#/c/21799/

I'm still on one of the previews but the battery life is pretty good (I'll try the next nightly). Thanks again FE, for continung to maintain the Vibrant!

edit: Sorry, I just noticed that the commit I linked to has been verified but not merged yet (as of this edit)...
[Vibrant Android Development] Drjjones426:
I'm trying to install apps from the market but keep getting the following error: unknown error code during application install "-24"

I did wipe everything and format when coming to cm10 8/21 nightly
[Vibrant Android Development] Toast6977:
Did you go to settings>apps find play store, force stop it and clear data? That might help you.
[Vibrant Android Development] hurtz777:
Gabriel just use an old version of ROM Manager and it will make the update.zip for you. FE I just wiped and installed CM10 0822 from 0821 and it didn't wipe out my IMEI. Next I Odined back to JFD and followed the steps on wiki and my IMEI got wiped out again. There is definitely something wiping out the EFS partition when flashing CM10 Nightly from a fresh JVD Odin. I was able to mount and get full permision to the efs partition with an app called called GSII Repair on the play store. After I got efs properly mounted with full rights I copied my good efs folder contents to /efs using ES File Explorer and IMEI has been properly restored and I don't get the IMEI error now. I have attached GSII Repair just in case someone needs help on fixing their corrupted efs partition.
[Vibrant Android Development] Drjjones426:
Ya that was my first attempt at a solution. I ended up just re wiping and flashing all is good now
[Vibrant Android Development] FaultException:
Could you move the backup folder off your sd card onto your computer and then reinstall from stock and see if a backup folder appears, then check to see if replacing your /efs with that backup folder fixes it?
[Vibrant Android Development] hurtz777:
CM10 0822 does properly make an efs backup when flashing. I transferred the files from the efs backup to /efs and IMEI is restored and works great. Do you think it is a line in the updater.sh script wiping out /efs or maybe it has something to do with writeback mode being enabled on /system since this /efs problem didn't seem to show up until the data layout change.
[Vibrant Android Development] GabrielGPP:
Just to confirm, the problem actually occurs when the CM 10 is installed a ROM Stock
[Vibrant Android Development] hurtz777:
That is correct. It appears that /efs gets wiped out when installing CM10 for the first time after a fresh JFD Odin.
[Vibrant Android Development] GabrielGPP:
FE,

You can put the option to take screenshot in the power menu?

And the new boot screen of CM10, will be available soon?
[Vibrant Android Development] deus_:
Find it in

Setting > System > Power menu > "Screenshot"
[Vibrant Android Development] Toast6977:
Or, at any time press volume down and power at the same time for a couple seconds and you should get a screen shot.
[Vibrant Android Development] hooutoo:
Back IMEI message

Need a little help as I'm getting this message about bad IMEI number on startup. I read in previous post about restoring efs from a backup. I ran CWM backup prior to installing CM10 0822. Is that the backup that EFS is being restore from?

Thanks
[Vibrant Android Development] GabrielGPP:
Yes, EFS Backup in /sdcard/backup/efs... use Root Browser or like something to move the backup into EFS folder ...
[Vibrant Android Development] hooutoo:
Gabriel.. you da best! Thanks,

BTW, if you're on Tmob what radio are you using with this Rom?
[Vibrant Android Development] cancrippler:
I'm getting the imei error message as well. However, my phone is working great. I have a Cincinnati Bell Vibrant. I think its a false positive. I backed mine up on cm9 and restored it on Cm10 with same result. I'd prefer not to have the check.
[Vibrant Android Development] fraserwAstro:
Can anyone else confirm that the IMEI wipe is NOT happening from install of CM10 from a NON JFD? Specifically, from CM9?

Thanks
[Vibrant Android Development] FaultException:
It's not a false positive. Your IMEI is 004999010640000 which is a generic IMEI deemed invalid by us in latest CM10 nightlies. If you restored from CM9 then it's also invalid on CM9. If you go back to CM9 and it doesn't pop up the warning, it's because the warning was not present in CM9, but you should go check your IMEI and see if it's still 004999010640000.
[Vibrant Android Development] hendykhanh:
The thread show 4.2.1 and Gapps 4.2.1 but click linkdownload only have 4.1.2 . So that . Anyone think it work both and flash . After .....

I hope tomorrow will have 4.2.1 for vibrant .
[Vibrant Android Development] te_quiero_forever_girl:
"So that . Anyone think it work both and flash . After ..... " <---- wtf is this ??? o.O

Anw he's just updating the thread accordingly as the builds are being compiled. Hold on still :)
[Vibrant Android Development] samsgun357:
If you have apps force closing etc, go to manage apps>all>(app name)>clear cache and reboot.

Would you prefer my usual method of conflict resolution?
[Vibrant Android Development] bill_kevin:
i use the other gapps and no problem, thanks for help
[Vibrant Android Development] TheKing90:
I believe that soon will be released an official 10.1 nightly for our Vibrant :victory:

http://goo.gl/4PFW7 Thanks FaultException!
[Vibrant Android Development] zhuzf:
Message on G+:

CM10.1 nightlies for the Vibrant are a go. codeworkx accepted the pull request to add them today and the first one should show with the next nightly.
[Vibrant Android Development] josh2020glacier:
Man I'm hoping I can have this for a Christmas present lol.
[Vibrant Android Development] zhuzf:
T_T
[Vibrant Android Development] testomat:
Is there a christmas release?
[Vibrant Android Development] akfelipe:
looks like our Christmas present failed compilation. noooooo! :(

http://jenkins.cyanogenmod.com/job/android/

lol it happens: http://jenkins.cyanogenmod.com/job/android/16171/
[Vibrant Android Development] TheKing90:
The first official CM10.1 nightly is out!

Download: http://jenkins.cyanogenmod.com/job/...chive/cm-10.1-20121226-NIGHTLY-vibrantmtd.zip