Originally Posted by XGX5309

Sorry, no. There's actually no commit under "teamchopsticks" Github for Jellybean on the Hercules. There's activity for the Skyrocket though, so maybe they'll start on the Hercules soon?

Teamhacksung doesn't cater to the Qualcomm devices. Only Exynos and Hummingbird (and an odd Epsilon Tegra kernel ?).

I think he's trying to do a bringup of the Galaxy R. While it's possible at some point one of us will grab a Qcom device, it's highly unlikely.

Epsylon3's experiences with the Galaxy R remind us of why we don't touch Samsungs with alternative processors... You get typical Samsungisms PLUS all sorts of extra weird **** due to it being an architecture they're not familiar with.

Just curious, when you run the ./proprietary-files.sh script, where does it actually store those files within the android/system tree??

Ive got my VMWare Ubuntu all setup and going but its not playing nicely with the whole 'cut and paste' and device sharing between my Mac and Fusion.
I got the entire environment ready to go, but when I connect my phone to USB, even though Ive told Fusion to pass it to Linux, adb cant see my phone to save its life to pull the files from it. I can still do it on my Mac, but from what I can tell, it puts them in both /devices/samsung as well as /vendor/samsung.

I copied both of those directories over (had to FTP to my Mac to get it to copy) and replaced the original ones, but when I try to sync the repo now I get errors. When I copied them over, Ubuntu couldnt copy any of the SVN files inside all the .git folders so I figured resyncing would put those back but nope..

Running into all kinds of errors during compiling so can anyone tell me any tricks to getting adb to see my phone inside VMWare???
Im assuming it works for everyone else??

Originally Posted by Slavestate

Just curious, when you run the ./proprietary-files.sh script, where does it actually store those files within the android/system tree??

Ive got my VMWare Ubuntu all setup and going but its not playing nicely with the whole 'cut and paste' and device sharing between my Mac and Fusion.
I got the entire environment ready to go, but when I connect my phone to USB, even though Ive told Fusion to pass it to Linux, adb cant see my phone to save its life to pull the files from it. I can still do it on my Mac, but from what I can tell, it puts them in both /devices/samsung as well as /vendor/samsung.

I copied both of those directories over (had to FTP to my Mac to get it to copy) and replaced the original ones, but when I try to sync the repo now I get errors. When I copied them over, Ubuntu couldnt copy any of the SVN files inside all the .git folders so I figured resyncing would put those back but nope..

Running into all kinds of errors during compiling so can anyone tell me any tricks to getting adb to see my phone inside VMWare???
Im assuming it works for everyone else??

I'm not using Fusion or OSX, but on the Workstation version you have this on the bottom right hand corner of your VM window. If you mouse over the icons it tells you which is what. You want to find one that says "Samsung Modem". Right click on it and let VMware capture that USB port I/O.

Its been a while since i actually did it but there is a target folder with the prop. files in it. honestly the easiest way... and the way i learned is to open up the .sh and read it. actually understand what it does...

Originally Posted by tmckenn2

Its been a while since i actually did it but there is a target folder with the prop. files in it. honestly the easiest way... and the way i learned is to open up the .sh and read it. actually understand what it does...

~/android/system/vendor/samsung/i777

Originally Posted by tmckenn2

Its been a while since i actually did it but there is a target folder with the prop. files in it. honestly the easiest way... and the way i learned is to open up the .sh and read it. actually understand what it does...

Yeah that was my first step but all the directory names are variables so I just grabbed the vendor one hehe.

Mr XGX - yeah those buttons are at the top of the fusion window. I can get the phone connected via USB fine but no love on adbs end. Ill have to play with it more when I'm home from work. The integration between the Mac and VMWare is already being flaky so I may have messed something up when I set up the VM.. Go figure my WinXP VM works perfect but not my lovely Ubuntu!

Sent from my SGH-I777 using Tapatalk 2

Arrgh this Android environment is tough hehe!

So I deleted the two folders I copied over from my Mac yesterday (devices/samsung, and /vendor/samsung) and resynced..
When it was done, since I still had the /vendor window opened, I noticed it had remade the samsung folder. Looking at it and comparing it to the folder on my Mac, it looks like this already pulled the proprietary files from github for me??? Is this possible??
Its got all the same contents as the one from my Mac which was pulled from my i777.

Still cant get my phone to be seen by adb on Ubuntu so I decided to build anyways, since it looks like its all there.
Im hitting this error repeatedly now:
"/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file".


So a little bit of research into the error and I ran across another JB thread with the same problem.
http://forum.xda-developers.com/show....php?t=1762641

Apparently (and maybe you guys that made guides for building should update it) JB requires a 64bit host to build.
I screwed up and installed the 32bit Ubuntu (thinking this was the right version for a first gen pseudo 64bit Mac Pro).
So now apparently Ive got to start all over again. Although I dont get why my Mac, even though it failed in building, never ran into this error.
Sure I have 64bit Xeons in here but my Snow Leopard is 32bit, and my EFI is 32bit as well so I cant even run a 64bit kernel if I wanted to.. Never saw it on my Mac but in Ubuntu it pops up almost instantly after starting a build..

Well it switched over to 64bit back in GB I want to say. When ICS rolled around you could do it with 32 but you had to make a complete hack job of your box.... but it was do able... idk about jb

Sent from my SGH-I777 using xda app-developers app

Originally Posted by Slavestate

Arrgh this Android environment is tough hehe!

So I deleted the two folders I copied over from my Mac yesterday (devices/samsung, and /vendor/samsung) and resynced..
When it was done, since I still had the /vendor window opened, I noticed it had remade the samsung folder. Looking at it and comparing it to the folder on my Mac, it looks like this already pulled the proprietary files from github for me??? Is this possible??
Its got all the same contents as the one from my Mac which was pulled from my i777.

Still cant get my phone to be seen by adb on Ubuntu so I decided to build anyways, since it looks like its all there.
Im hitting this error repeatedly now:
"/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file".


So a little bit of research into the error and I ran across another JB thread with the same problem.
http://forum.xda-developers.com/show....php?t=1762641

Apparently (and maybe you guys that made guides for building should update it) JB requires a 64bit host to build.
I screwed up and installed the 32bit Ubuntu (thinking this was the right version for a first gen pseudo 64bit Mac Pro).
So now apparently Ive got to start all over again. Although I dont get why my Mac, even though it failed in building, never ran into this error.
Sure I have 64bit Xeons in here but my Snow Leopard is 32bit, and my EFI is 32bit as well so I cant even run a 64bit kernel if I wanted to.. Never saw it on my Mac but in Ubuntu it pops up almost instantly after starting a build..

Originally Posted by tmckenn2

Well it switched over to 64bit back in GB I want to say. When ICS rolled around you could do it with 32 but you had to make a complete hack job of your box.... but it was do able... idk about jb

Sent from my SGH-I777 using xda app-developers app

64-bit should be a given. Personally, I haven't run anything less than 6GB of RAM since ~2007, so 64-bit is the only way I can utilize my hardware. The thought never ran through my mind to add that little detail to the guide. lol.

Originally Posted by XGX5309

64-bit should be a given. Personally, I haven't run anything less than 6GB of RAM since ~2007, so 64-bit is the only way I can utilize my hardware. The thought never ran through my mind to add that little detail to the guide. lol.

Yeah, I have 8 and I'm seriously thinking of adding 4-8 more just for filesystem caching during builds. My system hits swap way too often when I'm running builds.