yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] calikevin:
First off, I am by no means a developer. These guys do some amazing work and it has inspired me to start and get involved. This was done by lots of reading, clicking, sitting, reading, sitting, and clicking. Most of the hard work was already done by the real developers, so I would like to thank them early on-

Albinoman887, android1234567 and TeamHydra for getting the ball rolling with CM10.1 booting on our devices

h8rift, mg and slam for all the work done with CM10 and all the other amazing ROMs available for our devices

CyanogenMod and SlimRom teams for making some beautiful feature rich ROMs

DennisBold for porting the ROM to Sensation, only making it that much easier for me

Anyone else I may have forgotten, you too!

I got this booting by using albinoman's 0629 CM10.1 build as a base then using rishabh.raj37's guide to port SlimBean from the Sensation over to our device.

With a HUGE hand from sultan/android1234567, we have a 99% operational SlimBean ROM, built from source! Thank him here for his awesome work, without him I'd still be searching the forums! :silly:

FEATURES

Optimized Linaro kernel by sultanxda based on synergye's KangBang kernel

Ultra-fast boot time (20 seconds!)

Excellent battery life

Unique SlimBean Features

The real dark Slim.

Invert the whole ROM including Gapps with one click.

Notification drawer and and lockscreen shortcuts

Access your most important apps from everywhere.

Custom Quick Settings Tiles

Why just settings? Use whatever you want.

SlimPIE

Based on CM's PIE, inspired by PA's PIE with a light touch of Slim. A true community feature.

SlimPie is fully configurable, so you can change colors as you wish ..... SlimPie is also very useful if you want to use app-shortcuts with it

- See more at: http://www.slimroms.net/index.php/slim-bean-features#sthash.QUJSU04e.dpuf

Directions-

1. Flash ROM in recovery- http://d-h.st/GVc

2. Flash SlimGapps- http://www.slimroms.net/index.php/downloads/all/viewcategory/383-addons (I haven't tried any of the other addons so I cannot confirm that they will work for us yet)

3. Reboot!

WORKING

Data

WiFi

Storage

SlimPIE

The Real Dark Slim (looks beautiful)

NOT WORKING

Halo

Video Recording

Selecting Display in Settings will cause Force Close, to adjust brightness go into the Interface menu and adjust the Display in there. All other options in the Settings menu seem to be fully operational

Video playback is not working in YouTube or video gallery, to watch video files use MXPlayer for now

??????????????​
[HTC Vivid, Raider, Velocity] camo_flage:
:D
[HTC Vivid, Raider, Velocity] calikevin:
Running the booted ROM right now, really don't understand why but the Baseband version isn't showing up in the settings menu either. Has to be something to do with a ported file right? And there are folders for the internal and external SD but they show up as empty, even though they are still fully populated in recovery and CM10.1... Somewhere a line is pointing to the wrong path, I just need to find and fix it. Seems the APN issue might be a little tougher for me to figure out on my own..
[HTC Vivid, Raider, Velocity] camo_flage:
Ask albino man about those issues since he fixed them
[HTC Vivid, Raider, Velocity] babymatteo:
+1. Albinoman's CM10.1 build is flawless. But would love to run Slimbean on this phone
[HTC Vivid, Raider, Velocity] calikevin:
I did send him a PM but I know he's busy with his sensation developing and trying to make CM10.1 bug free so I'm just patiently waiting until he has some free time or sees this thread (: until then I just keep looking
[HTC Vivid, Raider, Velocity] camo_flage:
I'll try and see if I can get PAC 4.2.2 running
[HTC Vivid, Raider, Velocity] calikevin:
I already have sensation pac1.3 downloaded and was going to attempt porting it today but be my guest, maybe your mobile data and SD cards will work, haha

I also bit the bullet and asked in his thread, hopefully he's not too busy to drop by for a minute
[HTC Vivid, Raider, Velocity] Jaxellis:
I tried to get pac running it just gets to boot animation tgats it.... in a week i will see if I can get it to work
[HTC Vivid, Raider, Velocity] camo_flage:
Well I will give it a shot. Hopefully we can get it booting at least
[HTC Vivid, Raider, Velocity] calikevin:
Let me know how yours turns out, mine is on the bootanimation right now, I'll check for bugs if it makes it past.
[HTC Vivid, Raider, Velocity] camo_flage:
How is it?

---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------

Don't have my Vivid with me right now so it would be great if someone could test it. I'm uploading now
[HTC Vivid, Raider, Velocity] Jaxellis:
I'm pretty sure you have to do some kernel tweaks to get it to boot. once albino gets back I'll do some testing with him to get it running.

Also lets not hijack this thread ;) hahah
[HTC Vivid, Raider, Velocity] camo_flage:
Thanks for the info, will try anyways ;) and we should open up a 4.2.2 rom discussion thread.

---------- Post added at 04:54 PM ---------- Previous post was at 04:48 PM ----------

Here is my PAC rom. can someone please test this? Just flash it like any other 4.2.2 rom. wipe then flash rom and then GAPPS

http://d-h.st/9jb
[HTC Vivid, Raider, Velocity] Jaxellis:
http://xdaforums.com/showthread.php?p=43231830#post43231830

4.2.2 discussion Thread
[HTC Vivid, Raider, Velocity] camo_flage:
Thx :)
[HTC Vivid, Raider, Velocity] calikevin:
Upon first try it didn't boot, but second try before flashing albinoman's 6/30 kernel it booted. I can't seem to get mobile data connected, but the APNs are already there so that issue is a bit smaller. SD cards still don't seem to be showing up in File Manager, SuperUser seems to be malfunctioning somehow too, trying to change File Manager to Root Access Mode doesn't bring up the SuperUser app and File Manager stops responding.

Agreed on the discussion thread too, I will try your version in a bit.
[HTC Vivid, Raider, Velocity] Jaxellis:
Go into developers settings and make sure root access is set to at least apps.

If so does it use stock cm10.1 superuser? if not I can help you there ;)
[HTC Vivid, Raider, Velocity] calikevin:
Rebooting right now, I'll check that once its up. Just flashed the 6/30 kernel and so far so good.

And it does use the CM10.1 SuperUser app
[HTC Vivid, Raider, Velocity] camo_flage:
Thanks :) If mine doesn't boot I will re-compile with the 6/30 kernel....or you could just flash it x)
[HTC Vivid, Raider, Velocity] WildfireDEV:
That error has occurred because it can't I'd the kernel source. The kernel source has to be put in path it specifies. So in this you can see that the kernel source needs to go to a folder named msm8660 in kernel/htc.

**Press the thanks button if I helped you**
[HTC Vivid, Raider, Velocity] Jaxellis:
No the reason is that you arent using the custom kernel mk from team hydra. but since you are using their sources I would check with bino to make sure everything is okay.
[HTC Vivid, Raider, Velocity] calikevin:
How would I go about using their kernel? Is that another sync command? I don't remember having to do that when I used sultans source to build the old slim.. Is that what you mean by check with bino, to see if it was left out or something?
[HTC Vivid, Raider, Velocity] WildfireDEV:
Sorry man I don't mean to start an argument but I am pretty sure that this error comes up when the kernel isn't in the specified folder. The kernel.mk error comes later on in the build. I know because I tried to build Slimbean but it just wouldn't boot.

**Press the thanks button if I helped you**
[HTC Vivid, Raider, Velocity] gevans01:
USB access?..

First, great rom. I have been using it for two weeks as my daily phone with very little Fc and music is perfect. I've noticed when I try to connect usb, I only get access to the internal memory and not the SD. I tried changing the "USB computer connection" to MTP from Mass Storage. Once I do that I loss access to both memories. Any ideas
[HTC Vivid, Raider, Velocity] Jaxellis:
woah woah woah. 6/30 kernel? I thought that kernel didnt work?

it work on pac or slimbean?
[HTC Vivid, Raider, Velocity] calikevin:
The kernel by albinoman from 6/30 works on both Slim and PAC, I've used that kernel (named vivid-mpdec.zip) on all my ports successfully so far... Minus the SD cards not showing up and the mobile data, but I think that has something to do with the sensation side of things.
[HTC Vivid, Raider, Velocity] Sultanxda:
Building slim from source for the Vivid would probably fix those issues
[HTC Vivid, Raider, Velocity] calikevin:
Okay, so here's what I did..

Downloaded the git zips containing the files you mentioned, including the init, the four files in the ramdisk folder, and the only vold.fstab file I could find..

Unpacked the boot.img from the port that I had booting with WiFi, and placed all the files in their respective places (all the init files [5 total] in the ramdisk folder and I put vold.fstab in the system/etc/ folder of the ROM zip, as thats the only place I could find one to replace)

Repacked the boot.img, rezipped the ROM.

Flashed ROM and gapps, it hangs at the HTC Logo now.. looks like I'm heading to source :X

I'm syncing the repo for slimrom right now, and pointers or advice on how to go about combining the two from source and compiling it? Any help you can offer is greatly appreciated and wont go to waste! (:
[HTC Vivid, Raider, Velocity] WildfireDEV:
Hey seeing as I have also downloaded the source maybe we could help each other out.
[HTC Vivid, Raider, Velocity] calikevin:
I'm game, I'll probably be up all night anyways haha
[HTC Vivid, Raider, Velocity] Sultanxda:
Cherry-pick all the commits Albinoman made on June 27th from here: https://github.com/Team-Hydra/android_system_core/commits/holiday

Apply those cherry-picks to the system/core directory in your slimbean source.
[HTC Vivid, Raider, Velocity] calikevin:
Thank you! I'm still new at using GitHub, what's the most direct way to save those files to my computer?

I get this error when trying to apply those cherrypicked patches-

root@KevWebTech1558z:/home/kevin/Documents/ROM Ports/slimrepo/system/core# git am builtins1.patch
Applying: Revert "init: Check for symlinks with lstat() not open()"
error: init/builtins.c: does not match index
Patch failed at 0001 Revert "init: Check for symlinks with lstat() not open()"
The copy of the patch that failed is found in:
/home/kevin/Documents/ROM Ports/slimrepo/system/core/.git/rebase-apply/patch
When you have resolved this problem, run "git am --resolved".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
[HTC Vivid, Raider, Velocity] WildfireDEV:
I just tried to compile from source but when I run lunch cm_holiday-userdebug. It goes searching for the device on slimbeans github and returns with an error. Anyone can possibly help.
[HTC Vivid, Raider, Velocity] Sultanxda:
The problem is that you put cm. Cm means CyanogenMod; you're trying to build Slimbean :p Run breakfast to see what the proper command is for the Slimbean source.
[HTC Vivid, Raider, Velocity] WildfireDEV:
Okay I will try it

---------- Post added at 10:35 PM ---------- Previous post was at 10:27 PM ----------

It now says that the breakfast command isn't found.

---------- Post added at 10:35 PM ---------- Previous post was at 10:35 PM ----------

CM is what appears when you type lunch.
[HTC Vivid, Raider, Velocity] calikevin:
The commands for slimbean should be on the teams website, possibly their forums.. I haven't gotten that far yet
[HTC Vivid, Raider, Velocity] WildfireDEV:
Yep I will try and report back.

---------- Post added at 11:18 PM ---------- Previous post was at 10:47 PM ----------

I have fixed multiple errors but now i get this.
[HTC Vivid, Raider, Velocity] calikevin:
Well as far as I know slim isn't officially supported on the holiday, so they most likely won't have device files for it.. This is why I'm pretty sure we need part of team hydras device trees to make this work, I'm just figuring out how very slowly. That's why it started out as a port
[HTC Vivid, Raider, Velocity] WildfireDEV:
Okay when you figure it out please tell me
[HTC Vivid, Raider, Velocity] Sultanxda:
After running

. build/envsetup.sh

run

breakfast

and a menu of available devices to build for will be generated.
[HTC Vivid, Raider, Velocity] calikevin:
So will we want to build for a different device initially then add the holiday device tree files to make it compatible since the holiday isn't supported?
[HTC Vivid, Raider, Velocity] Sultanxda:
No. Using breakfast we can see what the proper command for building Slimbean is. Then we can compare the device tree to a Slimbean device tree and make the necessary adjustments/file renames.
[HTC Vivid, Raider, Velocity] calikevin:
Okay got it. breakfast brings nothing back though, so here's lunch-

root@KevWebTech1558z:/home/kevin/Documents/ROM Ports/slimrepo# breakfast
breakfast: command not found
root@KevWebTech1558z:/home/kevin/Documents/ROM Ports/slimrepo# lunch

You're building on Linux

Lunch menu... pick a combo:
1. full-eng	25. slim_jfltespr-userdebug
2. full_x86-eng	26. slim_jfltetmo-userdebug
3. vbox_x86-eng	27. slim_jfltevzw-userdebug
4. full_mips-eng	28. slim_m7att-userdebug
5. mini_armv7a_neon-userdebug	29. slim_m7spr-userdebug
6. mini_armv7a-userdebug	30. slim_m7tmo-userdebug
7. mini_mips-userdebug	31. slim_m7ul-userdebug
8. mini_x86-userdebug	32. slim_maguro-userdebug
9. slim_captivatemtd-userdebug	33. slim_mako-userdebug
10. slim_crespo-userdebug	34. slim_manta-userdebug
11. slim_crespo4g-userdebug	35. slim_n7000-userdebug
12. slim_d2att-userdebug	36. slim_n7100-userdebug
13. slim_d2spr-userdebug	37. slim_nozomi-userdebug
14. slim_d2vzw-userdebug	38. slim_p3100-userdebug
15. slim_endeavoru-userdebug	39. slim_p3110-userdebug
16. slim_galaxysmtd-userdebug	40. slim_skyrocket-userdebug
17. slim_grouper-userdebug	41. slim_t0lte-userdebug
18. slim_hercules-userdebug	42. slim_t0lteatt-userdebug
19. slim_i777-userdebug	43. slim_t0ltetmo-userdebug
20. slim_i9100-userdebug	44. slim_tilapia-userdebug
21. slim_i9100g-userdebug	45. slim_toro-userdebug
22. slim_i9300-userdebug	46. slim_toroplus-userdebug
23. slim_jflteatt-userdebug	47. slim_vibrantmtd-userdebug
24. slim_jfltecan-userdebug

Which would you like? [full-eng]

I also got this from another dev who had to do the same thing to get slim on his device, maybe this will help us figure it out?
[HTC Vivid, Raider, Velocity] Sultanxda:
Hmm I'll just try building Slimbean myself so helping you will be easier :) From the menu we see that the command to build slim is brunch slim_holiday-userdebug
[HTC Vivid, Raider, Velocity] calikevin:
Check my edit in my last post too, it explains which files another dev had to add to slim to get his device to work with it. Thanks for all the help sultan, you're the man!
[HTC Vivid, Raider, Velocity] Sultanxda:
Those are the device specific files to build a ROM that we're going to pull from Team-Hydra (i.e. display repo, media repo, etc.). We also have to modify the Holiday's device tree so it works with the Slim source. Right now the Holiday device tree on Team-Hydra is formatted for CyanogenMod. After we find out what we need to change to get Slim building with the Holiday's device tree, we're going to fork it from Team-Hydra and commit the changes. Then you're going to throw together your own platform manifest based on the one provided from Slim's GitHub and add the necessary repos to build Slim for the Holiday.

Right now I'm repo syncing the Slim source (hopefully this doesn't take forever :p)
[HTC Vivid, Raider, Velocity] calikevin:
Okay awesome, sounds easy enough now that we know exactly what to do. The repo shouldn't take too long, I'd say for me between one and two hours, slim isn't nearly as big as CM.

In the meantime, I'm gonna go build a little lunch in the kitchen for myself :p
[HTC Vivid, Raider, Velocity] onlychevys:
I'm watching to see if I can help ya'll, I love Slim and will help if I can.
[HTC Vivid, Raider, Velocity] Sultanxda:
Source finished syncing :victory: I was about to start building but apparently Slimbean doesn't like my Java version :p Once I get it built I'll post it here so you can see if it boots. If all is well and it boots, I'll upload all the source to my GitHub so you can fork it.
[HTC Vivid, Raider, Velocity] WildfireDEV:
Thanks a lot building will be much easier with your help.
[HTC Vivid, Raider, Velocity] calikevin:
Excellent, thank you sultan, I'll be here on standby.
[HTC Vivid, Raider, Velocity] calikevin:
What did you have to do to get your device officially supported? I assume that means it recieves the OTA slim updates too?
[HTC Vivid, Raider, Velocity] Sultanxda:
There we go, now it's building :) It'll be about 30-45 minutes until the build is done.
[HTC Vivid, Raider, Velocity] WildfireDEV:
Cool man I trued I have got past many of the errors but with your help we might end up with a new rom soon.
[HTC Vivid, Raider, Velocity] Sultanxda:
Build complete! Source-built Slimbean for the Vivid: http://d-h.st/Kso
[HTC Vivid, Raider, Velocity] calikevin:
Downloading now, I'll flash and report back

After the first boot, Wifi works, Storage seems to be working, data seems to be connected, and most Settings seem to work except I get a force close when I try to go into Display and set the brightness.
[HTC Vivid, Raider, Velocity] WildfireDEV:
Downloading as well will take me another 5 mins then will report back.

---------- Post added at 01:47 PM ---------- Previous post was at 01:34 PM ----------

Flashed it. It boots up fine. Wifi and Network Connection work. Well done. What ever you did it seems that we now have a working slimbean rom. Also storage mounting works.
[HTC Vivid, Raider, Velocity] Sultanxda:
Seems functional enough :p Maybe that's an upstream problem. What's your GitHub account name? Also, does the boot animation show?

Going to upload my sources so you'll see exactly what I did :)
[HTC Vivid, Raider, Velocity] calikevin:
Definitely functional enough, more functional than my initial port! Awesome work.

My GitHub name is the same as here, calikevin

The boot animation just shows "android" in silver and it shimmers, I do prefer the bootanimation from the port more to be honest
[HTC Vivid, Raider, Velocity] WildfireDEV:
The boot animation did show.
[HTC Vivid, Raider, Velocity] Sultanxda:
Ah ok, I'll fix the boot animation in the source so it looks like the one from the port.
[HTC Vivid, Raider, Velocity] Sultanxda:
Alrighty, instructions for building Slimbean (run these commands in terminal; each line is a different command):

mkdir slimbean
cd slimbean
mkdir -p bin
curl [url]https://dl-ssl.google.com/dl/googlesource/git-repo/repo[/url] > bin/repo
chmod a+x bin/repo
repo init -u git://github.com/sultanxda/platform_manifest.git -b jb4.2
repo sync -c -j4
. build/envsetup.sh
lunch slim_holiday-userdebug
make bacon

The default kernel is my kernel (not the kernel Albinoman uses). Happy building!
[HTC Vivid, Raider, Velocity] calikevin:
Thank you sir, as I said before you are the man.

Is here any way you can show me how you did all the inside work to get the slim files to work on holiday? There are other ROMs I am interested in building for the vivid like illusion and domination, both from the One.. Hate to keep hounding you for help unless of course you just don't mind, in which case you are the best.
[HTC Vivid, Raider, Velocity] Sultanxda:
This commit: https://github.com/sultanxda/androi...mmit/030940bcc4efa1b512156e2e64f9c2ec9895d5b5

Ignore the changes in BoardConfig.mk, those weren't necessary for converting the device tree to Slimbean. Note that cm.mk was renamed to slim.mk.
[HTC Vivid, Raider, Velocity] calikevin:
Basically.. I'll need to make the edits you made in that commit to whatever file corresponds in the version of the ROM I want to bring to the vivid if it doesn't have a holiday variant? Still a little bit blurry on the steps you took after you synced the slimbean repo to make it work for the holiday
[HTC Vivid, Raider, Velocity] Sultanxda:
Depends. You have to study what was done to a device tree that is officially maintained by said ROM developer. But those edits I made should be fairly universal.
[HTC Vivid, Raider, Velocity] calikevin:
Alright understood.

I think I found the display fc problem too, there's a Display settings menu in the Interface menu where the brightness can be adjusted, and that seems to work just fine along with all other slim options and settings I can find to play with.. Which leads me to believe the original Display settings menu button should just be removed entirely to avoid this FC issue and smooth this ROM out a bit. What do I need to do to take that out?
[HTC Vivid, Raider, Velocity] WildfireDEV:
Well now that we have three guys building from source including me. Who is going to release it as it is pretty stable rom. Mine should be finished building in about an hour but I wouldn't be back online until 3 to 4 hours from now.
[HTC Vivid, Raider, Velocity] Sultanxda:
Display menu button? Can you post a screenshot? Or is it pressing the physical menu button that's causing the force close?
[HTC Vivid, Raider, Velocity] calikevin:
Right, pressing the Display button in the Settings menu causes the FC, but the Display settings within the Interface menu work just fine. Does that make sense?

Wildfire, I'd like to figure out this Display FC before releasing the full ROM but if you're up when yours is built feel free to post it and I will put it in OP and give you credit
[HTC Vivid, Raider, Velocity] Sultanxda:
I'll start digging through to try and find the problem. It's probably an overlay problem. BTW, does the camera work?
[HTC Vivid, Raider, Velocity] calikevin:
Now that you mention it video recording doesn't seem to be working in 720p or 1080p, didn't try lower.. Panorama seems to work as does the normal camera though.
[HTC Vivid, Raider, Velocity] Sultanxda:
I suppose I'll look at that tomorrow. I'm done for the night :p
[HTC Vivid, Raider, Velocity] calikevin:
Excellent job for a days work I'd say, very much appreciated sultan!

I tried to build slim and I get this error during bacon-

make[1]: Entering directory `/home/kevin/Documents/romports/slimrepo/kernel/htc/msm8660'
GEN /home/kevin/Documents/romports/slimrepo/out/target/product/holiday/obj/KERNEL_OBJ/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
Using /home/kevin/Documents/romports/slimrepo/kernel/htc/msm8660 as source for kernel
GEN /home/kevin/Documents/romports/slimrepo/out/target/product/holiday/obj/KERNEL_OBJ/Makefile
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[3]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
/home/kevin/Documents/romports/slimrepo/prebuilt/linux-x86/toolchain/linaro-arm-cortex-a8gcc: No such file or directory
Is your PATH set correctly?
make[3]: *** [kernel/bounds.s] Error 2
make[2]: *** [prepare0] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/kevin/Documents/romports/slimrepo/kernel/htc/msm8660'
make: *** [TARGET_KERNEL_BINARIES] Error 2

Seems that its trying to go to a path with gcc added to the end of it for some reason?
[HTC Vivid, Raider, Velocity] onlychevys:
One of there team members started building for my device. I built and posted unofficial slim since 3.0, I just did a 7.0 build last night lol

---------- Post added at 07:52 AM ---------- Previous post was at 07:46 AM ----------

check out this thread, it is full of info on building from source! http://xdaforums.com/showthread.php?t=1798056 There is almost 400 pages but a search will probably have the answer to most any problem you might have. There is some super smart people in there helping.
[HTC Vivid, Raider, Velocity] kkruglov:
only video recording isnt working for now as i see..?

good work guys, another good rom for our device. for some places it works smoother than cm 10.1
[HTC Vivid, Raider, Velocity] Sultanxda:
My fault, I set the paths wrong for Linaro. My kernel can only be built with Linaro. Also, I think I forgot to add the audio HAL to the platform manifest :p