Related
http://forum.xda-developers.com/showthread.php?t=803208&page=39
I think that once their root method uss finally released we will be able to use it in the htc glacier
Sent from mai HTC AntiTitanic
Root Guide:
http://forum.xda-developers.com/showthread.php?p=9109921
So who's gonna do it first? You can always claim stupidity and bring it back to t-mobile for a replacement. Personally, I can't afford the downtime because I'm on call. :-/
If no one tries it by tomorrow I will do it. At work right now and have the kids tonight.
InGeNeTiCs said:
Root Guide:
http://forum.xda-developers.com/showthread.php?p=9109921
So who's gonna do it first? You can always claim stupidity and bring it back to t-mobile for a replacement. Personally, I can't afford the downtime because I'm on call. :-/
Click to expand...
Click to collapse
I would suggest not tryin to perm root until we have specific directions for our phone. It won't be too long until that happens so just be patient.
Good news and great work to the G2 team. Shouldn't take too long for us!
I am not 100% sure about this but we may need the kernel source for this. If I understand they way they got WP off was by using a kernel module to power down the emmc and then another to reinitialize it, we could need espresso source to make it work. I may be wrong though and someone may have it done by tomorrow.......
i'll wait for a script to be released to the market
double post
Don't try this with the G2 method. They're loading a kernel module that's kernel specific if I'm not mistaken. We need a specific module for the MT4G.
Sent from my HTC Glacier using XDA App
They did a awesome job!! Now everyone with the MT4G needs to bug HTC for the Kernel source code for our phones! Then we can recompile this the day its released and have S-Off on the MT4G. This will also let us create the overclock module for non rooted people. I cannot wait to see what this phone can really do!
Thanks to everyone in #G2root!!
Alright, I developed the effit attitude and figured if I screwed it up I would just play stupid. (I'm from Kentucky so the stereotype and accent work in my favor sometimes. )
I tried both kernel modules (wpthis-pre-ota.ko and wpthis-ota.ko) and both gave me an EXEC FORMAT ERROR. I ignored the errors and drove on with the instructions. DD'ing the hboot-eng.img went flawlessly and sync appeared to work b/c it just gave me a prompt waiting for the next command.
After reboot everything stayed the same S=on was still laughing at me. Sooooo, nogo.
All I got from this was the errors. No brick!
Gr8gorilla said:
I am not 100% sure about this but we may need the kernel source for this. If I understand they way they got WP off was by using a kernel module to power down the emmc and then another to reinitialize it, we could need espresso source to make it work. I may be wrong though and someone may have it done by tomorrow.......
Click to expand...
Click to collapse
I read a post saying they reversed engineered it before HTC released the kernel source. One way or another we'll get it.
grankin01 said:
Alright, I developed the effit attitude and figured if I screwed it up I would just play stupid. (I'm from Kentucky so the stereotype and accent work in my favor sometimes. )
I tried both kernel modules (wpthis-pre-ota.ko and wpthis-ota.ko) and both gave me an EXEC FORMAT ERROR. I ignored the errors and drove on with the instructions. DD'ing the hboot-eng.img went flawlessly and sync appeared to work b/c it just gave me a prompt waiting for the next command.
After reboot everything stayed the same S=on was still laughing at me. Sooooo, nogo.
All I got from this was the errors. No brick!
Click to expand...
Click to collapse
The EXEC FORMAT ERROR was because of mismatching kernel versions! We have to have one made against the HTC Glacier(MyTouch 4G) kernel source, which has not been released by HTC.
Also, the Engineering HBoot is specific to the G2. You could've bricked if you weren't careful.
travisjames said:
The EXEC FORMAT ERROR was because of mismatching kernel versions! We have to have one made against the HTC Glacier(MyTouch 4G) kernel source, which has not been released by HTC.
Also, the Engineering HBoot is specific to the G2. You could've bricked if you weren't careful.
Click to expand...
Click to collapse
Just figured I'd give it a shot. Nothing ventured nothing gained right.
Anyway, I figured it wouldn't work before I tried it due to different kernel builds. If I am looking at the two phones correctly they both have 2.6.32 kernels just different builds of it. And the architecture of the phones should be very similar based on the use of the qualcomm chips.
Could have bricked the phone, yes, but also could have (slight chance) worked without having to recompile anything.
grankin01 said:
Just figured I'd give it a shot. Nothing ventured nothing gained right.
Anyway, I figured it wouldn't work before I tried it due to different kernel builds. If I am looking at the two phones correctly they both have 2.6.32 kernels just different builds of it. And the architecture of the phones should be very similar based on the use of the qualcomm chips.
Could have bricked the phone, yes, but also could have (slight chance) worked without having to recompile anything.
Click to expand...
Click to collapse
attaboy
grankin01 said:
Just figured I'd give it a shot. Nothing ventured nothing gained right.
Anyway, I figured it wouldn't work before I tried it due to different kernel builds. If I am looking at the two phones correctly they both have 2.6.32 kernels just different builds of it. And the architecture of the phones should be very similar based on the use of the qualcomm chips.
Could have bricked the phone, yes, but also could have (slight chance) worked without having to recompile anything.
Click to expand...
Click to collapse
For sure. Someone has to be the first try it. Thanks for being the guy to put your balls together and do it.
InGeNeTiCs said:
attaboy
Click to expand...
Click to collapse
dwilson88 said:
For sure. Someone has to be the first try it. Thanks for being the guy to put your balls together and do it.
Click to expand...
Click to collapse
LOL, no prob! Just as eager for root and some cyanogen love (among other things) as anyone else.
Question: The desire HD is a different kernel correct?
grankin01 said:
LOL, no prob! Just as eager for root and some cyanogen love (among other things) as anyone else.
Click to expand...
Click to collapse
Haha...I'd settle for the battery percentage mod. I can't understand why this isn't standard....ugh
Hi there,I'm trying to port the SDK dump to my LG P500,which has the same specs like ZTE Blade.
After applying normal methods for making other phones' roms boot and a special patch found here it doesn't even give logcat,so bootloops in recovery.
After doing some research,I discovered that libs are built for armv7,which we don't have. But also Honeycomb SDK libs were built from armv7,but we got it working on both LG P500 and ZTE Blade.
So,any ideas? Just asking
I think honeycomb and below was build from armeabi (To run on the old simulator that was armv6 vfp (but the vfp wasn't used by google).
whereas ics was built for armeabi-v7a
That is certainly implied by the AVD manager anyway.
unrandomsam said:
I think honeycomb and below was build from armeabi (To run on the old simulator that was armv6 vfp (but the vfp wasn't used by google).
whereas ics was built for armeabi-v7a
That is certainly implied by the AVD manager anyway.
Click to expand...
Click to collapse
Thank you for replying
usually only kernel have ARM text and other also init.rc have kernel text if editing them to ARMv6 kernel text then it needs to work in ARMv6 device..
If not, then some files needs editing...
Android 4.0 ICS needs new EGL and hw files which needs to be ARMv6= ZTE Blade/other phone! all phones have own files to work fine!
If someone can edit Android 4.0 libGLES*.so, libEGL.so files and then egl folder files needs editing.. and then hw folder files for Screen, sensors, GPS, Audio, etc.
then them need right files to get work the audio, camera, WiFi...
WiFi files can work if you add older Android OS WiFi files: libhardware-legacy.so or what it is and then right WiFi files to /System/etc/
to get all to work it maybe takes many days and for me more than 9 months because I'm only 14! xD
SDK port is maybe not really good, it's better to port from other device ex: Samsung... then some files works without editing...
manumanfred the sdk was compiled for ARMv7, it's a different cpu, different machine code. It needs recompiling, to be able to do that you need the source code to compile it.
Without source code you're about as likely to get ICS running on your Blade as you are to get your PS3 running Windows 7.
When devices with ICS are available source code will be too, so porting it from another device would be a waste of time.
wbaw said:
manumanfred the sdk was compiled for ARMv7, it's a different cpu, different machine code. It needs recompiling, to be able to do that you need the source code to compile it.
Without source code you're about as likely to get ICS running on your Blade as you are to get your PS3 running Windows 7.
When devices with ICS are available source code will be too, so porting it from another device would be a waste of time.
Click to expand...
Click to collapse
its not hard to get ICS on zte blade as zte blade got a test verision of ICS
SWEATTAIMI said:
its not hard to get ICS on zte blade as zte blade got a test verision of ICS
Click to expand...
Click to collapse
Are you sharing it?
If not, it's still pretty hard.
http://forum.xda-developers.com/showthread.php?t=1312595
anyone please check this out maybe this can work
http://groups.google.com/group/android-building/msg/c0e01b4619a1455a?pli=1
Android ICS sourcecode is released! I belive that now in Cyanogenmod headquaters people hear red alert
uosiumen said:
http://groups.google.com/group/android-building/msg/c0e01b4619a1455a?pli=1
Android ICS sourcecode is released! I belive that now in Cyanogenmod headquaters people hear red alert
Click to expand...
Click to collapse
uosiumen said:
http://groups.google.com/group/android-building/msg/c0e01b4619a1455a?pli=1
Android ICS sourcecode is released! I belive that now in Cyanogenmod headquaters people hear red alert
Click to expand...
Click to collapse
Fail, u cant grab anything
Sent from my Transformer TF101 using xda premium
ICS on the Blade is booting!
But that's all it does
I used this ROM and replaced boot.img with CM N257. In the honeycomb port they fixed the flipped screen with patching libsurfaceflinger.so on offset 1AC90 but that does not work on ICS. Launcher FC's on first boot but does not after reboot.
Could you please upload that booting rom? I tried it and it won't even install. Even if nothing works, I would like to try several things on that to see if I can fix it, so if you upload it I would be very thankful
davidnintendo said:
Could you please upload that booting rom? I tried it and it won't even install. Even if nothing works, I would like to try several things on that to see if I can fix it, so if you upload it I would be very thankful
Click to expand...
Click to collapse
Take a working Rom for zte, and replace everything except build.prop and meta-inf folder
Sent from my LG-P500 using xda premium
FezzFest said:
ICS on the Blade is booting!
But that's all it does
I used this ROM and replaced boot.img with CM N257. In the honeycomb port they fixed the flipped screen with patching libsurfaceflinger.so on offset 1AC90 but that does not work on ICS. Launcher FC's on first boot but does not after reboot.
Click to expand...
Click to collapse
So correct me if im wrong, but you got ics booting on blade by using the g2 rom and boot.img from CM7 Latest nightly?
If so maybe start a new thread to track progress.
furrabbit.nh said:
So correct me if im wrong, but you got ics booting on blade by using the g2 rom and boot.img from CM7 Latest nightly?
If so maybe start a new thread to track progress.
Click to expand...
Click to collapse
LGP500 got bootloop on that, but thats our phone, so thats maybe work yes
SWEATTAIMI said:
LGP500 got bootloop on that, but thats our phone, so thats maybe work yes
Click to expand...
Click to collapse
I just tried it 10mins ago, it installs fine does not boot at all, no logcat output... Wonder if he/made any tweaks elsewhere.
I have a O1 somewhere might dig it out, and have a look
I got it booting! Screen is fliped, touchscreen doesn't seem to work at all and I couldn't test anything else because I can't press OK on the first tutorial screen, but it may be something to start with!
I'm uploading it right now, but I think it will take a while as my connection isn't working very well right now, but I'll post the link as soon as it's finished.
EDIT: OK. You'll have to be patient. Apparently, my 20 MB symmetric shared connection doesn't want to upload faster than 50 KB/s. It's always like this in the afternoon: too many people using it LOL. Hopefully it will be uploaded in 25 minutes or so.
davidnintendo said:
I got it booting! Screen is fliped, touchscreen doesn't seem to work at all and I couldn't test anything else because I can't press OK on the first tutorial screen, but it may be something to start with!
I'm uploading it right now, but I think it will take a while as my connection isn't working very well right now, but I'll post the link as soon as it's finished.
Click to expand...
Click to collapse
Thanks
Sent from my LG-P500 using xda premium
OK, fixed flipped screen & resolution. Thanks to smg22rus for the modified libsurfaceflinger.so.
Flashable ROM (for devs only!) can be found here
If you fix something, just post what you did to get it fixed, do not upload the whole ROM again.
That way, this thread stays clean & we have only one ICS ROM (not 10 different ones).
How would ROM deving work for this type of phone where people choose their own specs?
now that i think of it, how would there be updates either? its like a one and done process. so if you buy the phone, you'll stay on the Android version that comes preloaded
I am thinking towards windows kind of update model but free this time.
Only thing is can we modify Linux kernel for enough flexibility.
NaveenKumarXDA said:
I am thinking towards windows kind of update model but free this time.
Only thing is can we modify Linux kernel for enough flexibility.
Click to expand...
Click to collapse
Might be able to work if the MDK enforces a unified modular structure. And extra parts of ROM's would target some v heavy/popular modules.
I think you ubuntu may be the way to go.
Since my knowledge is really limited, if Google and manufacturers cooperate for open-hardware and open-source environment, it will be like installing drivers on a new OS. So everyone can use latest version of Android. Am I right or really really wrong?
Sent from my GT-I8190 using XDA Premium 4 mobile app
I could imagine an official update method in which the used modules are recognized and the update fits perfect to that phone or the modules have anyhow universal usable drivers stored on themselves while you can change them without re-flashing the entire rom.. what do you think?
Surely if all the componets are made by the same manufacter the roms would be universal but with some roms being heavier for the powerfuller phones and lighter for cheaper phones
It will be harder. There will be bloated kernels that account for unused modules. Likely to be devs that tune to a specific hardware set [their's], etc. But w/ a diy modular phone, they'll probably be no shortage of developers.
A cooler way would be to enable more run as module on kernel and have each module self-load its drivers [like plug-n-play]. This could avoid the kernel bloat I aluded to earlier.
Rob
insink71 said:
A cooler way would be to enable more run as module on kernel and have each module self-load its drivers [like plug-n-play]. This could avoid the kernel bloat I aluded to earlier.
Rob
Click to expand...
Click to collapse
I agree with this, or maybe if the system can build the driver files on startup or installation. but then you will be looking at stall's and system freeze if it's interrupted. (just mentioned something similar in another post lol!):fingers-crossed:
If the bootloader can report the serial/models of the components, the kernel can turn on and off what's needed or not. From there yes, there will be a ****ton of modules to compile even if half aren't used. We can also expect to see hybrid kernel drivers doing different things based on some data returned by the actual component (e.g. 16GB vs 32GB storage) -- assuming those components work the same.
Maybe they'll make a new OS for this, kinda like Windows OS. It's supposed to be universal, no matter what kind of parts are installed.
The rom devs can list the minimum specs for the rom so the user has at least the minimum for the rom
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Nope, it is said that you can change modules on the fly. Maybe there are just drivers in the plug in that are loaded first...
Maybe the compatibility to drivers coves with android 5.0?
Regards
Gesendet von meinem C6503 mit Tapatalk
as people have said this wont be common outside the custom pc type market and if it don't support android in some from whether that be via a custom rom and recovery like cwm/twrp it will be a massive flop
i cant see why it cant come with a option that has cwm installed with a rom,them its attractive to coders
I really hope that they have the option for sales of just the outer shell. Then, people like me can custom select whatever they want without having to waste the stock modules which would then be rendered useless.
i hope they make a rolling system similar to how its done by Arch Linux where you start with just a base and let the owner select his own modules or let the user make their own module. that would be fantastic! i mean perfect!
pandasa123 said:
How would ROM deving work for this type of phone where people choose their own specs?
now that i think of it, how would there be updates either? its like a one and done process. so if you buy the phone, you'll stay on the Android version that comes preloaded
Click to expand...
Click to collapse
I think there will only be ROMs for certain phone combinations
Sent from my ultimately bumped up LG-P700 running CM11
The modularity will be programmed into the OS. Wether that part goes open source or not is another question.
Gesendet von meinem XT1039 mit Tapatalk
all parts will be class compliant iirc, meaning each new OS/rom only needs have generic drivers, anything that isn't class compliant needs to carry its own drivers, i could be wrong but im sure thats what he said in the interview with the first working spiral 1
I may be a bit crazy in thinking this.
But I'd LOVE project ARA and Cyanogenmod to partner and have their CM OS on the ARA modular phones. Imagine we could have theme chooser on the device. And customise it exactly to our liking.
inside and out in this case.
But alas it's only a pipe dream.
this includes the kernel source. I am in the process of trying to build a gpe kernel. so far I can get into the menu config but cannot make successfully. I'm going to download a different distro with a clean build environment and try again. If anybody else has ideas and/or answers on how to do this successfully please post here.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv510
my attempt to build a kernel will be to allow for gamma correction and for the addition of ext2 to used on the SD card if possible. I have built kernels for my Linux box before but this is quite a bit more involved.
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Canadoc said:
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I don't know enough about it yet. one would think that with the source code you could simply build and install GPE on to the framework of the LGE device, meaning the removal of all of the old software in the installation of all new software based on the GPE Kit Kat build.
Apparently, by reading other threads here that is not the case, or they would have already done so. Then again, I did not see anything posted about the source code before now.
Maybe a developer will decide to do something with this, and even better write a tutorial on how to do something that is worthwhile for the GPE. In the meantime I will muddle through.
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Demetris said:
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Click to expand...
Click to collapse
howdy, I like your idea, but I would also like to see more development for the GPE itself. maybe even a separate forum dedicated just to the GPE as right now it seems that everything is spread out, disorganized and very difficult to keep together for one or the other version. Upon this basis it would be easier to see what items and options are available for one device, without being distracted by the same for the other.
That being said, I definitely agree there should be a collaboration to achieve the ends that you desire, as they will also help the GPE users find what they are looking for.
was I able to successfully compile a kernel? Yes! Yes I did!! Arch/arm/boot/zimage is ready!
unfortunately this does not mean an awful lot of this point all I did was change the name of the kernel slightly and if not adjusted anything else nor do I have it back into a boot image but! This is/was the hardest part I think. Reason being the dependencies for getting this done.
I have successfully compiled, and pushed a kernel onto my gpad gpe 510. Now you can too! I wrote a tutorial at : http://forum.xda-developers.com/showthread.php?t=2628951
You will be able to control your device now. No need for a custom ROM if your willing to put in a bit of effort, but I understand if you dont.??
I don't know if it's in the correct section (move this thread wherever is appropriate, and sorry for that)
Guys, miui based on MM are out, i understand that patchrom is still 4.4.4, but there's no other way to port it without using it?
Thanks
Sent from my Nexus 6P using XDA-Developers mobile app
CappyT said:
I don't know if it's in the correct section (move this thread wherever is appropriate, if no...
Guys, miui based on MM are out, i understand that patchrom is still 4.4.4, but there's no other way to port it without using it?
Thanks
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
PathROM was designed to help porting MIUI to devices. I used it 3-4 years ago for porting MIUI to my LG P500. A developer/user could definitely go the manual way, but it would be mess.
Anyways, why do you need MIUI on your 6P? I have had a nightmare using MIUI. And last I used was on the Nexus S.
DJBhardwaj said:
PathROM was designed to help porting MIUI to devices. I used it 3-4 years ago for porting MIUI to my LG P500. A developer/user could definitely go the manual way, but it would be mess.
Anyways, why do you need MIUI on your 6P? I have had a nightmare using MIUI. And last I used was on the Nexus S.
Click to expand...
Click to collapse
Well, i just like it more than i like cyanogen or other roms... Also has awesome themes and i like the design of the rom.
I understand that is not maybe the best rom for modding or battery usage, but still a great looking rom.
Sent from my Nexus 6P using XDA-Developers mobile app
CappyT said:
Well, i just like it more than i like cyanogen or other roms... Also has awesome themes and i like the design of the rom.
I understand that is not maybe the best rom for modding or battery usage, but still a great looking rom.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I can definitely agree on that point. Let us hope someone ports it.
Isnt there a miui v7 for nexus 5? Not sure about 5x, but definately should be possible, just dont think that devs are interested in miui
feis said:
Isnt there a miui v7 for nexus 5? Not sure about 5x, but definately should be possible, just dont think that devs are interested in miui
Click to expand...
Click to collapse
Exactly. Only a few people care for MIUI now.
DJBhardwaj said:
Exactly. Only a few people care for MIUI now.
Click to expand...
Click to collapse
If i get a guide or something to port it manually, i can try to, but i'm finding only patchrom guides...
Sent from my Nexus 6P using XDA-Developers mobile app
CappyT said:
If i get a guide or something to port it manually, i can try to, but i'm finding only patchrom guides...
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
3rd post in this thread would help - http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
When I started with MIUI port, we didn't had patchrom anyway near, so we followed something like this.
DJBhardwaj said:
3rd post in this thread would help - http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
When I started with MIUI port, we didn't had patchrom anyway near, so we followed something like this.
Click to expand...
Click to collapse
I may use some help here...
I extracted everything that is necessary and I have copied over the files, how to symlink everything together again? I'm using windows, I suspect I should use linux and extract everything there, right? Or there is any android kitchen (that support 6.x) that helps with this?
Many thanks
CappyT said:
I may use some help here...
I extracted everything that is necessary and I have copied over the files, how to symlink everything together again? I'm using windows, I suspect I should use linux and extract everything there, right? Or there is any android kitchen (that support 6.x) that helps with this?
Many thanks
Click to expand...
Click to collapse
I remember using a script from one of the developers, not sure who or when, or would have found it for you. Give a swipe on XDA for Android Kitchens that could help. I am sorry that I am not able to help much here.
DJBhardwaj said:
I remember using a script from one of the developers, not sure who or when, or would have found it for you. Give a swipe on XDA for Android Kitchens that could help. I am sorry that I am not able to help much here.
Click to expand...
Click to collapse
Thank you anyway, you helped me a lot =)
Oh man if you succeed im gonna donate my cat to you lol
CappyT said:
Thank you anyway, you helped me a lot =)
Click to expand...
Click to collapse
I guess its not going too well?
feis said:
I guess its not going too well?
Click to expand...
Click to collapse
I just need a little time and a little help with this...
Wish you luck! Would love to have miui for a change, sadly cant help you much, since im a noob when it comes to this
CappyT said:
I just need a little time and a little help with this...
Click to expand...
Click to collapse
I'm dont really know anything about porting ROMs, but if you tell me what you're having issues with I can try to help in finding the solution. Willing to do anything I can to help out
Sent from my Nexus 6P using Tapatalk
Thank you guys, I will use your help.
Today I will look into it, for the moment i'm still figuring out how to keep symlinks and permissions on windows, but i guess it's impossible. I will try firing up a vm with nix if everything fails.
Ok, so... I made a system and boot img, but I didn't tested those, and I can't get the updater-script to work. If someone helps me with this, I will be really thankful.
The permissions and symlinks part is something that worries me, but I keeped the symlinks and permission from original system.img filesystem by mounting it as a drive in linux and applying mods there.
Also, I keeped every part of the symlink script that camed with miui, so it should tecnically work.
If some of you guys helps me testing this, we can do it.
**** WARNING. IT CAN DAMAGE YOUR DEVICE AND AT THE MOMENT, IT DOESN'T WORK!!! ****
Here is the rom: https://mega.co.nz/#!b90GSJRa!7rXM2UhwtEw8M0fbIrK2F3za9w5KTGY1FPD4IGmHu1k
It was ported from the Mi Note (not the pro) which has really similar specs to our device, and this version also includes an italian translation (so there are 3 langs, English, Chinese and Italian)
No ones helping? I really wish i could help you with the testing but as i dont have computer access right now dont wanna brick my 6p without being able to repair it without pc.
Ok, i managed to get the rom flashed... So. The boot image seems almost fine, since i got to the bootanimation screen. There, it stucks.
I don't know how to debug it, since the adb doesn't show up (and is active in kernel)
I activated adb by the use of:
Code:
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=1
persist.service.debuggable=1
in the kernel default.prop... I don't know if these lines are outdated, but i'm still trying guys.
Also, you can reach me out on hangouts at: cappy95(at)gmail.com