yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] wkim02:
If there is anything I can do to help with the GPS let me know. I tested the gps with the original kernel for V13 and the new V13.boot3 kernel after deep sleep. Both get accuracy up to about 6-7 meters.

I haven't had any issues with gps since Neo got it working on passion. Also, I did not do a factory reset coming from v12, just cache and dalvik.

If you want screen shots let me know. I see all the people with issues on here and the facebook page.

---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------

You should be able to add Icons to the dock by long pressing the icon in the app drawer and when it goes to the home screens just add it to the dock.

As for scroll, not sure what you are looking for but maybe you can try the window and transition settings under developers options. Once again, not sure if that is what you are talking about though.
[Vibrant Android Development] Jon Po:
post link

Can you post the link for v13 boot 2? I only found boot 3.
[Vibrant Android Development] mveksler:
I just dont get it. How is it two people having GPS working on v13 kernels and others can not get it to work.

I did clean install following the OP. I tried both v13 boot2 and boot3.

The boot2 dies after deep sleep, boot3 after deep sleep seams to wake-up but not completely, the GPS icon starts flashing like it is obtaining lock but no PRNs are showing up in AngryGPS and no sats in view. I tried chnaging the governor from ONDEMAND to SMATRTASSIOANv2 and setting CPU speed to 200-1200 with no luck.
[Vibrant Android Development] VibrantThemer:
Where are you guys getting boot 2 and 3 from? Would you mind post a link.

Thanks
[Vibrant Android Development] robertd0619:
Yes sir GPS still works after deep sleep.

Just tested it again.
[Vibrant Android Development] davidgs:
I'm having the same problem when using the speaker during a call, the other end hear a lot of noise and themselves talking as echo.
[Vibrant Android Development] fscussel:
1) yeah but when I release the icon over the dock it doesnt works, doesnt apply there...

2) yeah I mean, when you do that movement to scroll stuff like the contacts, in froyo one single fast movement would make the list scroll till the end, now in this ICS it just stops after a few inches of movement?
[Vibrant Android Development] wkim02:
Maybe try clearing the cache for the launcher... I just tried it again and works for me.

As for the scroll, I don't think there is an option to change that.

---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------

Here is the link for the boot3 kernel:

http://www.mediafire.com/?lde372gllmy1b

Also, Nelson just posted a cleanup zip with the latest kernel as well. (I haven't tried this one) He said it should clean up some uneeded stuff to free up some room from the rom and hopefully make things work for those with issues.

http://www.mediafire.com/?1zuhd9dbzapr885
[Vibrant Android Development] Jon Po:
boot 2

Does anyone have a link for boot2.zip?
[Vibrant Android Development] michaelh99:
Unrelated question...

How did you get battery meter text working? I can choose that setting all I want and just get normal no-text meter.
[Vibrant Android Development] davidgs:
See post #9605

http://xdaforums.com/showpost.php?p=22341464&postcount=9605
[Vibrant Android Development] wkim02:
That is probably the battery mod by MP found here: http://xdaforums.com/showthread.php?t=1421876

I dont' think the options in the settings are working yet.

Also if anyone still needs boot2 here is the link:

http://www.mediafire.com/?hwbwoo7clax83na
[Vibrant Android Development] Raistline:
Small note, in case this helps anyone.

For the longest time (since ICS) I have been having issues using Titanium backup to backup my largest games. For example, Windup Knight.

I recently got sick of taking lots of time to move my installs to Internal SD and decided to try adding the .nodatadata file to the datadata folder. Once I did this my titanium backup was faster and I am once again able to restore all my backups.

I do have over 150 user apps in case anyone is wondering.
[Vibrant Android Development] fscussel:
how to clean that cache?

also, what happens if I restore my froyo (bionix v2) system data from a titanium backup into ICS?
[Vibrant Android Development] bobshute:
crash and burn.
[Vibrant Android Development] Jon Po:
Sweet, thanks for the link.
[Vibrant Android Development] wkim02:
You can find Trebuchet in titanium and try clearing data... Maybe even go into recovery and just clear cache and dalik cache and then fix permissions (this should not wipe any apps you have installed) ... If all else fails then reflash the rom and see if that fixes it.

And as posted above, do not restore system data... For one the systems data is different from froyo and ics... and they also differ between roms and only cause problems if restored.
[Vibrant Android Development] TFordham:
I've mentioned that I'm not much of a GPS person, but just flashed this cleaned up kernal. Had 12 birds in view in a few second and down to 19 feet not long after that. Good job Nelson.
[Vibrant Android Development] fscussel:
this damn Titanium backup is so idiot because it lacks a call logs and sms backup utility, now I will have to flash back to my froyo rom nandroid just to take those data... lots of work damnit
[Vibrant Android Development] christpuncher:
new to the ics and loving it. two things. everytime i go to type something a notification appears regarding my default keyboard. how do i get rid of that? i scoured every setting with no luck. and secondly, i'm seeming to have a sporadic issue of when i hit power and go to the lock screen, the screen doesn't register my touch. i'm kinda having to just lock and unlock it until it works.
[Vibrant Android Development] wkim02:
If I'm thinking about the same notification you are, there is no way to get rid of that except maybe remove all other keyboards. In ics that notification is the way to change the keyboard instead of long pressing the text field now.

As for the unresponsive touch, try setting your cpu min to either 200 or 400.

Also, for anyone who wants to see here are screens of my GPS and DS. First is the initial lock and the second is after getting a closer accuracy about 30 or so seconds from the initial lock.
[Vibrant Android Development] christpuncher:
the no touch issue seems to be related to the wifi being on. i turned it off and it isn't happening now. weird.
[Vibrant Android Development] uhs74:
here with new kernel means? - does v13 contains new kernel or need to install separably?

ICS_Passion_v13_RC1.zip ( v13 file)

ICS_Passion_v13_boot3.zip ( not sure on this)
[Vibrant Android Development] robertd0619:
Sorry bout that. I'm using ICS_Passion_v13_boot2. Everything is working great on my setup right now. I don't see a need YET to flash boot3 or the CLEANUP one. I'll see how it goes for the mean time.
[Vibrant Android Development] Smartassassin:
you could get call logs and SMS backup from the market

Sent from my phone, not yours.
[Vibrant Android Development] scaldaferri:
Same here. :(

Regards

Andre
[Vibrant Android Development] closedcircuit:
With v13rc1 stock kernel I didn't get GPS after deep sleep, but after flashing ICS_Passion_v13_boot3.zip then ICS_Passion_v13_cleanup.zip my GPS works just like v11b5 3.0.8. But I am still getting the same issues when the phone is set to speakerphone and the mic has way too high of a gain. I can completely cover up the mic with my thumb and that actually fixes the problem. When I don't cover up the mic the gain is so high that I can hear background noise of a finger tap on a table over 35 feet away. It seems to me like a fix could be running a script for us to manually adjust the mic gain settings. But with the mic settings as is set up so high the speakerphone function is completely unusable. On another note the call quality, when not in speakerphone, on the v13.boot3 kernel is much much better than any of the v12 kernels.
[Vibrant Android Development] lonepie:
I got heavy duty screen distortions (like horizontal lines cutting in and out of everything, very hard to explain - made me think the screen was broken) with this ROM. I switched to ICSSGS RC4.2 and the distortions went away.

I have a feeling it has something to do with the Kernel, since the problem first appears like so:

Vibrant Logo when phone is turned on looks normal for a few seconds, then it the screen distortion kicks in, and you can see the lines around the edges of the word "Vibrant" and the smaller text below.

Hope this helps. Let me know if you need any additional info.
[Vibrant Android Development] renegadedj:
You've got a case of the rainbows dude. Didn't install GB bootloaders or flash from cm7 at some point im guessing.
[Vibrant Android Development] BoomBoomPOW:
After flashing the new kernel boot2/3 cleanup, my NSTools app stopped working (it wouldnt open all the way, just stalls when superuser is supposed to give it permission; same goes with Rom Manager app).
[Vibrant Android Development] mveksler:
How did you flash? Cleanup first reboot then new kernel?

I tried installing new kernel boot3 and then flashing cleanup right after it then reboot and still no GPS after deep sleep. After reboot tried flashing cleanup again and still no good.
[Vibrant Android Development] m4r10:
Someone posted this earlier:

open the voodoo control app and un-select the "tune speakers for music" box. Don't know if it works or not yet.
[Vibrant Android Development] CM Wave:
Boot2? Boot3? What are you guys talking about?
[Vibrant Android Development] mveksler:
There were two v13 kernel versions released after v13.RC1 was released because the download did not include v13 kernel.

So there are two variants v13.boot2 and v13.boot3
[Vibrant Android Development] showson1:
No data connection

Hi all.

I'm having an issue where my data connection will suddenly drop.

It happens almost every time when turning off Wifi, but just at different times otherwise.

I've tried totally wiping and installing v13 RC 1 fresh and this just started happening maybe a week ago on v12.. never saw it before then.

Sometimes the bars will stay green, but I won't be able to connect.

Other times they will be grey and I have to reboot (sometimes several times) in order to get it to work.

I haven't changed my modem or anything, so I don't have any idea what's going on.

If anyone has any suggestions I'd really appreciate it.

Thanks!
[Vibrant Android Development] CM Wave:
You'd think this sort of information would be in the OP, no?
[Vibrant Android Development] rajush:
screen lock & key press sound

the "screen lock sound", "touch sounds" and "sound on key press" for keyboard is not working in v13. Is anyone having the same problem? And I have already flashed it twice.
[Vibrant Android Development] papi5120:
Same here....but its more like the volume is so low its almost muted
[Vibrant Android Development] wkim02:
Those are test kernels that are being released on the facebook group and then shared over here. Neo is discussing to see if Nelson should start a new thread on xda for his test kernels. If you haven't already, I would join the facebook group for the latest info and releases (although I know some people here have already stated that they refuse to go on facebook).
[Vibrant Android Development] dasunsrule32:
Tell Neo to go Google+, I'll be there ;)
[Vibrant Android Development] closedcircuit:
This was my install path.

v11 -> v12 -> v11b5 3.0.8 Kernel -> ICS_Passion_blue_b8_with_Nova Kernel -> v11b5 3.0.8 Kernel -> v12 -> v11b5 3.0.8 Kernel -> v13r1 -> Full Wipe -> v13r1 -> boot3 -> Reboot -> cleanup.

It is turned off, and has been for a while. I tried to turn it on to see if it made a difference, and it didn't. The speakerphone mic settings are still way too high.
[Vibrant Android Development] mveksler:
I will try this sequence: v13r1 -> boot3 -> Reboot -> cleanup.

However I have no hope. I been flashing cleaning re-flashing cleaning dalvik etc all day and nothing would get GPS going but v11b5.
[Vibrant Android Development] closedcircuit:
One thing I forgot to mention, after flashing over to v13r1 my GPS settings somehow got changed from msbased to standalone. I changed it back to msbased and I got a lock right away.
[Vibrant Android Development] Jon Po:
Same here

I have tried the 3 latest kernels and have had no luck with GPS waking up after deep sleep. No complaints here just thought I would let people know as well. At first it locked on super fast I then turned GPS on and off a few times and everything worked. It's just when it enters sleep mode it shuts off the GPS with no way of turning it back on without a reboot. I see no need to keep posting the same GPS issues that are obvious to us all. Just wondering if there were anymore kernels to try out. I don't do facebook, not my cup of tea.
[Vibrant Android Development] mveksler:
It always have been on STANDALONE on Passion and it has been working with STANDALONE since v11b5 with 3.0.8 but non of the new kernel can restore GPS functionality after deep sleep.
[Vibrant Android Development] shdw03:
just a question regarding signal....

Never really noticed, but I have a "R" by my signal bar and not a "H". Why am I roaming?

in About Phone>status

Network: T-Mobile

Mobile Network: HSDPA:9

Service State: In Service

Roaming: Roaming?
[Vibrant Android Development] phenom69:
I'm on v13 RC1 and flashed Nelson's clean up zip and now EVERYTHING is working great, GPS is accurate and finally the mute bug is gone. Great Rom
[Vibrant Android Development] snapple232:
Does anyone else have an issue where the battery will sometimes drain quickly and sometimes barely drain at all? Yesterday after I flashed v13, it lost only 5% in 8 hours. Today it's losing 2-3% an hour. CPU Spy says it's still in deep sleep, and "Android OS" is using the most battery. Wifi, GPS etc are all off.
[Vibrant Android Development] ferret007:
Does that include gps after deep sleep?
[Vibrant Android Development] mveksler:
I gave up on v13 kernels + clean up.

I had been testing this all day in different combinations and nothing i do will restore GPS after deep sleep.Going back to v11b5 3.0.8 until more stable kernel is available or someone can tell me exact reproducible steps not just one time luck to get GPS going on new kernel.
[Vibrant Android Development] anorris666:
snapple232 - Do you have USB Debugging enabled? Just curious. When that happened once to me, it coincided with me turning off debugging....
[Vibrant Android Development] dasunsrule32:
At least you get deep sleep. :) I've done a complete wipe, flash of v13 and tried the v13 boot2 and 3, also tried the cleanup. No bueno. Phone won't sleep.

And of course, as soon as I write this, I fix it. ;)
[Vibrant Android Development] mveksler:
In regard to phone not sleeping it is kind of strange. Maybe you have some apps that are preventing sleep? Have you done next: CWM->mound/format system->factory reset->install v13->reboot->wait 5 min->CWM->advanced/clean dalvik/fix permissions->clean cach partition->reboot. If Google Bakcup restored your settings, go to CWM->factory reset.

Try this might help.
[Vibrant Android Development] closedcircuit:
Use BetterBatteryStats and take a look at what is causing your wakelocks. If it happens to be an alarm causing your wakelock, then you need to either connect your phone to a computer and run this:

adb shell dumpsys alarm > AlarmDump.txt

or run the code below with a script manager:

cd /sdcard
dumpsys alarm > AlarmDump.txt
[Vibrant Android Development] snapple232:
Hmm I may have done that, don't remember exactly. Gonna try turning it on again to see what happens.
[Vibrant Android Development] woofiegrrl:
Hooray, thank you so much for this! I don't suppose removing .nodatadata reverses it, though? Ah well, I don't expect I'd need to do that!

And a reminder for those of you posting your GPS info...I know where you live...maybe blur that out if you're paranoid. ;)

Oh, and one question - why does turning off Pulse notification light never ever stick?? :)
[Vibrant Android Development] ameedi600:
This rom gets better and better, I still remember how it was when it first began. Good times, good times lol :-)
[Vibrant Android Development] TFordham:
I have no idea what happened. This morning, v13 was working perfectly. I got busy at work, so didn't really look at the phone for a good part of the day. Got back on it in the evening and it was totally ****ed up.

Lost root. Random reboots. Apps acting funny.

Odining right now and starting the whole process over again. This sucks, but I hope I'm the only one this is happening to.
[Vibrant Android Development] d3adbroke:
I'm just gonna stay on v12 for awhile
[Vibrant Android Development] Burner2K0:
I'm using the included kernel with v13 and not the new one and GPS works even after deep sleep as you can see. Loving it! :-D
[Vibrant Android Development] uhs74:
i just installed v13 - now fr me it is not working at all.

what are steps u have tried?
[Vibrant Android Development] TheContinental:
Massive kudos to Neobuddy and his development partners. This is one buttery-smooth ROM. No lag, super-fast. I didn't use any other kernels--just installed V13 RC1 as-is. From V12 Beta, wiped and formatted first. No battery mods, Voodoo or DSP sound settings, or CPU changes from stock.

Everything's perfect so far. The phone is faster than when it was new. GPS works better than new, and locks faster. The phone also sleeps with GPS on, even after running a GPS app. Can't comment on the mute/unmute, but my money's on Neo--I'm sure he fixed it.

Thanks for making our Vibrants more futuristic than most of the new phones. You deserve every donation you get, including one from me.
[Vibrant Android Development] Woody:
Haha put those coordinates into Google Maps and bam!!! You got a picture of their home.
[Vibrant Android Development] uhs74:
do u have samsung vibrant tmo usa version?

i did same thing but no luck- i had v12 and move to v13
[Vibrant Android Development] RaymondPJR:
Passion

That was a new feature in Gingerbread, if I am correct. It was changed to deliberately scroll a few inches, then stop.

---------- Post added at 07:54 PM ---------- Previous post was at 07:33 PM ----------

Wrong, wrong, wrong! I an never really concerned about the call logs, but I do care about my sms/mms. This is what I aways restore with Titanium, and I always get my sms back, (I know everyone says it doesn't work, but I'm looking at them, so I don't care). Also I just did a full wipe, and flashed Doc Master's last night. I have my logs going back to January 21st which was just about the time I got Jarmez Hack ICS to flash for the first time.

In Titanium: [CONTACTS/CAL...111230.XXXXX, [SMS/MMS PREF...111220.XXXX, and [SMS/MMS/APN] ...120126.XXXX.

I definitely proved that the last setting restores my SMS, I was never sure if just that or some combo of the three did it. But this last time I did the first, reboot, checked, the second, reboot, checked, the third, reboot, checked and my SMS were there!:cool:

EDIT: Need to say also that it is safe to restore even across OS Systems, e.g. going from Froyo to ICS. Yes, it is a restore of data, but it's just one thing.
[Vibrant Android Development] bobshute:
I restore that all the time. But it didn't work going from froyo to ics.
[Vibrant Android Development] RaymondPJR:
Passion

It worked for me moving from Gingerbread to ICS, so I assumed it would work coming from Froyo too. Next time I flash, I'll restore one of the really old backups just to test again. I have TB set to store 15.:cool:
[Vibrant Android Development] Woody:
That third one you mention SMS/mms / apn will also help with if you somehow lose your data connection. Many times have I had my apns disappear on me when ROM jumping.
[Vibrant Android Development] Burner2K0:
I didn't do anything special. Formatted data wiped and all that good stuff then flashed v13 on top of v12.
[Vibrant Android Development] aldoit01:
I been searching all over with no luck can someone plz link Me to nelsons Facebook or wherever he posts
[Vibrant Android Development] snapple232:
The first time I flashed this I didn't do a full wipe properly, and got slight lag. Wiped correctly this time and the rom really is amazingly smooth. When I compare it to the laggy stock froyo I was running for almost a year before I started trying custom roms, it's just embarrassing (for T-mobile and Samsung).
[Vibrant Android Development] Dattack:
look at first post. Right of neobuddy's signature.
[Vibrant Android Development] t1h5ta3:
pulled right from the OP : http://www.facebook.com/groups/308078452559685

:rolleyes:
[Vibrant Android Development] ajvasudhar:
v13 with new clean kernel from Nelson

Everything works fine, as good as the previous builds.

I did a complete wipe and flashed v13, then restored the apps, after which did a dalvik cache/cache wipe and installed the new kernel.

Initially the system was slow, but later fixing permissions did the trick.

Noted one weird bug, when Auto-rotation is disabled, the default mode seems to be the landscape mode, (when i disabled the auto-rotation the first time, it was in landscape mode).

GPS I did get a lock, but not as stable as v11.5
[Vibrant Android Development] l3oykute:
I have an issue in v13 - RC1, when i change the Image size in camera (5MP, 4MP, ...) it will FC!Have any suggest!??
[Vibrant Android Development] VibrantThemer:
You cannot just change the image size. The image size has to be exact. And you need to use apk tool or pak manager to de-compile the original apk and re-compile again before you can use the new apk.
[Vibrant Android Development] oblib__:
I was watching logcat while booting and noticed an error in one of the init.d scripts, S4nbconV7. Line 332 if missing the 'i' in if, which causes the script to abort.

When that's fixed, there's a mount command that causes a seg fault:

mount -o remount,noatime,nodiratime,discard,barrier=0,delalloc,noauto_da_alloc,commit=60,data=writeback,rw auto /data

I'm not sure what it's supposed to do, and don't know why it crashed, but FYI.
[Vibrant Android Development] kamparperak:
I like everything in the OP, especially:

Disclaimer:

We are not responsible for anything happens to your device.

You may install this at your own risk and slap T-Mobile and Samsung Crew for abandoning our devices.:D:D
[Vibrant Android Development] ferhanmm:
Is there a reason it's set to 200-1000mhz?

Can i bump it down to 100-1000?
[Vibrant Android Development] noCOMPLY:
On v12 my headphone mic button would work for pausing music and answering calls. Now on v13 it doesn't.

Anyone else having this issue?
[Vibrant Android Development] veol:
Getting the mute/unmute issue

I am still getting the mute/unmute problem on V13 :(

Has there been a fix for this? I heard that maybe flashing a different modem may fix it. Anyone know which one?
[Vibrant Android Development] SAI Peregrinus:
No, the test I do (in my region, yours may vary) is to call 911 and say "This is a non-emergency test call." when the PSAP operator answers. It is calling 911.
[Vibrant Android Development] mikeye9:
You're not alone.
[Vibrant Android Development] SAI Peregrinus:
V13r1 has this problem. v13 boot3 fixes it.

Also, the minimum CPU frequency is at 200mhz because there is some instability when it gets set to 100. You can try setting it lower, but you may end up with "black screen of death" where the phone won't unlock. Rebooting fixes it, but it's annoying enough to warrant setting the min frequency higher.
[Vibrant Android Development] WallaceLau:
GPS

Just flashed 13r1 and tested GPS immediately, noticed something strange... AngryGPS could never get a lock (time out), and after setting t/o to 0 and let it sit for a while, AngryGPS is now saying I have 21 sat in-view? Is that even possible? Or did something fried my GPS receiver? Never seen this before and although I have problems with GPS not recovering after sleep, I've always been able to get a lock within 60-80 seconds. This is a first to me...

Flash history as follow:

Stock -> CM7 -> MIUI -> Stock -> v12 -> ICSSGS RC4.1 -> full wipe (system, dalvik etc) -> v13.rc1 -> reboot -> boot3 -> cleanup -> reboot

Thanks!

W.