yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Try pressing q for quit ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
You gotta be kidding me. Derp! Thanks man!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I'm stumped and a little tired so maybe I forgot something but what does this mean? When I try to init a new repo...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Unjustified Dev:
Its an error with new repo :( I tried this still doesnt work http://stackoverflow.com/questions/19126603/android-source-repo-gpg-public-key-not-found
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] judas1977:
Hello, i have two sets of compilation errors. Assuming, that i found that errors on pastebin - i'm not the only one...

*

I tried to compile CM10.1, and the result were errors, breaking compilation process:

*

frameworks/base/core/java/android/app/admin/DeviceAdminInfo.java:411: error 101: Unresolved link/see tag "#USES_POLICY_ENFORCE_MMAC" in android.app.admin.DeviceAdminInfo

frameworks/base/core/java/android/app/admin/DeviceAdminInfo.java:411: error 101: Unresolved link/see tag "#USES_POLICY_ENFORCE_SELINUX" in android.app.admin.DeviceAdminInfo

frameworks/base/telephony/java/android/telephony/NeighboringCellInfo.java:104: error 101: Unresolved link/see tag "TelephonyManager#NETWORK_TYPE_DCHSPAP TelephonyManager.NETWORK_TYPE_DCHSPAP" in android.telephony.NeighboringCellInfo

frameworks/base/telephony/java/android/telephony/NeighboringCellInfo.java:166: error 101: Unresolved link/see tag "TelephonyManager#NETWORK_TYPE_DCHSPAP TelephonyManager.NETWORK_TYPE_DCHSPAP" in android.telephony.NeighboringCellInfo

*

That is copy-pasted from pastebin (not mine), but the errors are EXACTLY the same, all four (when trying to compile slimbean - there were only two last errors)

*

I found couple of pastebin entries with those errors, which mean that i'm not only one with it, but solutions on some forums aren't clear enough to me...

*

I found solution for last two errors on some chinese forums (that solution was copy-pasted trough that forums, because was exactly the same, with the same spelling errors:)):

*

2 crrect the file NeighboringCellInfo.java

$ vim frameworks/base/telephony/java/android/telephony/NeighboringCellInfo.java

3

27 //import static android.telephony.TelephonyManager.NETWORK_TYPE_HSPA;

4

:%s/DCHSPAP/HSPA/g

:wq

5

$ make**

*

i think that i'm supposed to change line 27 in NeighboringCellInfo.java, but i don't know exactly how (adding two slashes?)

and i don't understand point 4 of that solution completely ^^

*

Other solution says, that i should delete some "@hide" from TelephonyManager.java or sth, but it didn't help too (but i didn't perform "make clean")

*

For last two errors - i believe, that my country doesn't support that DCHSPAP type of network, so maybe reverting commit adding that type of network could help (if so - how to do it "automatically"?).

*

I found solution for the first two errors too, but it didn't helped much also:

*

The error is fixed by adding '$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk)' into device configuration file.

*

but where? We have such line in "full_device.mk": full_codina.mk, but its "full_base_telephony.mk".

I checked some other phones and that's full_base_telephony.mk too...

*

So, if someone could help me to get rid of those errors - i'll be grateful.

TIA
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey guys, I think I slapped together a CWM touch recovery compatible with 4.3/cm10.2!?

This is what I did.

Downloaded the most current (6.0.3.3) touch from the cwm site. Unzip.

take the recovery.image out and put it in a folder.

Extract zhack into that folder. (swapped the red for the green. The original commands are as per the instructions in the zhack tut)

./zhack -x [COLOR=Red]boot.img[/COLOR]
[COLOR=SeaGreen]recovery.img[/COLOR]

I get extracted: "bootimg.cfg, initrd.img, zImage".

Then, I do the exact same thing with the recomended recovery image 6.0.3.7

Next, I swap out the 'initrd.img' files so the '6.0.3.3 initrd.img' is now in the '6.0.3.7' folder.

issue command:

./zhack -z [COLOR=Red]boot.img[/COLOR] -f bootimg.cfg -k [COLOR=Red]<new zImage>[/COLOR] -r initrd.img
[COLOR=SeaGreen]recovery.img[/COLOR] [COLOR=SeaGreen]zImage[/COLOR]
That gives me a new recovery image that I put back into the 6.0.3.3 folder I extracted earlier with the updater and all that and zipped it up.

Flashed it. Rebooted recovery and flashed a new 4.3 rom and rebooted 3 times with no fail.

The downside is that I couldn't change the version info inside recovery but damn, it works! lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
a good way to test is flash a rom thats not jb4.3 based, boot into it then flash a jb4.3 rom and do a couple of reboots
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
???

Edit: sorry, brain gapp
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Hey guys...can I pick your brains for a minute?? I built a rom from source...aosp based....and everything works except I have no internal or external sd cards?? In twrp, all my files are there, but once the roms boots, there is nothing...

any thoughts?? or help?! Thanks!

I tried to logcat both error and verbose when opening the galley and root explorer, but nothing is showing out of the ordinary??
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ktempleton:
I had that happen to me and I had to replace the external/e2fsprogs and the system/vold I used the ones from cm and that fixed it

sent through the worm hole from a galaxy far far away!!!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I saw a revert for that today
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
Do you remember where? A gerrit, a forum, xda ?

sent from somewhere upon the beanstalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey, there is a cwm 6043 touch recovery posted

recovery-clockwork-touch-6.0.4.3.zip - 7.59 MB

I zipped up a package for y'all. :fingers-crossed:

---------- Post added at 08:00 PM ---------- Previous post was at 07:02 PM ----------

New rom is up everybody! woot!

[ROM][JB][4.3][UNOFFICIAL] Dirty Unicorns v1.0- Skyrocket (06/10/13)

http://xdaforums.com/showthread.php?p=46238178#post46238178
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] herna:
I know how to fix screenshots problems maybe :)

Also I am having one error on my phone. I have 720p and 1080p camera videorecording, but having one big issue with 1080p.

Just see that screenshot using HD 720p, all lools good and can make zoom normally

But if use 1080p it is zoomed at maximum and zoom is not working so quality is so bad. I thibk problem is on media_profiles but cannot find anything annoying , just to say both pictures are token feom the same placea and time, I didn't move myself.

Enviado desde mi GT-N7000 usando Tapatalk 4
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
I was thinking of building the dirty unicorn awhile back. How is it?

I've been fighting with a VanirAOSP build all week and am still at square one. I get a build going and its smooth as $hizz, but I have no internal or external memory.

sent from somewhere upon the beanstalk
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
That's a systen_vold problem or one of the external repos. Also frameworks_av/native might also bee a good place to look.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
It's excellent. Check my thread so far. Everybody seems really happy. It's a little bit of a nut to build tho. The vendor format and overlay calls are a lot different then anything else. It's also a very large repo. Well over 30gigs

Have you checked garret? I just know I saw a fix for that storage issue someplace...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
That's cool! I've been playing with different builds and they all seem to build differently.

What gerrit? CM or Vanir...i am having trouble with my Vanir builds. Everything is good except the storage thing?? I'm off to work but I'll dig through the gerrits some more tomorrow.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I don't have time right now to open a thread but I thought that I would bump this just in case some missed it....

recovery-clockwork-touch-6.0.4.3.zip - 7.59 MB
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
Thanks for providing this, Wantowan2.

A couple of suggestions: font is rather large (can't read all of the "button" text), and there is no option for fixing permissions.

Is it possible to add these changes?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] herna:
Has somebody idea of hown to fix the problem I reported few post before? As it is Galaxy Note and is so similar to GS2 maybe fix is easier to find for yoy

Enviado desde mi GT-N7000 usando Tapatalk 4
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Hey guys, I have 10.2 working fairly well, but am having a couple of bugs and haven't been able to work them out yet.

First, sometimes when unlocking the screen, the buttons come on but the display stays black. Locking, then unlocking usually fixes it. My logcat shows an error about unblankscreen() taking an excessive amount of time while turning the display on. I found one post about this on cm's jira but there was no resolution.

Next, sometimes vibrator doesn't work after a reboot. Thinking maybe the modules weren't loaded, I tried insmod from my shell and it said file exists. A reboot fixes it, but sometimes have to reboot 2 or 3 times before it works again.

Last, I implemented the bln found here:

http://review.Cyanogenmod.org/#/c/45646/

It works, but sometimes it doesn't turn off any ideas why?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
That BLN patch is far from complete and doesn't work - I wouldn't use it, you'll need to trace through the BLN events and how the timers work to fix that problem. We're aware of the fact that it's there, we just stopped working on it because CM10.2 landed at the same time. Additionally, you'll need to create/use the appropriate sysfs interfaces to properly manage the timings and durations and also tie those into a user settings panel in system settings.

As a general rule, don't expect any gerrit patch to work as intended. They are usually still in review for a reason.

With regard to screen wake up, dig through the 9040 & 6E63M0 LCD driver commits from the msm8660 kernel to see how we fixed it for those in both CM10.1 and CM10.2. Not sure which driver you're using, but I'm assuming it's a similar problem related to early suspend/late resume screwing up the power regulators on the LCD board.

In fact, here's my patch for 6E63M0 for the Exhilarate ...

https://github.com/CyanogenMod/andr...mmit/d12cd5f7ed49abe5877d09382b04bc56a95ab32e

This patch is a different way to do it, we're debating the merits of both to figure out whether or not to commit this change:

http://review.cyanogenmod.org/#/c/51296/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] titanic_fanatic:
Cheers. Thanks for the links. My LCD is a MIPI_S6E8AA0_HD720. I'll investigate your commit this evening and see if I can figure out how to port that to my LCD driver.

I'm also going to look into fixing the bln if I can figure it out as I'm still very new to c/c++.

Thanks for the suggestions :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I think this is what I saw....

https://github.com/DU-Final/device_...mmit/8b9b1dda442aea5ed8a809f1b22642281d1b553d

https://github.com/AOKP/device_sams...mmit/be33a29aeee7d166b352420b712e47e17fabc537
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] patch_Adams:
thanks, I'll check this out
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Ya, I really don't know how it might apply to you but I think that is what I saw. Who know, may get you closer anyhow....lol:rolleyes:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Hey guys,

I've noticed something odd with my builds for awhile now but I've been focusing on some other stuff and haven't had an opportunity to look into it. For some reason, the phone is not correctly displaying the battery images/charging animation when the phone is charging while powered off. I know the images are in the system/core repo at system/core/charger/images, and I know that for our phones, those default images are replaced by the images in /device/samsung/qcom-common/charger. The latter images are also the images I see in the filesystem on the phone at /res/images/charger. However, those images are not what I see. Instead I'm getting a long skinny white rectangle. It doesn't appear to be any image I can find anywhere in any source, so I'm guessing there is some type of error in reading the images somewhere. Since I can't take a screenshot with the phone off, it's hard to capture a picture of it where you can really see it well without a lot of reflection/glare/flash/etc. But, here's a crappy picture that will at least give you some idea of what I'm talking about:

Anyone have any idea what might be causing this or which repo to troubleshoot? I'm not sure if this might be an error somewhere in PAC sources, something in the kernel sources (I'm using cvd's Moretz kernel), or some error caused by something derpy that I did to my sources locally.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Some candy if anybody wants a try. android 4.3.1, regular and gapps

Let me know what you think?

Dirty Unicorns

Edit, damn devhost keeps kicking my upload I will have to repost
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I would swear a similar thing was reported in my buddy's PACman ROM for the m7spr recently, but when I looked for it in his thread, I didn't find anything about it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
[MENTION=4559825]wantowan2[/MENTION] ...

You might wanna check your local machine and build environment out ... here's your devhost failure:

Additionally, you need to inform your users that they need to do virus scans if you've uploaded that elsewhere for people to download.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Maybe a PM would have been the way to go here. No need to spread panic for no reason.

This was a false positive. I unzipped the package and scanned it multiple times with a few scanners including Kasp. online scanner.

As it was never uploaded, there is clearly no reason to tell 300 people to go scan everything for absolutely no reason.

Also, that app in question came from PlayStore in the first place. I'd put my money on Googles scanners over hivelocity.net any day.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
For sure, no need to bring the virus police into here.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
You can upload the file(s) to virusscan.Jotti.org or virustotal.com to have them checked by multiple scan engines.

I agree with wantowan2 here. I've seen this detection with the Team Black Out inverted ES File Explorer package before, but not the "official" one. I always thought this was falsely detected because inverting the apk required resigning and possibly created a file size difference.

It's a good opportunity to educate ourselves about potential Android virus threats, even if nobody was at risk this time. It is a real risk.

Here's a decent reference (albeit over a year old): Revealed! The top five Android malware detected in the wild
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Fair enough but it also has to be understood the technically, 99% of all Android apps exhibit malware like tendencies based on the pre Android model. Because of all the info gathering that is allowed to go on. Push etc... Glad you guys understand at least.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Conversely it is always better to be transparent about these things. Making people aware of a false positive is better than saying nothing and having it be a real issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
No worries guys. If you're flashing roms you should know how to take care of the rest of your phone. Always better to error on the side of caution.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
No dude. I'm not dumb. I checked the package 8 ways. There was nothing. Spreading disinformation is way worse. That is a virus in itself. If it never got uploaded in the first place, how is anybody at risk??? And by a false positive no less.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
So, where did I say you were dumb? You seriously need to calm down, nobody here is out to get you as you suggest in your PM. Excuse the f*** out of me for trying to be helpful.

Next time, I'll make sure to keep my advice to myself.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bone_Enterprise:
I for one appreciate the info, it is better than to be cautious than not about something like that.

Thanks for the call out CvD and thank you for the more detailed information wantowan2 about the situation.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Can anyone throw me a bone on this?

device/htc/m7-common/m7-common.mk:166: *** missing separator. Stop.

And here are lines #161-172:

# HTC IR Blaster resources
PRODUCT_PACKAGES += \
CIRModule \
htcirlibs \
<<<<<<< HEAD
cir \ [COLOR="Red"][B] <---------- this is #166[/B][/COLOR]
cir_fw_update \
libhtcirinterface_jni
=======
libhtcirinterface_jni \
init.rc
>>>>>>> 1eb33c4... m7-common: HTC IR Blaster support for AOSP

Any ideas?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
That's a merge/cherry-pick conflict. Older code (what was prior the cherry-pick/merge)is

cir \ [COLOR="Red"][B] <---------- this is #166[/B][/COLOR]
cir_fw_update \
libhtcirinterface_jni

Newer code (what was in the cherry-pick/merge) is

libhtcirinterface_jni \
init.rc

delete one or the other or mix them (example)

cir \
cir_fw_update \
libhtcirinterface_jni \
init.rc
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
Maybe an adventurous builder wants to check this out? http://omnirom.org/why-omni/

Sent from my SGH-I727
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onlychevys:
There are some big dev's working on that! Very interesting.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
I tried compiling it for mako, which should be the easiest and priority for them with flo/deb, and doesn't compile. After adding vendor blobs, my kernel and modifying qcom/display it compiled but black screen after kernel splash. Gave up there.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
Seems to be a common issue right now. Don't think the build for grouper boots either.

Sent from my SGH-I727
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Ha, just started looking into it and come here to read this... awesome. Going to have a look into it and see what I can get done.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] prbassplayer:
Probably isn't hard (for Nexus) . It's mostly aosp last in checked source. Not sure for other devices
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] toyes:
Not building for my Nexus 4. Believe it or not I still have it stock. I'm working on it for the skyrocket right now. Synced and have a build running right now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lackyking:
I have the same problem? anyone could help us?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] drewopo77:
so if i am reading it right , have the the command prompt read

"andrew@andrew-Dell-System-XPS-L702X:~/cm10/device/samsung/skyrocket$"

and then run the patch for it

"git fetch http://review.cyanogenmod.com/CyanogenMod/android_device_samsung_skyrocket refs/changes/99/18999/2 && git cherry-pick FETCH_HEAD"

and it will get apply the patch
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
BINGO!!! We've got a winner.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] drewopo77:
thank you very much for the help , its not as hard as i thought it would be.

also,

BMP7777 if you want to add on first page , i have been useing twrp recovery without any problems so far
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aSquard:
Bah! You mean to tell me I might have been done with all this?? I have 32bit because the Viao says it won't run the 64bit
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Can't build GB and above on 32bit.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] aSquard:
That's the error I got when running the nomodeset acpi=off on the 64bit Linux Mint boot disc

and then:

alpha@Mint-Book:~$ dpkg-architecture
DEB_BUILD_ARCH=i386
DEB_BUILD_ARCH_OS=linux
DEB_BUILD_ARCH_CPU=i386
DEB_BUILD_ARCH_BITS=32
DEB_BUILD_ARCH_ENDIAN=little
DEB_BUILD_GNU_CPU=i686
DEB_BUILD_GNU_SYSTEM=linux-gnu
DEB_BUILD_GNU_TYPE=i686-linux-gnu
DEB_BUILD_MULTIARCH=i386-linux-gnu
DEB_HOST_ARCH=i386
DEB_HOST_ARCH_OS=linux
DEB_HOST_ARCH_CPU=i386
DEB_HOST_ARCH_BITS=32
DEB_HOST_ARCH_ENDIAN=little
DEB_HOST_GNU_CPU=i686
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=i686-linux-gnu
DEB_HOST_MULTIARCH=i386-linux-gnu

Looks like I'm 32bit guys - regardless, I appreciate all the help and tips!

Sugary Jelly Bean 4.1.1 (CM10 Alpha) and XDA Premium
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
It's been very quite in here tonight, I guess everyone is busy building?

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Saitou33:
Thank you. It looked like it was going to work after I did that...but I fail once again. :o

http://pastebin.com/81dnKvsk

I don't get it...the first thing it says is that it cannot find github. Then it starts syncing (doesn't that mean it did connect to github?) and a few hours later it gives me the finger.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] drewopo77:
One more question about cherry picking. When do u do it after the resync and before the build or before u resync
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mindmajick:
After the resync before you build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
I just got word from daveyglow that installing the latest gapps-729 fixed the camera crash after taking one picture it did for him anyway.

Can the people reporting the same issue after flashing my 8/1 build verify if this worked or not? After flashing gapps I would also wipe both caches and fix permissions.

http://goo.im/devs/cdesai/gapps/gapps-jb-20120729.zip

Thanks Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Cboss:
I flashed your 8/1 build yesterday. Also have gallery crash error. Just flashed these gapps and wiped both caches and fixed permissions still getting gallery crash. It's a no go for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
Import includes file: out/target/product/skyrocket/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
make: *** No rule to make target `out/target/product/skyrocket/obj/lib/libaudioalsa.so', needed by `out/target/product/skyrocket/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....

Crapping out on mka bacon

any ideas?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Decepticaons:
I was having this problem too. First i would go back to the guide for setting up build environment, and follow steps 1-5 only. A lot of the command will say "already exists", that's ok, we just want to verify nothing is missing. Then jump back to sk8ers guide. Copy and paste everything in the repo script box, then hit enter. In the cm10 directory box only copy and paste from mkdir through the first repo sync -j16. That will only run a few minutes. Then terminal should be at CM10$, at that point copy and paste from wget through the next repo sync -j16. See what happens then.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bdusmc:
Don't give up yet! :)

How old is the vaio? I don't know the exact terminology, but you need to have certain cpu flags in order to run the 64 bit version. It doesn't mean you need to have a fancy 64bit CPU.

I know it's kind of counterintuitive, but try and install the amd64 version of mint just for the hell of it. It might just fly.