yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] omnifarious:
No sorry I wasnt able to get it to boot, didnt spend too much time on it. Got stuck in bootloop and had to odin back to stock. Somehow I ended up with the powe reset or unknown power whatever. So ill be trying to fix that problem either tonight or tomorrow.

Sorry all, whish I could have been more help.
[Vibrant Android Development] mistermish2000:
Der dont leave us here. Doug has a point if I9000 can run then vibrant can too... :(
[Vibrant Android Development] cannondaleV2000:
The vibrant will be fixed soon enough be pacient. Stratosk has 4.3 kernel source up so I'll build som stuff on Monday and getting us booting and running good. And I've got in semaphore between 418-431mb ram with camera still working. And its amazing for gameing
[Vibrant Android Development] Dougfresh:
I know SB stopped development on 959 4.3 temporarily because we couldn't get the thing to boot. Crazy stuff that the Vibrant can't boot! PRB is waiting for CM to build it. I know Der whips out working builds eventually.

Peeps should not despair.
[Vibrant Android Development] akarshfrevr:
can anyone say what is the md5sum for latest version?
[Vibrant Android Development] samsgun357:
It must be an issue with tbu.

Also I believe snc74 is using a different ROM with the HB kernel.

sent from the depths of helly bean
[Vibrant Android Development] snc74:
That's right bro', it's the other rom...but with hb kernel (1.2.1) for me this kernel is the best one, imo! And I'm having lock in 25 secs average. In accuracy my best is 19 feet (i think is very good). So i'm keep mixing things up :)

Sent from Darth Vader's tv remote!!
[Vibrant Android Development] chadhoard:
What other ROM?
[Vibrant Android Development] samsgun357:
Slim Bean

sent from the depths of helly bean

---------- Post added at 01:42 PM ---------- Previous post was at 01:35 PM ----------

To each his own my friend! Its great that we have fantastic dev's cranking out fantastic buttery JB ROMs. I personally don't care much about GPS. I would like it to work JIC. Its better to have and not need than need and not have. With that said, I couldn't even get locks with any ICS ROMs so I don't have high expectations with my vibrant and GPS.

sent from the depths of helly bean
[Vibrant Android Development] imilleson:
Formatting dalvik works great for me on 901
[Vibrant Android Development] Dougfresh:
Hmm..Do you get " Optimizing Apps " "1 of xx " during boot? :eek: Pre-ICS roms didn't have this pop-up 4.0 and 4.1 does
[Vibrant Android Development] chadhoard:
Can you give me a link to this kernel?
[Vibrant Android Development] ssjwiggy:
Any other suggestions for this?
[Vibrant Android Development] blazefury:
Try using a root explorer and moving the swiftkey.apk into the system/app folder and set permissions to 644

Sent from my Vibrant in a blaze of fury
[Vibrant Android Development] imilleson:
Yeah I am a regular dalvik cache wiper ;) I usually do it at least once a week. And yes the "Optimizing 1 of 146" always shows up like i expect. I find that letting the system recreate the dalvik cache every so often actually keeps the system healthy - that and regular file system maintenance and permission management.
[Vibrant Android Development] omnifarious:
I didn't do a full wipe either but wiping dalvik cache should do the trick.

Yes, If I wipe dalvik cache in recovery.
[Vibrant Android Development] joroboyvn:
Do you guys know if there is another kernel compatible with hellybean that supports DockSound Redirector app. The app was routing the audio on ICS (for my car docking station) but can't get it working with Jelly Bean.

Thank you!
[Vibrant Android Development] samsgun357:
The 1.2.1 HB kernel was in the ROM a couple of builds back. Do you recall better performance in a previous build? Just seems like a step in the wrong direction.

sent from the depths of helly bean
[Vibrant Android Development] chadhoard:
The way I understood it, he was using that kernel with SlimBean. I was going to switch to SlimBean and that kernel to see if I had better luck with my GPS.
[Vibrant Android Development] Big Dog KMc:
Here are the MD5 sums I come up with from My downloads.

helly_bean_allinone_20120901.zip

34c7571f74beabfefe1e19d30fc8ed94

------------------------------------

helly_bean_allinone_20120904.zip

168604535cf2ec182dc27fb73af442b1

This is the MD5 Summer Program that I use to generate the Sums.

unzip the .exe in windows and run it.
[Vibrant Android Development] omnifarious:
You can also use Hash Tab - http://www.implbits.com/HashTab.aspx
[Vibrant Android Development] Dougfresh:
Cool! I'm going to update to the latest HB :good: I usually wipe dalvik at least once or twice a day lol. I like my phone squeaky clean!

:good:
[Vibrant Android Development] Guitar100:
You do this daily? Interesting. So just wipe dalvik? No reflashing rom or anything else?
[Vibrant Android Development] Globespy:
The GPS saga....

I've been happy back on froyo for the last few months, primarily because my gps works flawlessly - I have hardware fixed gps on my vibrant, so lock to within 10ft usually in under 20 seconds when I'm outside.

I know that the best possible result with ICS was to ensure a lock on phone start up, and for many that meant gps would survive a deep sleep. But still sketchy.

I've been keeping my eye on the JB development (frickin amazing that this aging device just keeps on rocking!), and it would seem that hellybean is the current JB rom of choice.

In the OP, it is stated that "some people have gps issues", but wonder if the gps functionality is more reliable than out was on ics, or if its basically the same deal as before, having to hey a lock as soon as the phone starts, and then hope for the best?

Would love to try it, but only if gps is better than it was in ics.

Thanks.
[Vibrant Android Development] cannondaleV2000:
I think semaphore will work since stratosk has a 4.3 build I'll try building for the vib tomorrow. And have you or anyone talked to fault exception. Looks like he hasn't been on in a while
[Vibrant Android Development] Dougfresh:
Not to FE, but to PR Bass yes.SB might follow on the source tree on CM10.2. Well , not follow but use it. I'm sorta done speaking, for giggles, 4.3 is coming.
[Vibrant Android Development] cannondaleV2000:
+1 its comeong
[Vibrant Android Development] Dougfresh:
Its inframs like Der says. And symlinks also

---------- Post added at 01:43 AM ---------- Previous post was at 01:38 AM ----------

Kernel stuff.
[Vibrant Android Development] Ace42:
And video?
[Vibrant Android Development] DerTeufel1980:
Please try my new build :) I hope this one is booting now
[Vibrant Android Development] cannondaleV2000:
Downloading now!!!
[Vibrant Android Development] DerTeufel1980:
Fingers crossed. I'll be on vacation for two weeks now. I guess if it still isn't booting, it gets fixed by someone else till I am back
[Vibrant Android Development] cannondaleV2000:
If new build doesnt boot. Il build stratosk kernel later today and test that

---------- Post added at 11:03 PM ---------- Previous post was at 11:00 PM ----------

Il be back in school in about 2 weeks so i wont be on nearly as much. Hope i can get a 4.3 kernel out vefore then and il get the vub a few diffrent 4.3 roms once its booting

---------- Post added at 11:24 PM ---------- Previous post was at 11:03 PM ----------

Nope not booting. But il see what i can do later. Jope to see this booting before i go back to school
[Vibrant Android Development] letthebasskick:
Not booting up for me either
[Vibrant Android Development] Cooptx:
Try disabling the ril

That is how the SGS4G got 4.3 to boot until we found a fix
[Vibrant Android Development] edwin270:
Great, but is camcorder working? Love the mackay kernel but gradually falling out with the camcorder thing.
[Vibrant Android Development] cannondaleV2000:
Yeah i changed the mqckay kernel ram settings and it broke camcorder will revert that change in next update. And 480p works at 418mb ram but picture only in 431mb for my senaphore kernel. Il release it after i update to 4.3 and i discovered that 4.3 kernels should be backwords compatible with 4.2 also. But il have to test that more
[Vibrant Android Development] edwin270:
Great direction with the backward compatibility. Looking forward with the release.
[Vibrant Android Development] Cooptx:
On the backwards compatibility I believe you have to disable SELinux or Settings>Security will FC

At least that is what we found on the SGH-T959V
[Vibrant Android Development] cannondaleV2000:
Thanks for the tip
[Vibrant Android Development] apples723:
I cant get this to boot it sat ther for hallf an hour and gave up and restored back to cm 10.1
[Vibrant Android Development] Ace42:
Didn't you read the posts before yours?
[Vibrant Android Development] apples723:
Yes but I thought it was fixed in an update I couldn't find anything after the post from the dev on the latest update
[Vibrant Android Development] Ace42:
It's still being sorted for now.
[Vibrant Android Development] DerTeufel1980:
I was hoping that reverting selinux would fix booting. Unfortunately it doesn't :mad:

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] Alberto96:
Can anyone try if this rom boots with my 4.3/jb3 kernel?

Thanks
[Vibrant Android Development] apples723:
I'm new to the custom ROM and cwm and I just got the vibrant Sunday let's say I do do it how would I get out of a stuck at the boot logo? And how do u flash a kernel? What are the exact steps?
[Vibrant Android Development] Cooptx:
You restore from backup...

You flash it like a ROM...

I am the Potati King!
[Vibrant Android Development] apples723:
just an fyi with the gearkernal this rom still doesnt boot
[Vibrant Android Development] ioancr:
No, it doesn't boot.

I had flashed another launcher, hoping it was a launcher problem, this time it ALMOST booted, it showed up "Upgrading Android" screen and even the "Select home" window, BUT soft rebooted immediately and never booted afterwards.

Another curious thing. The Devil Kernel included in this ROM will boot - WILL BOOT - my own port of Slim 4.3 from GT-I9000, however it breaks cell signal, makes unresponsive home key and won't allow for rebooting to Recovery from Power menu.
[Vibrant Android Development] DerTeufel1980:
You should try taking a logcat if you are able to connect by adb. Also make sure to try with a clean install, with formated system before install, and wipe data after install.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] Linkmeup82:
I think this may be the end of my Vibrant flashing days. If I had only read the forum prior to flashing and created a backup. How could I be so wreckless? I know better than that. I'm stuck at the boot screen but I can get into recovery. No ROM I flash will boot. I guess because of the partition swap. I normally just Odin back to a factory image but now my PC doesn't see my Vibrant and Odin doesn't see it when I have it in download mode. Odin still sees my S4 and they use the same driver. I have an issue with the charger port that requires the cable to be attached a certain way to get the phone to charge. I can get it to charge while off when it is connected to the PC but doesn't see the phone. Sorry to blow up your thread. I've been an avid devil user for over a year and haven't had an issue like this. I tried glitch as well to fix. If anyone can assist , please PM me if there is a way to recover the device after a partition swap when Odin doesn't see it. Thanks.
[Vibrant Android Development] apples723:
I'm new the vibrant family but I had some probs yesterday with my imei not be reconised my device but couldn't get Odin to detect my device so I did some research and found Heimdall Suite witch you can try flashing your device with it different then odin and more often than not if has always seen all my devices as on windows 8 odin doesn't see it but any way you can find instruction here http://www.glassechidna.com.au/products/heimdall/ download for heimdall here http://d-h.st/bbq and the stock image here http://d-h.st/M93 this is just a suggestion as it got my device working yesterday no guaranties
[Vibrant Android Development] Ace42:
How anyone can stand W8 is beyond me, but I digress.

Do you have access to any W7 machines? Odin works fine under 7, haven't attempted it on my 8 partition.
[Vibrant Android Development] Linkmeup82:
I use Windows 7 Ultimate on 3 machines all 64bit. I think he was simply giving an example using Windows 8. 8 is awesome in my opinion but that is neither here nor there. Odin is confirmed working on 7 and that's what I'm using. I'll try it on a different machine when I get home. If that doesn't work, I'll try Heimdall. Thanks guys.
[Vibrant Android Development] apples723:
Windows 8 came preinstalled on my computer but i do have a windows 7 virtual machine but hemidall in my opinion is better. I always get a lib something something error when using a pit on heimdallbut that's another story but oh well.

I hope u get or device up and running let me know if u do. Best of luck apples
[Vibrant Android Development] Linkmeup82:
Thanks apples. I think your good graces did the trick. My Vibrant is booting! I swear to God I did this multiple times last night to no avail but this is how I fixed it without using a PC. I flashed HellyBean 8/18/13 release and it errored as usual and said repeat the process to confirm due to the data loss from partition swap. I flashed it again and then it for some reason went back into Clockworkmod recovery. From there I flashed CM 10.1 RC and it booted up. Then I flashed CM10.1.2 and everything is working fine. I think the trick was not wiping. That was the only thing I did differently this time. I still can NOT get the phone to show up on any computer. There is not even an option in the notification panel or status bar on the phone to mount as storage. The phone will charge while connected to a PC though. I'm using the stock usb cable and my S4's usb cable. I think because the port has a bad connection from age is the cause. I'm going to try to repair it. Believe me I have created a nandroid backup to avoid this. Disaster averted.
[Vibrant Android Development] smokey155193:
To get into recovery try this if you have gingerbread bootloader.

remove the battery. attach phone to PC via USB cable while Odin running. press the volume down button (recovery) or volume up (bootloader). keep it pressed continuously. don't press any other button like power button. now slide in battery and wait for few seconds. it will boot into recovery or download mode.

for froyo bootloaders press both volume up and down buttons.

third method is to use home made jig. attach 301k (exactly) resistance between terminal 4 & 5 of micro usb. power off phone by removing battery. plug in battery after 2 minutes. without pressing any button insert jig and wait for getting into download mode. I hope this will help you.
[Vibrant Android Development] freshjr:
Derteufel do you know what the last version of hellybean was that still used devil

kernel?

Devil allows me to change my mic volume making calls sound a lot better.

I know 2011-11-15 all in one had devil kernel and manager included but that one gives me screen wake problems.

The recent ones have options for mic control but the options do not work.
[Vibrant Android Development] tsatomas:
[MENTION=3899860]Linkmeup82[/MENTION]

Just in case make sure that you have not enable somehow fast charge because this broke the USB connection.
[Vibrant Android Development] DerTeufel1980:
All version are using devil kernel.

I'll look into the mic volume and also boot issue (of 4.3) when I am back from vacation in 1.5 week

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] Linkmeup82:
I'm pretty familiar with Odin and ADB. I have gingerbread bootloaders and can get the phone into download mode by holding volume up and power. I got an S4 and let a friend borrow the Vibrant. When I got the Vibrant back the usb port seems to be wallowed out a little bigger so my usb cable is lose in there and I have to lay the phone down a certain way for it to charge. The problem is that the phone never shows up on the any of my 3 PCs or my roomate's PC. My S4 does and my GF's Fascinate (Verizon S1) shows up. My roomate's Galaxy Nexus and my Nexus 7 all show up. I believe it is the usb port on the phone. It is old and seems to only be charging the phone now. Thanks.

---------- Post added at 09:39 AM ---------- Previous post was at 09:34 AM ----------

The device never booted originally for me to enable fast charge. I was stuck in recovery. If I had been able to actually boot into Android to enable the feature, I would have made sure it was disabled since I am clear on how fast charge works. Booting now using CM10.1.2 (there is no fast charge) and PC still doesn't see it. Thanks though.
[Vibrant Android Development] omnifarious:
Could also be the cable and driver combo.
[Vibrant Android Development] roberton:
ugrade from 7/23 to 8/16 built was ok.. no problems at all... but today i did turn the GPS on and my vibrant restarted by it self in a bootloop....
[Vibrant Android Development] apples723:
how did you get it to boot i tried the 8/16 build but i got it to boot to updating apps but then it rebooted and still is i have a back up to get out of the boot loop but i want 4.3 so bad :)
[Vibrant Android Development] roberton:
i did nothing, i just installed when i saw the 8/16 update, it worked fine.. i did not know the problems of bootloop until i tried the 8/18 build.. but i didnt installed as it told me that will delete my data partition... so i get back to the forum and realize that the bootloop..

today i restored angrygps from a titanium backup and as soon as i run it and activate the gps, the phone restart it going to the never ending hellybean logo..

i restore only boot from my 7/23 cw backup and it boot and start to upgreade the apps (X from XXX) but it get loop on the starting app message...

I need the data from my 8/16 backup that i made after the bootloop (from gps start) so i been playing with backups but cant make it work

i did restore my 7/23 cw whole backup, and all fine... if i restore my 8/16 cw data backup over this i got a bootloop

if i restore the 8/16 cw backp and restore the 7/23 cw boot backup over, it get pass the hellybean logo and start to update the apps again but get stuck on the stating apps msg.....
[Vibrant Android Development] Cooptx:
Does this mean that GPS is the issue? By any chance was your GPS off when you updated to 4.3 and was it off when you booted?
[Vibrant Android Development] apples723:
ill try that now to see if it makes a diffrence
[Vibrant Android Development] DerTeufel1980:
Please take a logcat of the bootloop. I don't own a vibrant, and instead of blind guessing, this is a good chance to get it booting

Btw: if you made the backup after you got into bootloop, you'll always restore the bootloop state.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] roberton:
my GPS is most of time off, been off for a couple of month, it was off during the upgrade from 7/23 to 8/16.. dont know if that was the issue or the installation of angrygps
[Vibrant Android Development] Cooptx:
GPS would be the issue then because others tried without it booting once. And as far as I know, GPS is on by default

I am the Potati King!
[Vibrant Android Development] roberton:
correct, my backup restore thre bootloop state, how can i get the logcat of the bootloop? im kind of newbie
[Vibrant Android Development] apples723:
i installed inframus and it installed twrp recover and wont flash any zip help please

---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------

how do you compile and build roms then if you dont own a device
[Vibrant Android Development] DerTeufel1980:
You need to install adb (android development bridge) on your pc. (please use Google to get this)

Then connect your device to your pc, open a terminal/command line window and type:

adb shell

logcat > sdcard/logcat.txt

Then upload the logcat.txt

I own a i9000, it's almost identical

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] apples723:
twrp wont flash anyroms and my computer isnt detecting my device how do i fix this
[Vibrant Android Development] DerTeufel1980:
You need to install nexus s usb drivers, if you didn't already

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] roberton:
before connect the device to my pc:

do i have to restore the 7/23 cw backup first to have the phone working

or do i need to 8/16 cw backup with the bootloop state (dont know if i can connect the device to my pc with the boot loop state)
[Vibrant Android Development] apples723:
why would i install nexus s usb drivers i flashed like tuesday night from my computer fine
[Vibrant Android Development] DerTeufel1980:
It doesn't matter. But we want to log the bootloop, hence the 8/16 build.

What rom did you have installed at this point? Aosp based ones need nexus s driver

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] apples723:
infamous and i cant the nexus s driver
[Vibrant Android Development] Dougfresh:
Yo, Apples. You are really spamming these DEVELOPMENT THREADS! You need to stop man.

When I was a Noob, I searched and searched and broke my head until I learned the basics. I never asked just learned. I'm not bashing yet but read up like Jrongi told ya yesterday. ;)

---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------

Nexus S drivers work excellent on the Vibrant
[Vibrant Android Development] samsgun357:
I don't know who you are doug fresh but I imagine you hang in Ybor. How you like them apples? Oohh Billy......

Eat Play Google
[Vibrant Android Development] Dougfresh:
I'm going to report you to the Mod-Father and your done broski! Axed!!!!!!!!! Lol!
[Vibrant Android Development] roberton:
cant get the logcat from my device..

if connected from the cw recovery menu i got a not found error:

sdk\platform-tools>adb devices

List of devices attached

33355DC5048B00EC recovery

\sdk\platform-tools>adb shell

~ # logcat > logcat.txt

logcat > logcat.txt

/sbin/sh: logcat: not found

if connected once the hellybean logo appears (bootloop) cant get to the shell:

\sdk\platform-tools>adb devices

List of devices attached

33355DC5048B00EC unauthorized

\sdk\platform-tools>adb shell

error: device unauthorized. Please check the confirmation dialog on your device.

---------- Post added at 02:37 AM ---------- Previous post was at 01:56 AM ----------

found logcat at sbin, and got this from the 8/16 cw backup restored today after the bootloop:

--------- beginning of /dev/log/main

I/ARMAssembler( 131): generated scanline__00000077:03545404_00000A02_00000000 [ 30 ipp] (52 ins) at [0x40ded1f0:0x40ded2c0] in 148208 ns

I/ARMAssembler( 131): generated scanline__00000077:03545404_00000A08_00000000 [ 30 ipp] (52 ins) at [0x40ded2d0:0x40ded3a0] in 100499 ns

I/ARMAssembler( 131): generated scanline__00000077:03545404_00000000_00000000 [ 29 ipp] (43 ins) at [0x40ded3b0:0x40ded45c] in 95208 ns
[Vibrant Android Development] DerTeufel1980:
Thanks. It's useless taking it from the recovery :(

Now it's getting more complicated.

While in recovery, ensure /data is mounted, then connect again by

adb shell

Then, from the terminal in your pc:

echo 3 > /data/property/persist.sys.root_access

Then reboot and try again the logcat commands

adb shell

logcat > sdcard/logcat.txt

Edit: please also try, if it boots up again, after restore of your backup, followed by a data wipe

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] edwin270:
Sure, and to clarify things about the Windows 8, I use it everyday for all my works and sure it has driver compatibly issues but not for Samsung.

But in a situation where u have issues check the device manager, things like "gadget serial.." showing when the device is connected means you have a wrong driver installed.

Another thing to note: Windows 8,has driver signing turned on and must be turned off if installing drivers especially unsigned ones,... But then the drivers can be extracted using 7zip and installed using the "driver update" method of install