yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] jir591:
I want to give this a try (with modded kernel)but before I do, I want to make sure I know how to go back to before the changes just in case. So are these the right steps?

1) deactivate voodoo

2) reflash with JI6 via Odin and reinstall apps & settings from my Titanium backup

or

1) deactivate voodoo

2) restore nandroid backup

Thanks guys
[Vibrant Android Development] Greenarcher707:
Got a problem copying contacts from kies on to my phone after flashing this. The phone connects but when i go to the phonebook utility it doesn't copy numbers from the pc to the device. What's up with that?
[Vibrant Android Development] ibuddha:
Anyone got an answer for this it would be mighty useful.
[Vibrant Android Development] kiddiosky:
Even with JI2 battery drains pretty fast. Just unplugged my phone 1 hour ago and its already at 91%
[Vibrant Android Development] SkOrPn:
Yeah I know that, but since nothing else is working and I have no more options what else can I do other than just quit trying? I will just format everything manually and pray...
[Vibrant Android Development] sombionix:
True true. Guess it won't hurt. Hope everything works out...ya kind of have me stumped. :/
[Vibrant Android Development] SkOrPn:
Ok I think I have a phone that cant be formated to ext4 or something. I have formatted everything I could find, gone to stock several times, re-downloaded all the files in question and still no dice. Maybe I have locked nand, or maybe I am reading it wrong and I actually have the lagfix. When I use adb shell and type mount, below is what it says. Is that not still disabled?

C:\sdk>adb shell
$ mount
mount
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx
,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/loop0 /data/data1 j4fs rw,noatime,nodiratime 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
[Vibrant Android Development] Paging Dr B:
Lol, we're on the same boat. I used odin and reverted to stock, flashed 1.3 voodoo via recovery, nothing. Reverted to stock, flashed 1.3, re-downloaded 1.3 voodoo, reflashed voodoo same result. this time I repartitioned my internal sd, and am getting ready to try for the last time. Worse case i'll just flash 1.3 and use the old lag fix. can anyone comment on the speed who is using a custom kernel but not using the voodoo lagfix? just wondering if i should stick with kernel included in the voodoo fix or if i should use jac's. Thoughts?
[Vibrant Android Development] SkOrPn:
I got an idea. Im just going to install bionix1.3.zip stock kernel, then use the "other" lagfix method you have in the OP. Then maybe I can use something like apps2sd and have them install to my external class6 sdcard. It has a 1gb ext4 partition on it that might help, but not sure. either way its obvious my phone is broken somewhere, lol....

Thanks for the help sombionix
[Vibrant Android Development] SkOrPn:
Oh yeah... lol, I got you beat. I have spent 18 hours just trying to get voodoo beta4 to work on 4 different roms now. Next up is unsoldering my internal memory and replacing with new memory is my next step I think... lol
[Vibrant Android Development] Viralblack:
Least you didnt end up with a brick cause the perfectly working old Voodoo didnt disable. >.>
[Vibrant Android Development] brandnewsimmy:
Rom is awesome and Voodoo is wonderful but all my media isn't recognized anymore... My photos are gone, ringtones etc. Well they are there still I checked, just not recognized in the Android system. Any idea what that's all about? Thanks!

Sent from Tapatalk
[Vibrant Android Development] Lunatixz:
Hi.. I installed bio1.3.. but voodoo didn't install.. I have no disable file and the voodoo log says my device is not compatible. Any ideas
[Vibrant Android Development] paradox4286:
Installed with the oc kernel, I absolutely love it, its night and day above 1.2

Keep up the awesome romming.

No problems thus far either
[Vibrant Android Development] Keslynn:
I'll probably be trying the Bionix ROM in the morning but I've been having similar luck. Nothing has worked so far. :(

When did you guys get your phone? Right at launch? The date on the box is 7/1. I'm wondering if its a certain batch that can't be converted?
[Vibrant Android Development] Pangulo:
Can I just flash from the king kernel version to voodoo?
[Vibrant Android Development] SkOrPn:
Yeah I was waiting in line at tmo on july 15th, I was the first person in the door. The date on my box says 06/29/10. Maybe we need a newer phone?

EDIT: LOL, muahhahahahahahah.... I selected the insurance option no questions asked, I made that girl tell me out loud that I could bring it back for any reason..... thinking thinking thinking... hmmm
[Vibrant Android Development] adm1jtg:
Just finished installing kingklicks version seems to run very smooth even though quadrant scores are no better then stock. Will report back on battery life in a few days.

One minor issue I did find though when you enable GPS no notification icon appears. I have reloaded twice now and same results. Great work if someone as choosy as me can only find that one minor thing.

Also I did modify the framework-res manually and added the green segmented circular battery and the colored notification icons back in. I wanted the black mods for the dropdown and the colored icons so if the gps is an easy fix if you could just tell me what file to update it would be much appreciated as opposed to modding the whole framework file again.

Thanks again for all your great work I am glad to see someone else who likes the touchwiz interface.
[Vibrant Android Development] adm1jtg:
If you swap it now you will likely get a hardware locked unit.
[Vibrant Android Development] rakeshchn:
Man I love your support on this thread. I am 100% sure you stand behind your ROMs. My vibrant is going to lose virginity tonight (you are responsible :D)
[Vibrant Android Development] LovellKid:
Sombionix you have outdone yourself. Very awesome work, just installed kings and everything was seamless. The black in this ROM is the bomb, very snappy, I for the first time also have considered using touchwiz launcher for the first time. Ill report back on battery life tomorrow. Thanks again...

P.S. Does anyone know if you use SetCPU for Vibrants if you still select the "conservative" option?

Edit: I am a +1 on how awesome you are at responding to this thread. :)
[Vibrant Android Development] Superfrag:
Nice! Thanks a lot man!
[Vibrant Android Development] Maverick777:
Just wanted to give a big thank you for releasing this rom. I finally got it to flash properly. Looks like I may have had remnants of another lag fix or something. I did ODIN back to stock originally, but I guess it didn't completely remove something. I'm guessing I still had a hidden partition or something from a previous lag fix.

I ended up following your guide as if I flashed before uninstalling the voodoo lag fix. Used ODIN to flash Eugene's froyo rom. Downgraded to stock 2.1 and repartitioned. Then flashed Bionix 1.3. Worked like a charm. The only drawback was I forgot to copy the files off the internal SD card so I lost everything when I repartitioned through ODIN. Luckily there wasn't anything important on there.

I also really appreciate the fact that you provided the stock TW theme for those people that don't like the black theme quite as much. You've given an option for practically everything. Kudos for being so flexible.

The rom is insanely fast and the voodoo lag fix is by far the most responsive for daily use.

Thanks again for the great work.
[Vibrant Android Development] Lunatixz:
Anyone getting an error in the voodoo log that there device is not compatible... I have an early release vibrant
[Vibrant Android Development] scpieps:
That's about the rate mine's draining with JI6
[Vibrant Android Development] ebullient:
Odin flashing to stock and then to 1.7 fixed a lot of gremlins for me. It's a good thing to know anyway in case you ever need to do a warranty return.
[Vibrant Android Development] richan90:
The camera creating hundreds of jpgs problem did not resolve itself after several reflashes. I tested this 2 reboots after the flash w no programs or settings changed. How can I get alogcat of this when it occurs at random times?
[Vibrant Android Development] yvyv:
Weird behavior, I have to agree with you for some strange reason 1.4 by far seems to have the best battery life..
[Vibrant Android Development] LovellKid:
According to Cyanogen's wiki.. No. Just has to be plugged in until fully charged before use again.

http://goo.gl/k7Nd
[Vibrant Android Development] whodatfever:
Going from 1.6 Voodoo to 1.7 Voodoo:

Disabled Voodoo. After I flash, what do I need to do to re-enable voodoo or does it just happen naturally. Will the "disable-voodoo" file still be there and still be disabling it? I tried to delete the file in the past and it caused no end of headaches.
[Vibrant Android Development] kizer:
Personally what ever is in JI6 modem or not is a battery sucker.
[Vibrant Android Development] The K-Zoo Kid:
From what i understand, you are supposed to keep the file while you flash 1.7, and afterwards you can delete it and it will be enabled.
[Vibrant Android Development] LovellKid:
Im not having the battery issues others seem to be having. I re-calibrated and between moderate-heavy usage I lasted 19 hours. And I am by no means trying to save battery...
[Vibrant Android Development] smashpunks:
Ok so had the phone off the charger last night used it straight for like 2 hours ask internet, youtube and etc. phone was at 61% when I went to bed for 9 hours, woke up and it was at 55%, I'd say battery is damn good especially the standby.....

No issues on my end still battery is awesome... .
[Vibrant Android Development] Passat80:
Yep, I got same thing happen to me.

Every time I take a picture I find the camera folder filled with hundreds of empty files. I just deleted the camera folder and when I used the camera the next time, a new camera folder was created with only the last picture inside. Can't say if its a fix yet, but will let you know later if I see the folder filled with files again.

Vibrant, Bionix 1.3 ,KK kernel#2
[Vibrant Android Development] orells:
I answered this when he asked this morning "YES"
[Vibrant Android Development] memorito:
Its not working on my phone. I installed the ffc.

I also noticed that /sdcard/DCIM/Camera is stuffed full of Zero KB image files. I am going to cross link this post to the FFC thread for reference. But I think it's a Bionix 1.7 issue as others don't seem to have the problem.

P.S. The size of this thread is ridiculous. Is there no way to segment it by version number?
[Vibrant Android Development] adm1jtg:
On 1.7 with the JI2 I could go 8 hours sleeping and not lose even a single percent.
[Vibrant Android Development] ebullient:
I also got thousands of 0kb jpgs. On my backup folder, which is a straight drag-drop of my folders after several flashes worth, the 'Camera' directory had almost 5,000 empty jpgs. In my fresh stock->1.7 flash, I had 499 jpgs. Now, with the stock Vibrant camera it put photos in 'Photos' and I had no empty jpgs. I think it might be the Captivate software that's doing it somehow, in 'Camera' is where the empties show up.

I'll pop in IRC later today to see if I can ping anyone about this.
[Vibrant Android Development] memorito:
Do you have the FFC installed? I am having that issue, but I thought it was related to the FFC. Maybe it isn't. I am getting the regular pictures I am snapping, but also all the dummy files.
[Vibrant Android Development] winhwah:
Once you flash 1.7 and reboot, just use "Files" app to rename the "disable-voodoo" file to whatever you want and reboot. By doing that you will enable voodoo again and you should hear Linda's voice at startup. Keep it in your folder, it serves as a switch. When you want to flash another rom, just make sure to rename it correctly to disable voodoo.
[Vibrant Android Development] Argusi:
It only seems to happen if I store pics on the external sd, which is what I normally do. If I store pics on the phone, it works fine. When I get some more time I'll get a logcat if no one gets one up by then.

Edit: No FFC yet...
[Vibrant Android Development] ebullient:
I don't have the FFC and I'm having this issue. Fresh stock to 1.7.
[Vibrant Android Development] namansell:
So maybe im retarded but the task manager doesn't list running applications :/
[Vibrant Android Development] richan90:
I tested it for a while using both internal and external sd. For me when I store to ext it will still create files in the internal sd folder.. But my ext folder is clean and stores everything properly
[Vibrant Android Development] winhwah:
I 2nd that, the jpeg files are stored whether it's internal and/or external. I don't have a FFC; I think it's just a common issue.
[Vibrant Android Development] Argusi:
Sorry. That's what I meant. The pics go to the external sd normally, but it creates the superfluous files in the internal sd camera directory, when it's set for external.

If I select internal and delete the junk files, it seems to work normally.
[Vibrant Android Development] Viralblack:
The jpgs are a media scanner issue, looking into it now.

(LOGCATS FTW SLACKERS)
[Vibrant Android Development] Sym_Link:
We are using the international galaxy camera in this build. I was getting the same thing with the zero kb files. I do not see it with the stock Vibrant or the Captivate camera's. So, now I am using the Captivate camera. I have an flashable zip if anyone wants it.

EDIT : Nevermind. I get it with the Cap camera as well and now I see Viral posted, so I guess he is looking into the media scanner issue.
[Vibrant Android Development] wizern23:
to those having the issue with the camera jpegs. download rom manager > select fix permissions > reboot phone. now take a picture and go to gallery. its just a simple permissions error.
[Vibrant Android Development] Viralblack:
Now mount and unmount your SD card to your PC USB, what what the media scanner does ;) You can even practice making a logcat of it

Edit:

Guys I dont tell you to logcat every day for my own good, my phone runs just about perfect cause If I can SEE a bug I can trace the root of a bug. Its like if you had a problem with your car and all you had to do was flip over a simple switch and EVERYTHING going wrong with your car spit itself out on paper. It told you every single thing to look at...

As a community, stop being lazy and learn to pastebin logcats.
[Vibrant Android Development] Argusi:
Lol, I'm out and about with the family and sneaking posts. It would take 30 seconds longer to get the alogcat and I might get caught! :p
[Vibrant Android Development] Viralblack:
Then you shouldnt post a bug! lol

Bugs without logcats to me are like opening this thread and dropping my pants and slamming my junk in the desk drawer, its pointless, it makes me mad, and afterwards all im left doing is holding my **** when I could be fixing a problem.
[Vibrant Android Development] Jacosta:
My google maps isnt working...... Any idea why that would be? Any ways Im loving 1.7 so far great job!!! Thanks
[Vibrant Android Development] Viralblack:
*stabs Jacosta in the throat*
[Vibrant Android Development] Sym_Link:
I'm trying to get you a logcat right now for the jpg issue, but now I can't reproduce. Mounted and unmounted a few times. :mad:
[Vibrant Android Development] wizern23:
nevermind. i misread the post.
[Vibrant Android Development] smutek:
OK thanks, and will do.

I have no idea how to make a logcat but I am willing to learn. I've a paper to write, a house to clean, and a freelance project to finish - but this evening once everything is winding down I will hop on, search, and learn how to make logcats.

Thanks so much for everything you do!
[Vibrant Android Development] vinnydakid:
That just made my day.
[Vibrant Android Development] Argusi:
I know, I know... I am using the camera and did a quick browse to see if it was an issue. The last posts were talking about it. I was trying to narrow it down. Give me a few and I'll "go to the bathroom" and get you a log. :o
[Vibrant Android Development] ebullient:
I'm not where I can do that, I simply wanted to confirm that it's happening and then followup with the fact that I don't have an FFC.

Once I'm back at my box I'll post a logcat.
[Vibrant Android Development] :
LOL...epic
[Vibrant Android Development] Viralblack:
"confirmations" still leave me as I stated before, **** in hand

Luckily for you guys, I was able to recreate this issue and watch it on the debugger, its something I believe with the media scanner, its trying to create thumbnails for something or other
[Vibrant Android Development] wizern23:
so why would some have this issue and not others?

edit: well its back now. it lasted for a little while.
[Vibrant Android Development] winhwah:
Download the aLogcat app from the market to run a logcat.
[Vibrant Android Development] Viralblack:
Because nobody really checked it lol
[Vibrant Android Development] richan90:
logcat attached
[Vibrant Android Development] smashpunks:
Happens when mounted to the pc not when a pic is taken. Fine after taking a pic and looking in gallery, then once mounted and unmount it puts 500 thumbnails in your crap. Trying to do log cat now.
[Vibrant Android Development] richan90:
Here's the logcat about the in call-lock screen unresponsive issue as well.
[Vibrant Android Development] noahkk:
Even that takes some time to make everything come back, don't you still have to download paid apps through the market to get update notifications?
[Vibrant Android Development] ebullient:
Well, I was also hoping to narrow down exactly where it happened so I could try to reproduce it. For me it seems like it only happens when I flash.

Also re: aLogcat, after I posted I thought 'wait a sec I bet there's an app for that.' Yep.

Viralblack don't hate me I e-stalkenjoy your posts in the CM forums.
[Vibrant Android Development] memorito:
That just made me hot.

Is anyone running their FFC on Bionix 1.7?
[Vibrant Android Development] Viralblack:
Oh I dont hate anyone man lol, Im just very direct
[Vibrant Android Development] Viralblack:
Its not throwing any codes, ill try to recreate it

give me a step by step to recreate the same issue on my phone and ill try to do it while hooked up to the dalvik debug
[Vibrant Android Development] smashpunks:
heres my logcat on the issue
[Vibrant Android Development] adamcooks:
I believe that it created the empty photos while rebooting from fixing permisions. This is my first logcat so if its useless hit me a pm and i will try to fix what i need to. thanks for all your work. the web page is quite nice. Is there a team donation link or just hit yall up individual like? Sorry i had to compress it i was .02 bytes over the size limit :(
[Vibrant Android Development] Viralblack:
Its all just individual as you wish to :)

So yeah, now im working on the jpgs, and I dont have quite enough information to go on the wakelock, still fishing
[Vibrant Android Development] richan90:
Thanks, just look at this when you have time. It's definitely not as important as the camera issue.

1. Make a call to any number (tested with vmail)

2. While you're in the call, press home or go to any program.

3. While remaining in home or program screen other than the call screen, press the lock button or let the phone lock itself.

4. Press the lock button again in attempt to access the phone, and it should give you a blank wallpaper screen that is unresponsive.

You can't end the call unless you turn on airplane mode. This problem only occurrs when I use the puzzle lock screen.
[Vibrant Android Development] cashyftw:
I have no idea how or why, but my battery is some how great now, at first I would lose battery in about a couple of minutes, but now I haven't lost any. I unplugged my phone at 94%, went on facebook, went to the market, downloaded pandora, and now playing music, and my phone is still at 94%. Definitely in love with my phone now :D
[Vibrant Android Development] sombionix:
I'm strongly considering going back to ONE lock screen instead of four different options. It seems to be causing more issues then its solving.
[Vibrant Android Development] smashpunks:
the Jpeg issue is wierd, it happens right, take a pic, Mount to pc now theres 500 blank Jpegs. Did a logcat, Mounted again to upload it to pc, unmounted again and the 500 Jpegs were gone..

So mounting once seems to put them there, then mounting a second times erases them. Thats my experience anyways...
[Vibrant Android Development] ZombieDude00:
I just use the puzzle default

Nice work on your Rom dude
[Vibrant Android Development] richan90:
My issue is very minor, but its a bug nonetheless, which is why I submitted it. I just really like the puzzle notifications, so as long as a lockscreen has that im happy =)
[Vibrant Android Development] doubleohseven:
haha can you keep the android and glass ones? those are the two i use most often, and havent had any problems... :/ lol
[Vibrant Android Development] smashpunks:
when you first unplug it, it will stay on that charge for about 10 mins solid or even more, then it should drop normal.
[Vibrant Android Development] ardchoille:
If you do, my vote is for the Epic or stock android lock screens. They're nice and easy in my opinion.
[Vibrant Android Development] smashpunks:
your call, but its sweet to have the option. A great benefit in your rom i think, but im all for stability so if thats what it takes to do it, im all for it. I dont care which one either cause its a lock screen.
[Vibrant Android Development] smashpunks:
ok, ill agree, if I had to choose 2, these would be my pic also..
[Vibrant Android Development] jasonmlit:
My vote is epic.
[Vibrant Android Development] doubleohseven:
hey guys i dunno if anyone saw the question i posted late last night... i had 1.7 bionix j12 and was having outstanding batt performance, more than i needed actually. i wanted to try out j16 so i flashed the standalone modem, but in settings>about phone>baseband version it still reads j12, is this normal or did it not flash?
[Vibrant Android Development] cashyftw:
Keep the Epic lock screen! It's seriously the best.
[Vibrant Android Development] Viralblack:
I agree, leave the epic in, I NEVER have any of these issues

Plus with the new MMS.apk I get notifications again
[Vibrant Android Development] esemkaye:
I vote epic as well, if it comes down to that. =)

...either way, thanks for all the hard work. I've been flashing bionix roms since the beginning. Loving 1.7!

Samsung Vibrant via Tapatalk Pro.
[Vibrant Android Development] ScooterG:
LOL...and I've been using the Epic and Puzzle without issue...
[Vibrant Android Development] miclflores:
As long as there is a Samsung lock screen it's cool. When I use the stock android lock screen it doesn't work the samsung music player lock screen controls. Not sure why this happens, but don't really care if it's the puzzle or sweep screen as long as those lock screen controls work.

Thanks for the great work, trying 1.7 stock kernel with JI6 modem. Will see how battery does after reconditioning. I've seen some pretty impressive results being posted with this ROM hopefully it works out for me. Quick question though. If I want to flash the JI2 modem after testing this out, do I have to recondition the battery again? What if I flash another kernel? Do I have recondition the battery again?