yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rrryan2:
The 4.2 keyboard does allow swiping, but I found the accuracy to be well short of Swype. The voice integration was better though.

I've bought and tried Swiftkey, just can't seem to learn to love it and always come back to Swype. When it hit the Play store for $0.99 it was a no-brainer for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Capa1970:
Well, I got the Google 4.2 keyboard and I have been messing around with it a couple of days and I am really impressed. It just might be my favorite keyboard but I'm going to wait a week or two for my final verdict. I love gesture typing/tracing/swyping and own both Swype and Swiftkey. A couple of points:

---The voice integration is superior on Google's keyboard.

---I love the fact that when I restart my phone that Google's keyboard is still the default keyboard. The same cannot be said for Swype and Swiftkey (I realize that rooted phones can circumvent this inconvenience).

---So far I'm finding the Google keyboard to be the most accurate swyping-wise. Normal tap typing accuracy would have to go to Swiftkey.

---However, when it comes to themes the Google keyboard is sorely lacking whereas the two other competitors aren't. Also, both Swype and SwiftKey have secondary symbols on the main keyboard that can be accessed by simply pressing a little longer on the different keys. The Google keyboard, like Apple's, doesn't. I have to hit the number key to get most of those symbols :(

---the Google keyboard is free!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ohmna:
I've been using the swype beta for a couple years now and really like it. The 4.2 android KB is okay for swiping but I like how the keys are closer together in swype and I find the accuracy better in swype. I have never had the issue with the default KB changing after reboot though I haven't tried the official release. Currently on the newest Slim Bean ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] accrews2001:
Default issue doesn't happen with side loading. Only when downloading from the play store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NyceHS:
Is it better than the "swipe" type setting built in the google keyboard??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rrryan2:
Sheesh. Scroll up 3 posts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NyceHS:
My apologies, I'm using public WiFi that SUCKS so I'm trying not to load pages if I dont have too, so I only read the first page. Again my bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexa1:
On my Nexus 4 (stock 4.2.2) Swype stays default keyboard after phone reset just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chilln09:
Swype text prediction is just about as good as swiftkey now.

It really is an amazing product.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I don't know, maybe you guys aren't understanding the guys question. There is already a version of Swype on our STOCK ROM. He wants to know if the one on Google Play is any better than the version already on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rrryan2:
They're fairly similar overall in my opinion. There are some features though like cloud sync for dictionary, which is helpful if you have multiple devices.

I don't remember the one included with stock to have predictive text either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akj_1989:
I'd like to add here, the new version on the play store has been release after extensive beta testing. While the one on our stock ROMS is based on an older version.

I've been on the beta test program for long, and it's the best keyboard I've found (after trying SlideIT, Swiftkey, Google etc).

Just now I realized (by reading the thread!) that the official updated version has been released, and bought the app straight away!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] breeze1000rr:
I'm not sure yet but it seems as if I lose my added words in the dictionary when I restart. The purchased Swype that is,,,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ezwalker63:
I beta tested Swype for 2 years then purchased the app from the Play Store last week. I signed in the app with the same email address from the beta version and all of my saved words were there. I didn't lose a thing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ISperfection:
yes Swipe!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigun66:
Agree with all of this - I used Swype quite a bit before the Google keyboard support "swiping". The thing that bothered me most was the different voice recognition engine. I have had better luck with Google's built in voice recognition. I'd suggest trying the Google keyboard first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingsway8605:
Only reason I don't use Swype is because it makes you use dragon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Valiante:
They need to have two finger swype like keymonk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gc84245:
Love the predictions, but caused way too many wakelocks and killed my battery so I had to uninstall :(
[Samsung Galaxy S (4G Model)] getochkn:
So I managed to get wifi working with 4.2.2, but it's a bit clunky and manual and I have no idea why it works, but it does.

ROM here.

So for now since Beast is busy this week, anyone who wants working Wifi with this can do the following.

*Download the attached script and put it on the root of your SD card.

*Install Script Widgets and Script Manager (going to need to use a few mb of data for this, download from another ROM and save the apk's to offline install, or use the manual steps above to get wifi working at least once)

*Start up script manager and navigate to the wifiscript.txt file from the above step, click on it, it will open a window. Click SU and Boot and then click save. This will set the script to run at boot up.

*Go to your home screen, add a widget to the Script Widget, set it to run your wifiscript.txt

*click on it, it will start and run. exit out of the widget, go to wifi setting. you should see your access points. Click on the one to connect to, enter password and make sure to choose automatically connect. It won't connect yet

*Go back to your home screen, run the widget shortcut again, it should connect. Anytime you want to switch AP's that you are connected to, you will need to run the widget shortcut again.

*Reboot your phone, let it fully boot, your wifi should be connected to your AP.

I offer no support here, don't clutter up the dev thread with anything about this. I know the junkies out there want something to flash and want wifi to play with this.
[Samsung Galaxy S (4G Model)] hechoen:
Nice find man. You might be able to just add the script to an init.d file and have it work from boot. I'm busy fixing some gallery issues on my rocket so if you have time to try it would be great.
[Samsung Galaxy S (4G Model)] getochkn:
I tried in the init.d, even at 99 and it runs too soon to be executed. That was my first thought. Not sure how to set it to run once you're like at the lock screen, and not the slimrom logo time, then I could set it there but couldn't find a way, so the script manager works out good. The widget also works out great if you switch AP's like lots of people do. It's only a few extra taps and gives you control when to run the script so can kick your wifi back in to gear if you need to.

Something for now anyways............

If you talk to beast, tell him to check out the thread and see if he knows why it's doing it. I posted some of my other findings in the dev thread.
[Samsung Galaxy S (4G Model)] hechoen:
Yeah I saw the dev thread. I'll let him know but he's pretty good at checking in. At least the drivers built correctly. Oh and sorry about quoting the whole OP. lol
[Samsung Galaxy S (4G Model)] Vismis:
:blowjob: is virtual but that and a thumbs up is all i can give you
[Samsung Galaxy S (4G Model)] Fluidification:
no vismis, please keep it PG.
[Samsung Galaxy S (4G Model)] Vismis:
Check out the bottom of this post

---------- Post added at 10:04 PM ---------- Previous post was at 09:45 PM ----------

Any kid playing around on XDA has already learned far more on the internet then just blowjobs BTW :cool:
[Samsung Galaxy S (4G Model)] FBis251:
Try adding sleep before the netcfg command

sleep 30

netcfg blah blah

It'll make the script wait 30 seconds before executing the rest of the script.

That's odd that it works out that way. Can you show me the output of netcfg with no arguments? ICS shows me this:

When booted after wifi toggle was off:

root@android:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 2e:f9:39:dc:db:fb
ifb1 DOWN 0.0.0.0/0 0x00000082 82:b6:22:43:a0:df
gannet0 DOWN 0.0.0.0/0 0x00001082 b6:55:4b:d2:2f:db
usb0 DOWN 0.0.0.0/0 0x00001002 96:e2:9e:da:43:3c
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

When wifi is enabled:

root@android:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 2e:f9:39:dc:db:fb
ifb1 DOWN 0.0.0.0/0 0x00000082 82:b6:22:43:a0:df
gannet0 DOWN 0.0.0.0/0 0x00001082 b6:55:4b:d2:2f:db
usb0 DOWN 0.0.0.0/0 0x00001002 96:e2:9e:da:43:3c
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 192.168.1.9/24 0x00001003 b4:07:f9:44:42:19

When wifi is disabled again:

root@android:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 2e:f9:39:dc:db:fb
ifb1 DOWN 0.0.0.0/0 0x00000082 82:b6:22:43:a0:df
gannet0 DOWN 0.0.0.0/0 0x00001082 b6:55:4b:d2:2f:db
usb0 DOWN 0.0.0.0/0 0x00001002 96:e2:9e:da:43:3c
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 0.0.0.0/0 0x00001003 b4:07:f9:44:42:19
[Samsung Galaxy S (4G Model)] Dwack:
Turning wifi on and off would require us to run the widget command again?
[Samsung Galaxy S (4G Model)] Fluidification:
I'm just playing lol.
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi Dwack

from what I understood it is required only before registering a specific AP for the first time.

Therefore if you simply open and close on a known network, script is not needed.
[Samsung Galaxy S (4G Model)] getochkn:
If you add it to the bootup as I said, and you connect to an AP already saved in your list with the password, you shouldn't need to run it, but you might. It's not a perfect system or the end all fix for it, simply a tempfix for the junkies, but more importantly to show Beast that his drivers work fine and wifi can work, scan, and stay connected so hopefully that point him in the right direction of if it's a kernel thing, system thing, or what. I don't know to be honest. I'm surprised I got this to work, I'm not a linux guy by any means. I get all screwed up over permissions every time and folder owners and all that jazz. This was like a rainman type of find for me. lol.

FB. Cold boot without the script running but wifi on gives.

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 be:17:b3:a2:d9:f9
ifb1 DOWN 0.0.0.0/0 0x00000082 ae:af:e5:5a:52:70
gannet0 DOWN 0.0.0.0/0 0x00001082 4e:05:c6:59:ad:75
usb0 DOWN 0.0.0.0/0 0x00001002 82:bf:75:80:f3:6b
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 0.0.0.0/0 0x00001003 50:cc:f8:f0:69:4f

But it won't connect so the eth0 is up, but not connecting.

when disabling the wifi button

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 be:17:b3:a2:d9:f9
ifb1 DOWN 0.0.0.0/0 0x00000082 ae:af:e5:5a:52:70
gannet0 DOWN 0.0.0.0/0 0x00001082 4e:05:c6:59:ad:75
usb0 DOWN 0.0.0.0/0 0x00001002 82:bf:75:80:f3:6b
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

Enabling the button

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 be:17:b3:a2:d9:f9
ifb1 DOWN 0.0.0.0/0 0x00000082 ae:af:e5:5a:52:70
gannet0 DOWN 0.0.0.0/0 0x00001082 4e:05:c6:59:ad:75
usb0 DOWN 0.0.0.0/0 0x00001002 82:bf:75:80:f3:6b
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 0.0.0.0/0 0x00001003 50:cc:f8:f0:69:4f

Running the netcfg eth0 down

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
svnet0 UP 0.0.0.0/0 0x000000d1 a0:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 be:17:b3:a2:d9:f9
ifb1 DOWN 0.0.0.0/0 0x00000082 ae:af:e5:5a:52:70
gannet0 DOWN 0.0.0.0/0 0x00001082 4e:05:c6:59:ad:75
usb0 DOWN 0.0.0.0/0 0x00001002 82:bf:75:80:f3:6b
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 192.168.1.119/24 0x00001003 50:cc:f8:f0:69:4f

I don't know why telling it go "down" actually keeps it up and it locks on within a second to my AP as you can see, I have an IP address now.

Again, I have no reason why it works, just hope Beast or someone can and maybe Beast can stop going crazy chasing other libraries or worried about his drivers, because it works fine once you do that command. Going back in wifi settings though and it connects and disconnects, so something is so close to working, it's there.
[Samsung Galaxy S (4G Model)] Vismis:
My bad ^_^
[Samsung Galaxy S (4G Model)] Iamaninstructor:
Working as advertised. Tkx geto! Nice step-step. Easy.
[Samsung Galaxy S (4G Model)] dgmoodey:
Random Wifi Shutdowns

I know this is only a temporary fix, but my Wifi seems to disconnect randomly... Here is a logcat

Google Now and some other services shut down WiFi
[Samsung Galaxy S (4G Model)] getochkn:
What was the problem?
[Samsung Galaxy S (4G Model)] dgmoodey:
Acutally, I wasn't able to make it work... When I open up the Google Search app, the Wifi immediately shut down and would not start right... This also happens with some other Google services.

After even rebooting phone, the WiFi stays up for 3-4 min, then shuts back down... Its strange

Also, after long periods of inactivity (10 min lol) the WiFi sleeps due to the inactivity and will not start unless the script is run again.
[Samsung Galaxy S (4G Model)] Fluidification:
I guess that i will have to install jb 4.2 now.
[Samsung Galaxy S (4G Model)] getochkn:
That's why it's proof on concept. lol. I ran into it crashing after install the AIO slim apps and adding all the google apps in. Not a daily driver by any means. GPS doesn't work, no videos play, etc. It was just to show Beast that wifi works and maybe get any other devs looking into it or knowing, hey, I had that problem on a ROM and it was this file, etc. I was in way over my head when I decided to even try as I had no idea what I was doing. lol.
[Samsung Galaxy S (4G Model)] dgmoodey:
Well you sure as heck did an amazing job by making Beast's job a hell of a lot easier! Really nice job with it :D

I think that we should have a working ROM by the end of this month, hopefully
[Samsung Galaxy S (4G Model)] Fluidification:
i think it's my turn to look into the gps prob.

Can people pm me loads of gps crud?
[Samsung Galaxy S (4G Model)] CSP III:
Great job so far devs and the like. You guys are all awesome. Hell of a job. Hang in there, you're making it happen. Thank you so much for even working on this great phone.
[Samsung Galaxy S (4G Model)] turtlepa:
Basically netcfg is like ifconfig in linux with its option/switches being like ifup eth0, which is respectively the same as ifdown eth0. Leaves same arguments. When u look a different filtered logcat and dmesg, seems like this would eventually just be config to get wifi maybe with something extra. Thanka guys for the temp fix. I will work on this
[Samsung Galaxy S (4G Model)] getochkn:
Ya something is so close, yet a bit wonky. Certain google apps seem to kill the wifi, etc. Yesterday though on a clean install, I was connected to wifi for about 10hours straight with no issues and still 30% battery left using airdroid to remote into it.
[Samsung Galaxy S (4G Model)] suck it monkeys:
How to access root

morning,

I have tried cutting and pasting txt file into root. but I cant get it to stick. any ideas
[Samsung Galaxy S (4G Model)] getochkn:
The root of what? It should just go on your SD card.
[Samsung Galaxy S (4G Model)] bullriders:
Good Job

Great Find.

Worked great running Slim Bean 4.2.2 on GS4G
[Samsung Galaxy S (4G Model)] suck it monkeys:
thanks, I will try the recommended set up. I thought it had to go in the root of the SD card. and yes I it the button. Awesome work
[Samsung Galaxy S (4G Model)] Dwack:
"root of the SD card" simply means it has to go on the SD card, but cannot be inside of any sub-folders.
[Samsung Galaxy S (4G Model)] getochkn:
It can be anywhere you want it, I just tried to make it simple. You can mount the system file system as writeable and push it right to the device, us ES file manager in root mode and do the same thing, make a folder on your SD card called /scripts/slimbeam/4.2.2/wififix/ if you want. As long as you use the script manager and point to wherever it is, it's fine.
[Samsung Galaxy S (4G Model)] suck it monkeys:
Its alive!!!!

took me a bit to figure it out. thanks for the help getochkn and Dwack. click the button
[Samsung Galaxy S (4G Model)] suck it monkeys:
logcat for wifi

It works great, I attached a log going from start screen/settings/wifi settings/and back to start screen. As getochkn said it acts a bit weird while you do that but once back home screen it reconnects
[Samsung Galaxy S (4G Model)] suck it monkeys:
GPS

GPS Crud log
[Samsung Galaxy S (4G Model)] bullriders:
Nice

Good Job. Sometimes the WiFi just drops out, but If I click on the Widget and run the script it reconnects quickly.
[Samsung Galaxy S (4G Model)] Fluidification:
I am sure I know what the GPS issue is, so I might have a build up this weekend. My mom didn't let me do anything on Sunday which is why I still don't have a build up.
[Samsung Galaxy S (4G Model)] turtlepa:
I guess next we should try for a temp or perm video fix, seeing that cm7s latest kernel and release 9.1 has borked video there as well
[Samsung Galaxy S (4G Model)] Vismis:
Is this working with new update i can't seem to get it to work on the be update anyone else having the same problem?

Nm I'm a idiot
[Samsung Galaxy S (4G Model)] getochkn:
So it does work on CM10.1 then is what you're saying?
[Samsung Galaxy S (4G Model)] Vismis:
Yea lol rofl i wanted it to be slim so bad i never read the title just flashed i even flashed slim gapps lol
[Samsung Galaxy S (4G Model)] turtlepa:
In init.d try making it sleep 30 then do the netcfg command then sleep 10 then the netcfg command again
[Samsung Galaxy S (4G Model)] pisherthefisher:
Would it be possible to make this script automatically run everytime WiFi disconnects with tasker or a similar app?
[Samsung Galaxy S (4G Model)] Beastmode:
Can someone using this grab me a log startjng from when you turn on wifi to when u connect to your router?
[Samsung Galaxy S (4G Model)] pisherthefisher:
Here you go. I started out with WiFi turned off, I turned it on then ran the script to connect. This is on beanstalk

http://db.tt/rJiPbMFZ
[Samsung Galaxy S (4G Model)] Fluidification:
I am porting BCMDHD from aries!

Building right now, so let's see what happens.
[Samsung Galaxy S (4G Model)] FBis251:
Instead of mka bacon run mka bootimage. Don't forget to clobber.
[Samsung Galaxy S (4G Model)] Fluidification:
i also need to build the rom, so I am making bacon.

---------- Post added at 11:08 AM ---------- Previous post was at 10:33 AM ----------

i got a last minute error so it didn't build the module:(
[Samsung Galaxy S (4G Model)] Beastmode:
I had that issues when porting bcmdhd myself it would get to where the module was about to be spit out and I got the error
[Samsung Galaxy S (4G Model)] Fluidification:
i'll look into it.

I'm just bulding the bootimage

---------- Post added at 02:24 PM ---------- Previous post was at 01:26 PM ----------

Do you have any insight as to what's going on?

---------- Post added at 03:17 PM ---------- Previous post was at 02:24 PM ----------

time for me to work on aries kernel.

Maxman is right, this is too frankenkernel.
[Samsung Galaxy S (4G Model)] FBis251:
Try to keep what you're working on small. It's easier to debug one thing rather than a whole kernel port. Posting the make error messages will help. It's harder to see if you run mka first since it uses multithreading so run

mka bootimage

Let it error out

make bootimage -j1

That'll only compile using one thread which is slower, but you'll be able to see what the error was. Hopefully the error message will include line numbers and file paths to make it easier to debug
[Samsung Galaxy S (4G Model)] noiphonehere:
It just so happens I isolated the cause of the Sleep of Death earlier this afternoon.

The config needs to contain

CONFIG_FIQ_DEBUGGER=y

Then, the SoD does not occur - at least, not for me.

Looking at your GitHub, I see you have reworked the config to include this, so you shouldn't have any trouble with that.

Also, I fixed call audio, on my phone anyway. I've tried to attach my patch, but I'm a noob so we'll see if it lets me... :D

Oh yeah, I'd better warn you: I've had plenty of weird radio issues with Aries (Airplane Mode is wonky, and I seem to be having issues enabling 2G-only mode). I'll try to get a log of it. :p
[Samsung Galaxy S (4G Model)] noiphonehere:
OK, here are a couple of logs from Aries. In the future, I'll post about Aries in the cm9 Q&A, since that's the most relevent thread it'll let me post in.

Airplane Mode sometimes works, but sometimes it sticks. It might just be my phone, but here's a log anyway.

2G mode took me two attempts to get working. The first time, it just undid the setting after I left the menu.

This is on 3.0.8, since that is what I have been working on.

Hope this is helpful.
[Samsung Galaxy S (4G Model)] Fluidification:
I am compiling right now.

But I am working on cm10.1
[Samsung Galaxy S (4G Model)] FBis251:
Dude! Do you know how to use github? Do you have an account? If so you can also try submitting some pull requests to the team acid kernel

https://github.com/teamacid/android_kernel_galaxys4gmtd

EDIT

If you have your own account that works for me too! We haven't had too many people posting source for working fixes lately.
[Samsung Galaxy S (4G Model)] Fluidification:
HAHA.

LOL.

HAHA.

LOL.

There was a fix sitting here for so long???? AND Max was frantically abusing rtc?

ANYWAYS,

Could I have some help if someone were to check my source?

:2: error: implicit declaration of function 'S5PV210_GPHI' [-Werror=implicit-function-declaration]
/Volumes/android/cm/kernel/samsung/aries/arch/arm/mach-s5pv210/dev-s1-phone.c:79:2: error: initializer element is not constant
/Volumes/android/cm/kernel/samsung/aries/arch/arm/mach-s5pv210/dev-s1-phone.c:79:2: error: (near initialization for 'mdmctl_data.gpio_cp_reset')
/Volumes/android/cm/kernel/samsung/aries/arch/arm/mach-s5pv210/dev-s1-phone.c:81:2: error: implicit declaration of function 'S5PV210_GPIO' [-Werror=implicit-function-declaration]
/Volumes/android/cm/kernel/samsung/aries/arch/arm/mach-s5pv210/dev-s1-phone.c:81:2: error: initializer element is not constant
/Volumes/android/cm/kernel/samsung/aries/arch/arm/mach-s5pv210/dev-s1-phone.c:81:2: error: (near initialization for 'mdmctl_data.gpio_int_resout')
cc1: some warnings being treated as errors

make[3]: *** [arch/arm/mach-s5pv210/dev-s1-phone.o] Error 1
make[2]: *** [arch/arm/mach-s5pv210] Error 2
make[1]: *** [sub-make] Error 2
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....

EDIT I THINK I FIXED IT