yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ioancr:
Strange thing, I could get a working port from GT-I9000, using the same kernel as our vibrant build. No changes to the ROM, except those device specific (deleted the "assert" lines in update script, replaced keylayout files etc). AND wiped Data again AFTER flashing (as Der suggested)

Problems found:

- Unknown baseband/No imei/Erased efs

- Superuser not working properly. After a few installs won't allow root access

- WiFi won't turn on

Changing kernel (to Gear JB3) and problems persist.

PS I don't have a dedicated PC to provide a logcat. Sorry :(
[Vibrant Android Development] DerTeufel1980:
Missing baseband is caused by vibrant using Froyo ril.

SuperUser is working after going into development settings and switching superuser to app+adb

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] Linkmeup82:
So I shouldn't use the stock cable? I'm also using a new S4 cable, Nexus 7 cable, and Samsung Galaxy cable. My GFs Verizon S1 shows up and so does all other devices. I have the correct cables and drivers installed obviously or how else would her phone that uses the same driver and similar cable be able to show up? It's definitely not but good guess.
[Vibrant Android Development] tsatomas:
I suggest to download kies or Samsung drivers again to check, may be there is a slight different driver for other phones, the cables normally works ( I use Nokia!) Between phones.

The other obvious solution is to use a card reader to put files in phone exsdcard.
[Vibrant Android Development] roberton:
not sure what im doing wrong first restore my 8/16 build cw backup with the bootloop state, mount data partition at recovery, but after the adb shell command echo 3 > /data/property/persist.sys.root_access and reboot i still not able to get adb shell to work on the bootloop (only at recovery)

same happened if i wipe cache and devilk cache after echo 3 > /data/property/persist.sys.root_access and reboot (used reboot to bootloader from cw advance menu)... i get pass the hellybean logo and start the optimizing apps .. then android is upgrading... stuck at starting apps... but cant get the adb shell to work to continue with the logcat:

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.

after the wipe data im still stuck at the android is upgrading... starting apps. message.. the only difference that before now is that i cant connect to the abd as there is none device in the device list... the usb drivers change to a usb mass storage and 2 disk Linux File-CD Gadget USB Device.... still get adb connection on recovery...
[Vibrant Android Development] DerTeufel1980:
The message seems to be caused by a security feature. One would need to recompile the kernel or at least modify and repack the initramfs.

I think the default.prop needs to be changed to have ro.secure=0 instead of the value 1. I can't do this before Friday, because I am on vacation without a pc.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] apples723:
looking forward to the point when we get this to boot!
[Vibrant Android Development] omnifarious:
No worries der. We are all patiently waiting and anticipate your safe arrival. =]
[Vibrant Android Development] apples723:
+1
[Vibrant Android Development] netss:
hey. anyone can tell me, what is the mark quadrant score them with the latest rom?
[Vibrant Android Development] roberton:
just recover app data that i have from the 8/16 build and applied to my 7/23 restore... but by accident i deleted the 8/16 cw backup with the bootloop state.

so i restore my 7/23 cw backup.. then i upgrade to the 8/16 build and everything goes fine (did upgrade and wipe cache and devilk before reboot system), boot ok.. no bootloop as i did before when 8/16 build came out...

did a reboot just to confirm that no bootloop was no present.. everything fine again.. running 8/16 with android 4.3

as soon as i turn the GPS on as before, the phone reboot in a bootloop
[Vibrant Android Development] Cooptx:
Looking forward to the point when you finally decide to stop spamming and maybe read some stuff and do something constructive.

I am the Potati King!
[Vibrant Android Development] letthebasskick:
i ported the slim rom from the captivate to our vibrant and as far as i can tell everything works

i used the new 4.3 gearkernel
[Vibrant Android Development] DerTeufel1980:
Can you attach a screenshot, showing

4.3 please :)

Seems like a GPS issue. Does it work? My Kernel should be fine, too. Can you please try it?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] roberton:
I took screenshot of it but did not put it on the post as look like i have to upload them to the web and use an url to stick them to the post.. can you help me or told me how to post the pics here?… i made a cw backup for the 8/16 build running and return to the 7/23 restore as i it have the gps working… ..
[Vibrant Android Development] roberton:
never mind find the attach files buttom at the botom... here are the pics of my vibrant with the 8/16 build

someone should upgrade to it with gps off...

also, find out that i didnt deleted the 8/16 cw backup with the bootloop, so i have both the one working with the gps off and the one with the bootloop state
[Vibrant Android Development] jrongi1:
I compiled this PAC rom.
[Vibrant Android Development] ioancr:
[MENTION=438188]Der[/MENTION]

Solved baseband issue, it was modem.bin. Now calls are ok. Still root problems, even after switch to apps+adb (they are on my port of Slim 4.3 as well).
[Vibrant Android Development] letthebasskick:
Alright so GPS works with the slimbean port from the captivate using gearkernel , i also tried it using hellybeans kernel but i couldn't get signal and the wifi was grayed out
[Vibrant Android Development] DerTeufel1980:
Then you didn't copy the modules :)

But we're getting closer

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
Which device tree did you use?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] jrongi1:
I modded the cm repo to match closer the i9000

Nexus⁴ PAC 360° Productions
[Vibrant Android Development] DerTeufel1980:
Did you change it to use i9000 GPS? (this would be the obvious fix, but I guess GPS working after deep sleep would be broken again)

Do you have your tree at github?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] Alberto96:
insecure kernel : http://www.xdafileserver.nl/Files/D...nt/NoSecure_GearKernel_JB3_Vibrant_1.0.6v.zip
[Vibrant Android Development] DerTeufel1980:
Didn't think about it previously. Now that you have a working rom, please make a nandroid, then reboot and try to connect your phone by adb shell again. This time you should get a pop up on your phone, to allow connection from your pc.

After this please enable GPS and reboot. You now should be able to get the logcat.

Btw: is GPS working, before you reboot?

@ the others: please try to get a logcat by using the kernel Alberto96 kindly provided for me/us

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] tsatomas:
Do you need a try with i9000 (not vibrant)?
[Vibrant Android Development] roberton:
will try later today at home (i already had a nandroid of 4.3 working)

but, i tried the adb shell with the 4.3 working rom and had the same problem of device not authorized, so i can get the adb shell, will try again later at home to confirm, do i need to change something i the settings to get the adb shell working?

as soon as i enable the gps it get reboot by itself and get the bootloop..

gps was working before upgrade to 8/16 build, but it was off.. i cant tell you if it worked on 8/16 build as at the moment that i turn the gps on, it reboot like it crashed, and get into the bootloop..
[Vibrant Android Development] DerTeufel1980:
Then please also try the unsecure kernel to get logcat working :)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
Btw: based off the reports, here's a workaround to get 4.3 booting.

Install any 4.2.2 rom, wipe data and boot up. Then disable GPS and boot to recovery to flash 4.3 hellybean :)

After it is working, don't turn on GPS again, unless you did a nandroid before, and want to help to fix this problem

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] jrongi1:
Yes I setup the repo to the same gps settings as the i9000. No I don't have it on github.

As of right now the vibrant I am testing with has broken gps so I can't test how/if it works.

Nexus⁴ PAC 360° Productions
[Vibrant Android Development] apples723:
ive got some time on my hands ill try and help you fix it now that i got it to boot my computer wont detect my device with out getting usb device not recognized error so if you need adb thats probably out of the question i do have adb installed though so if i can still help let me know
[Vibrant Android Development] roberton:
what do you mean with try the unsecure kernel? is this a kernel to flash before turn on the gps to create the bootloop? if so, where can i download the file...
[Vibrant Android Development] DerTeufel1980:
The kernel posted by Alberto96 should allow adb connections. I asked him to compile it with ro.secure 0,to allow this

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] tsatomas:
I have tried adb logcat in my i9000 with devil(default) kernel and is working while in rom. in recovery i have error:/sbin/sh: exec:line 1: logcat: not found.

but the question I think is if insecure kernel is working with adb. So now I backup and then flash insecure and report back.

By the way can you tell me how I can tell adb to create a backup? the command backup return warning unlock your device (obviously I must type the command in proper way but I cnnot understand which)

Edit: I flashed gear (nosecure) kernel on my I9000 HB4.3. work good. In rom I can have logcat with adb. In recovery I have the same errror (sbin/sh...logcat not found) please tellme If it is need to do something more for it to work (I have mount everything also but still nothing)
[Vibrant Android Development] Linkmeup82:
That is a good suggestion as that will ensure the correct drivers are installed. Also, you are correct about the cables. My old Nokia cable and Blackberry cable also both work. I have have been using the sd card method to flash ROMs, oh well. I'm using the stock Vibrant cable and my S4 cable for testing. I have attached a screenshot of a Galaxy S1 attached to Windows 7 using the Nexus S drivers. It shows up in device manager as Google Nexus S ADB Interface and files can be transferred using Windows and\or ADB. The difference is that the screenshot is a Galaxy S1 Fascinate not my Vibrant. They are running the same AOSP firmware and use the same Nexus S drivers. There are other or different drivers but not "slightly different drivers." I have installed "The Nexus S Driver" that works on the Vibrant and any S1 running AOSP in my experience. I just wanted you all to see that the correct diver is installed and I'm using a stock USB cable. The S1 Fascinate on AOSP shows up and works fine with the Nexus S driver and my S1 Vibrant on AOSP does not but will charge. The charger port on the Vibrant is wallowed out and is obviously causing PC connectivity issues. On a side note, I have plugged my Vibrant in to PCs without any Android drivers installed and the PC normally will still recognize the device and mount as removable storage prior to the port issue. This just doesn't happen anymore and since I have the correct drivers installed and the S1 Fascinate (that uses the same Nexus S driver) is showing up, it has to be a port issue. I've tested 5 PCs. I'm going to quit spamming this thread since I did believe at first the issue was with this ROM, I now blame my old Vibrant's wallowed out USB port. Thanks to the dev for a wonderful ROM and the xda community for all of your help. I've always said, if any of you would like to PM me to avoid being flamed by the trolls when asking for help, please feel free.
[Vibrant Android Development] Globespy:
Link to last stable 4.2.2 build

I'm reviving my old vibrant to gift away.

I'd like to stick with 4.2.2 given the unresolved cellular and WiFi issues with 4.3

The phone is currently running the build from Friday December 28th 2012.

I'd appreciate a working link to the last stable 4.2.2 build.

Also, I'm running Devil kernel so if anyone has the last stable 4.2.2 version I'd appreciate it.

Thanks!
[Vibrant Android Development] thraizer:
http://andromirror.com/rom/hb42-vibrant/downloads
[Vibrant Android Development] omnifarious:
I got 8/16 to boot following your instructions. Thanks!
[Vibrant Android Development] omnifarious:
Pic 1/2
[Vibrant Android Development] DerTeufel1980:
Did anyone adb shell to work on the 4.3 build?

I still need a logcat of what is going on, by turning on GPS.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] tsatomas:
Hi, if I can help tell me. I have gt-i9000 with hellybean4.3 and gear kernel. Wifi gps adb working here, I can have a logcat if you like but I dont have a vibrant. you can post or pm to me ;)
[Vibrant Android Development] DerTeufel1980:
Thanks, but this doesn't help, unless you flash the vibrant rom

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] tsatomas:
Sorry but I don't have the time to do that. I am going abroad tomorrow and I need a working phone! :p
[Vibrant Android Development] omnifarious:
I flashed the latest gearkernel on top of the ROM, will that be a problem. I have adb but I don't know how to generate a logcat. Also, I have no power button so going into recovery is extremely hard if it's not recognized in adb or boot loops. I had to flash bionix fisherman mod after I flash the 8/18 build because "adb reboot recovery" wasn't working.
[Vibrant Android Development] jrongi1:
gps issues

I got a logcat and will send to you via pm

its not helly_bean but pac but should have the relevant info.

sorry it was what I was already testing.
[Vibrant Android Development] omnifarious:
I'm tempted to try but I figured I'd ask first, will 8/18 boot if I flash with no wipe on 8/16? At the moment I'm happy I even got 4.3 to work in the first place but I also want to help further development. I have backups and I know now how to work my phone without a power button so I'll do what it takes. Let me know if I can further assist in anyway.

EDIT: I just realized this after flashing gearkernel 1.0.6sv and switching to default memory. I also flashed kb5 modem so it could be either one or all of those.
[Vibrant Android Development] omnifarious:
1/2
[Vibrant Android Development] omnifarious:
2/2

SElinux disabled
[Vibrant Android Development] DerTeufel1980:
Selinux is disabled in gearkernel. It should be working with mine

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] cmw6300:
Just had a weird problem occur on my Vibrant. The phone wasn't responding to anything so I held the power button to reset it. When it came back on, it went straight to recovery. This isn't too troublesome but when I try and reboot the phone, it goes right back to recovery. I tried flashing the ROM again, (I'm on 6/26 build) but it says my SD card is not there. I keep trying to get in to Download mode but instead it goes in to recovery and I'm back a square one again. Any help you guys could give me would be greatly appreciated.

Thanks,

Chad
[Vibrant Android Development] jrongi1:
[MENTION=4196889]DerTeufel1980[/MENTION]

If you want/need anything different in the way of a logcat send a pm with instructions.

I will try to get what exactly you are looking for.

Nexus⁴ PAC 360° Productions
[Vibrant Android Development] roberton:
i cant download the unsecure kernel form page 147.. link is not working for me...cant get adb to connect, it only get connected on recovery....
[Vibrant Android Development] DerTeufel1980:
Thanks, that was correct. I just need to understand the error now :(

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
I am going to upload two test builds in few minutes.

Please prepare for it by creating a nandroid.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
Done. Both builds uploaded.

You can find them at:

andromirror.com/hb42-vibrant

By using the drop down menu you can choose test1 and 2

Please report back

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] jrongi1:
Any flash instructions?

Like before with turn off GPS?
[Vibrant Android Development] DerTeufel1980:
you can flash with gps off, and see if it is booting this way, then turn it on.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
I am going to sleep now. Hope there'll be some positive feedback when I am up

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] jrongi1:
Both roms boot but gps is non-functional.

I will try to get logs later.

Nexus⁴ PAC 360° Productions
[Vibrant Android Development] DerTeufel1980:
Have you also booted with gps enabled? Maybe it's the old deep sleep bug

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] jrongi1:
They both boot fine with gps on.

I just don't seem to get any response from the gps, but I will try to get a log later.

Nexus⁴ PAC 360° Productions
[Vibrant Android Development] nomadman:
Thanks for the feedback. How are other function. I never use GPS, but what about wifi, BT issues, and just overall responsiveness and battery life?
[Vibrant Android Development] jrongi1:
wifi works fine

BT I cant test

and with gps on no deep sleep(didnt turn off)

otherwise all seem fine.
[Vibrant Android Development] edwin270:
Everything is working great, except gps, battery life is good. And unless I forget a little graphical glitch when you turn the screen off.

App bar has a little problem when chosen to be in the right.

Halo seems to be below v2. Though it works well but not compared to v2.

Status bar (notification drawer) summertimes have misaligned toggles when slided down.

Using Chrome browser can be a pain also.

Focal has its problem like all others.

Overall can be used as a daily driver.
[Vibrant Android Development] DerTeufel1980:
New build uploaded, gps still broken :banghead:

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] Ace42:
Are test 1 and 2 needed still?
[Vibrant Android Development] DerTeufel1980:
No, I got the logs, but I have now idea how to fix it

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] driodmaster92:
Can you give me the sources from which you are building the ROM ?

Edit: Could not find relevant changes in your github for this device
[Vibrant Android Development] elfabio00:
I tried todo flash this ROM and i gave an error, so I installed my previous ROM version (remics 4.2.2) and I don't have signal now :( !!help please!!
[Vibrant Android Development] DerTeufel1980:
In the last test I just had taken the proprietary files from i9000 for the vibrant. Those changes are at my github. It's vendor/samsung/vibrantmtd

But there seems to be a call to a function inside the proprietary file, which isn't used by vibrant.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] apples723:
The way I fixed that was flashing back to stock or check your APN settings.
[Vibrant Android Development] DerTeufel1980:
New build online

GPS should be fixed now

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] cannondaleV2000:
Cool. I'm gona have to try that
[Vibrant Android Development] mastewman:
Losing APN settings after upgrading from latest Helly Bean build 10/10/13.... Currently, on 07/10/13 build...
[Vibrant Android Development] DerTeufel1980:
Can someone confirm this? Did you keep my kernel?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] selmandeli:
I made a clean flash, coming from CyanAOSP JB 4.3. I lost my Baseband after flashing the last version. It was lost on first boot (usually happens after 1st reboot). I copied files from efs backup and flashing another modem with no success.
[Vibrant Android Development] mastewman:
Yes, I have kept your kernel....
[Vibrant Android Development] DerTeufel1980:
I am not at home this weekend. I am going to look into this on Sunday

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] cannondaleV2000:
I didn't loose anything while flashing. But zram won't enable through performance settings like of used to
[Vibrant Android Development] DerTeufel1980:
New build online, if you didn't notice it already :)

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Vibrant Android Development] tsatomas:
Thank you for this, I upgraded friend's phone to 4.3 without problem:)
[Vibrant Android Development] livbean:
Last version installed without a hitch, latest clean install am receiving keyboard crash.

EDIT: Fixed with install of older Gapps. All is well.
[Vibrant Android Development] omnifarious:
Which version exactly did you flash to fix this issue? I used the one from 03/01/2013 and Slim minimal gapps 4.3 build 2 and neither one solved this issue. I'm about to revert to an older version of Hellybean.

BTW, I tried Albert's new Universal 1.1.0 sv flashed thru odin and it gave me a bootloop. 1.0.9v2 sv woks fine for me but I still had the f/c issue with phone app.
[Vibrant Android Development] livbean:
gapps-jb43-20130726-signed.zip

I keep all the older files on my SD for that very reason.
[Vibrant Android Development] Dougfresh:
Yes I wipe dalvik cache and also cache everyday, that's it, keep background processes to 2, sio,smartassv2, allow purging of assets, no zram or uksm, both smooth settings in devil app...Runs like BUTTAH!!
[Vibrant Android Development] Drjjones426:
I don't find it to be anywhere close to ICS and definitely not froyo
[Vibrant Android Development] samsgun357:
Same GPS deal as with ICS, maybe worse IMO. To me its worth it!

sent from the depths of helly bean

---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------

Got ya, I wasn't bustin balls, just curious if you thought that kernel version had better luck with GPS.

sent from the depths of helly bean
[Vibrant Android Development] N_B:
Awesome.

This friggin' rules. Thanks everyone who worked on it.

Aside from keeping me amused...both by having a new ROM to play with AND making me the only one in my area to have JB (on a 3 year old phone, no less), this is definitely the best Android version yet...I could go on about how the email app finally has enough functionality where I don't need touchdown, and how the calendar widget is now actually really useful...and resizable..., and how the notifications dropdown thingy gives me more info and useful options, and on and on...but you can find that info elsewhere.

Haven't tried GPS, haven't dialed 911, and can't tell about battery life because I'm playing with my phone 10x more than usual... All my email, gmail, texting, important app, and phone call needs are being met, and well.

One thing that is affecting me though, and sorry if it's a known issue that I missed, is speakerphone - sounds fine from my end, but from the other end...super noisy - mostly unusable (I tested from both ends in different environments). My wife has complained about my headphones mic too...but I seem to have lost those in the last few hours, so haven't tested.
[Vibrant Android Development] samsgun357:
Go to advanced in settings and adjust the in call volumes, that will help a lot.

sent from the depths of helly bean
[Vibrant Android Development] Guitar100:
Where do i find 'Background process"? :eek:
[Vibrant Android Development] Big Dog KMc:
Settings/Developer options/Background process limit
[Vibrant Android Development] imilleson:
Here is a dumb question for you, if I leave live over clock high at 1400 MHz but under performance settings leave the max at 1000 MHz, will live over clock still be able to ramp the processor past 1000 MHz ?