yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8erwitskil:
so here is a touchpad kernel for cm9 that i have on my touchpad and works great: http://xdaforums.com/showthread.php?t=1454963

the github that the source is in is here:

https://github.com/showp1984

the kernel is called 'bricked-kernel'....maybe there is some useful stuff in there.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Thanks, I'll take a look at this later tonight.... I'm guessing it will help in one way or another.

Sounds good with the dd idea, keep us updated on the results.

I really don't want to talk about xboarder anymore on this thread. Like you said, he obviously doesn't want to contribute, so let's stop twisting his arm.

In other news, here's a link to (theoretically) updated boot.img if anyone wants to give it a whirl.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jim93:
It sounds like he will release source and his ROM post are more open in attitude and function. Its not like his thread will be

[ROM] Evolver 4.0

Kangers beware. Everyone else is a clone. 50k+ downloads.

Like others ROM threads have been.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jayharper08:
I think it's pretty obvious why this thread got closed for a bit. I will say this once and once only, if I see anymore flaming, bashing, etc. on one another, there will be consequences. I don't care if you are a noob, a moderate user, senior member or an "RD", or how many "thanks" you have it will not be tolerated. Simple as that. If you have nothing to provide worth while in this thread and it's not about building, then DO NOT POST. That goes for new threads started about this also. It's done and over with. Thread re-opened for now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] DANIEL133337:
There is another source apart from CM9 that also may help, AOKP! ClassicNerd is about to release a source for the TouchPad. It may help build a device tree for our device due to having the same chip. Who knows though, their Github is on this thread and a mini tutorial for compiling.

http://xdaforums.com/showthread.php?t=1485861
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] topprospect:
Here is my latest status on building the Code Aurora Gingerbread branch with proprietary blobs:

It boots!

UI is still very sluggish; maybe because this is an ENG build?

What works: display, touch input, lights, buttons, accelerometer, wifi

What doesn't work: radio, audio, internal and external sdcards, usb mass storage, wifi hotspot, nfc, camera, bluetooth, and anything else you can think of

Again, I am using Da_G's 0.3 kernel so that I can focus on getting a good device tree for Skyrocket.

Since I have been hacking the image, I am going to rebuild, make sure I can get a clean zip, and then I'll post a link. I will also update my GitHub with the latest device tree changes. Look for a post later tonight.

I need some help getting the radio going though. In the radio logcat I get the following message repeated over and over:

E/RILQC-QMI( 228): linux_qmi_qmux_io.c: Unable to open port id /dev/sdioctl0

sdioctl0 does not exist under /dev. It is also referenced in /ueventd.rc so it seems like it should exist. Does anyone know why it wouldn't? What puts it there? The kernel? /system/bin/ueventd?

EDIT: Found out why /dev/sdioctl* didn't exist. /system/bin/ks was missing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] trinikartel:
I've been following for a few days now and just stumbled across this today

http://xdaforums.com/showthread.php?t=1494847

ICS for the Sprint SGS2

not sure if it would help but have a look anyway
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] pfer10:
Totalty different device only shares the name and screen size I think. The SGH-I727 and SGH-T989 are the same. (Skyrocket and Hercules)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] orlandoxpolice:
Don't forget the I957!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] pfer10:
Doesn't that have the Tegra?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8erwitskil:
yep sure does. here is a link to all the devices that share the same cpu. http://pdadb.net/index.php?m=cpu&id=a8060&c=qualcomm_snapdragon_apq8060 scroll down on that link and click "browse all devices based on snapdragon APQ8060"
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] pfer10:
Pantech in the house!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] orlandoxpolice:
I know for a fact that the galaxy tab 8.9 LTE (SGH-I957) has a qualcomm chip.

http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00045037&fm_seq=45639

Android System Info App also shows the MSM8660 board.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] pfer10:
Any AOSP threads? ICS?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8erwitskil:
yah you are right. the samsung site shows it as qualcomm but here it says nvidia.

http://pdadb.net/index.php?m=specs&id=3214&c=samsung_sgh-i957_galaxy_tab_8.9_4g_lte_64gb

i would believe the samsung site over pdadb.net anyday tho. :-)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] orlandoxpolice:
We have no devs lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] topprospect:
Gingerbread built from source, build 11

Here is my latest build (#11) of the Code Aurora Foundation Gingerbread msm8660_surf target. This one is important since it is the first build using proprietary blobs (QC_PROPS=true).

Link to the CWM installable zip: http://dev-host.org/5eQ

Link to my device tree for Skyrocket on GitHub (please help debug!): http://bit.ly/yUnWHm

Build instructions are on the GitHub page.

I will always post links to code and build instructions for anything that I do. This is in the hopes that it helps someone else or that someone else can help me debug my code.

As I previously posted, here is the status:

It boots!

UI is still very sluggish; maybe because this is an ENG build?

What works: display, touch input, lights, buttons, accelerometer, wifi

What doesn't work: dhcp over wifi, radio, audio, internal and external sdcards, usb mass storage, wifi hotspot, nfc, camera, bluetooth, and anything else you can think of

To install the zip:

Wipe in recovery

Flash this zip

Flash Da_G's 0.3 kernel

Reboot

Once you get to the lock screen, you won't get a slider to unlock..not sure why

Reboot; you should get a slider to unlock

Again, I am using Da_G's 0.3 kernel so that I can focus on getting a good device tree for Skyrocket.

Also, devs: I need some help getting the radio going. In the radio logcat I get the following message repeated over and over:

E/RILQC-QMI( 228): linux_qmi_qmux_io.c: Unable to open port id /dev/sdioctl0

sdioctl0 does not exist under /dev. It is also referenced in /ueventd.rc so it seems like it should exist. Does anyone know why it wouldn't? What puts it there? The kernel? /system/bin/ueventd?

EDIT: Found out why /dev/sdioctl* didn't exist. /system/bin/ks was missing.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] R4INS:
Anyone see the latest cm9 progress update? They mention msm8660 Samsung devices.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Top, I think you're ready to start a new thread just based on this topic itself. You'll get more recognition, and with that, more help with the debugging process.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] topprospect:
Okay, will do. Thanks for letting me mooch off your thread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] pfer10:
Top thanks for working on this. I was amazed getting this device that there were no AOSP roms. I am a newb but you have motivated me to dive in and see how much I can learn.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] alphadog32:
What kernel do we have to flash? If uses another recovery, then is it going to change it to a stock ICS one? Thank You!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Making some progress on finding the differences between the two kernels. Here's a tutorial for porting Gingerbread Kernel to ICS.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] armyveterangunner29:
http://www.mediafire.com/?8jonpte1jz54xwc

da_g .03 kernel
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] romracer:
Sorry guys, I have not abandoned this effort. As I mentioned previously, I'm buying a house (we close next Friday) which limits my time to work on these projects. I've also decided to take a couple of steps back. I'm using the Gingerbread kernel for now since I've seen other devices successfully do this under ICS and we have these sources available to us from Samsung. I've also started a device tree which I've successfully used to build ICS's recovery v5.5.0.4. All of my sources are on github.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] :
Sweet 6lb 8oz baby Jesus thank you for all this awesome development
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] armyveterangunner29:
Hey congratulations. You better throw one hell of a house warming party, brother
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] R4INS:
I closed on the house I was in on a Thursday, and had settlement for my current house the next day. Talk about fun. I had no CO for the new house so I was sleeping on an air mattress at my sisters house with all my crap on a trailer. Sooo fun.

Good luck with everything. Settlements are funnnnn.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] topprospect:
Awesome news, romracer! I like the approach.

Even better! I have a device tree at https://github.com/dferg/android_device_msm8660_skyrocket that compiles and boots GB Code Aurora. I'll go take a look at what you have done. Hopefully we can all work together to put together a solid tree for Skyrocket.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] futuregerald:
Isn't the galaxy note running the same chipset as us? there's a leaked Sammy rom, not sure if it'll help but you can find more info at: http://xdaforums.com/showthread.php?t=1500186
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nkrick:
Not sure if you guys got around the MTD partitioning problems yet. If not, talk to someone from teamhacksung (the guys responsible for getting CM7 working on the i9000, i897/6, i9100, and i777).

I'm no dev, but my understanding is that Sammy uses a proprietary BML partitioning structure and AOSP uses MTD partitioning. While it may be possible to shoe-horn a AOSP ROM into the existing BML structure, teamhacksung repartitions the devices they support using MTD.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] alphadog32:
ATT Galaxy Note. Not the regular one.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] futuregerald:
That's awesome man. Appreciate all the work. I'll be buying you a six pack.

edit: Donation sent. And i'll be sending more as you hit more milestones.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] romracer:
Nicely done. If you're not already, you might try using the gralloc* from the Samsung stock ROM (in /system/lib/hw). Not sure if there is anything ICS specific in them, but it might shed light on the issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dac1227:
Funny guy:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Are you suggesting this as a way to fix the error that appears on the screen after boot, or just something in general I should try?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] carrett:
Maybe a n00b question but is it an issue that the Skyrocket actually runs msm8260 (not 8660)?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
No, the Skyrocket runs the msm8660. Otherwise, how else would the devs have been able to get it to boot? :P
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] carrett:
Respect. Just was reading these pages:

http://en.m.wikipedia.org/wiki/Snapdragon_(system_on_chip)

http://en.m.wikipedia.org/wiki/Samsung_Galaxy_S_II

Both say ours is 8260. Maybe the differences between 8660 and 8260 are negligible.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
That's the Galaxy S II international version. We have a different chip.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] carrett:
Actually both pages explicitly state that our phones run MSM8260. Here's a verbatim quote from the second one:

Check it if you don't believe me. I'm not saying that 8660 won't work, I'm more curious as to what the differences between the two are (since, as you say, the devs have been able to get a 8660 source to boot, I suspect they are negligable). I've googled and not found anything. I'm more curious than trying to downplay the work being done in this thread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
Strange. This website says it's the msm8660.

http://www.crazyupdates.com/review-...yrocket-i727-specificationfeatures-and-price/

Well, I don't think it matters either way. If the msm8660 source works, then I'm assuming our skyrocket and the msm8660 aren't too different.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] carrett:
Never mind! I found it! 8660 can also do CDMA stuff, whereas 8260 can not. That's why you see it on the CDMA 3DEVO and the Rezound. I guess since 8660 is 8260+CDMA, its source could only help us. Sorry to clutter up the forum but hopefully this info helps other people curious about the discrepancy. For the record, Skyrockets do indeed have 8260.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
Oh, that makes sense then. Alright.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8erwitskil:
i wonder if the extra unnecessary CDMA stuff would make the ROM bigger in size? bigger ROM size means less ram. probably not much to make a difference though.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] billydroid:
The t-mobile t989 definitely uses msm8660 chipset. I thought the skyrocket had the same exact specs, minus the accelerometer. That's why we can flash each other's ROMs.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] orlandoxpolice:
both are MSM8660
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] carrett:
No, you're wrong. Here's a post in a thread that will help elucidate: http://xdaforums.com/showpost.php?p=21776845&postcount=18. Basically they're all more or less compatible, but we have MSM8260, CDMA phones like the Rezound have the 8660, and the T-Mo runs the 8060. Looks, though, like processor wise, we are basically compatible with anything in the 8x60 series. Here's more info on 8260 vs. 8660: http://smartphonebenchmarks.com/for...msm8660-12ghz-dual-core-snapdragon-processor/

Again, check my links, we are 8260. It doesn't matter though. 8660 stuff will work just fine. If you insist on saying we're 8660, that's fine...but you're wrong.

Check out that complete thread too on xda. Dudes with more knowledge than me explain basically the same question.

At this point I sort of regret bringing it up, but not enough to let people say stuff that isn't true. We have the 8260, not the 8660, but...it doesn't matter.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] billydroid:
You are correct. I did some thorough searching. It must be all the same source. All the build props including cm7 say "ro.product.board=msm8660_surf" so whatever.

Let's let this guys have their thread back.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] orlandoxpolice:
this, please.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Still getting that pesky "SystemUI error" here's the latest logcat ------>

http://dl.dropbox.com/u/14908986/icslog5.txt

Here are all the blocks that have something to do with the SystemUI

I/ActivityManager( 234): Crashing app skipping ANR: ProcessRecord
{4189f3e0 370:com.android.systemui/1000}
Broadcast of Intent
{ act=android.intent.action.TIME_TICK flg=0x40000014 (has extras) }

I/ActivityManager( 234): Crashing app skipping ANR: ProcessRecord{4189f3e0 370:com.android.systemui/1000}
Broadcast of Intent
{ act=android.intent.action.BOOT_COMPLETED flg=0x10 cmp=com.android.systemui/.BootReceiver }

W/ActivityManager( 234): Receiver during timeout: ResolveInfo{418a1c60 com.android.systemui.BootReceiver p=0 o=0 m=0x108000}

/AndroidRuntime( 370): FATAL EXCEPTION: main

E/AndroidRuntime( 370): java.lang.RuntimeException: eglConfig not initialized

E/AndroidRuntime( 370):	at com.android.systemui.ImageWallpaper$DrawableEngine.initGL(ImageWallpaper.java:581)

E/AndroidRuntime( 370):	at com.android.systemui.ImageWallpaper$DrawableEngine.drawWallpaperWithOpenGL(ImageWallpaper.java:392)

E/AndroidRuntime( 370):	at com.android.systemui.ImageWallpaper$DrawableEngine.drawFrameLocked(ImageWallpaper.java:322)

E/AndroidRuntime( 370):	at com.android.systemui.ImageWallpaper$DrawableEngine.onSurfaceChanged(ImageWallpaper.java:268)

Can anyone see specifically what's going on here? It looks like it may be something with the wallpapers, but maybe I'm just being stupid.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] quikt:
Looks like u need to initialize eglconfig somewhere
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] iandr0idos:
It's not just the wallpapers. As you can see, the eglConfig hasn't been initiated. This'll cause other graphics-related problems as well...

Get eglConfig fixed first.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Ok, thanks, looking into it as we speak.

Edit: Ok, fixed the constant SystemUI force closes. Working on touchscreen responsiveness. May have an Alpha build or something of that manner later tonight.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kornklown69:
Ahhh me like alpha builds and the buggs haha
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jomeister15:
Alpha 0 out for flashing now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] projeqht:
Awesome jo! Keep up the work man!

I salute you :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wali01x:
whats difference between this & xboarder's preview aka alpha? :confused:
[TouchPad Q&A, Help & Troubleshooting] Nhialor:
Now, I know that this rom is still in an early Alpha stage, but as a test I left it on, unplugged with wifi on, not connecte (having that irritating bug where it won't connect to anything), to see how long the battery lasts, and I noticed 2 things.

A. Should the battery be draining this quick, when it was not used for the 24 hours which it lasted on battery? I mean, no apps were running, and it wasn't even connected to wifi, I usually leave wifi on on my phone by an accident and I don't notice it draining the battery that quick...(my only explenation although I dunno if it's right, is that while it's not connected and there are networks that it knows and can connect to in range, that it is constantly TRYING to connect, and thus draining the battery?

B. It says that it was constantly awake, but if you look below, the screen was turned on like, 2 or three times throughout the day?

Any ideas about these? Anyone know a fix for wifi? I tried wifi fixer from the market, but it didn't work (looks like all it does is reset the wifi) (and please don't suggest the changing channel thing on the router, cause I can't do that in college). Also, calendar won't sync with my email, says sync is down, try again later, and in accounts and settings, it doesn't say sync Calendar, it says sync com.android.calendar...? I tried wiping dalvik cache and reinstalled GAPPS V11...but nothing, still won't sync :(

Thanks guys.

Niall
[TouchPad Q&A, Help & Troubleshooting] Nhialor:
I'm on 0.6 Alpha btw
[TouchPad Q&A, Help & Troubleshooting] seliger:
I would say that is not normal. I watch my graphs loosely from day to day and I never see that sort of drain.

I will also say that mine is never awake for that amount of time. There were a couple of small blocks in the middle of today where it was awake but the screen was off, but for the most part, awake and "screen" on were grouped together.

You might check to make sure you don't have some background task running eating up CPU and battery...

PS: I also leave my wifi on all day, though since it's pretty broken it's rarely connected to anything useful. But even if it is, I can get a good day or two out of the Touchpad with light to moderate use.
[TouchPad Q&A, Help & Troubleshooting] Mr.Quipster:
Request

Hey man. I'm really glad you posted this. i think we this community can get a lot of this thread if treated right.

I was wondering if you would be willing to change the Tittle on this thread to something down the lines of "Battery Comparison and Issues" Reason being, I think you and I, and many more, can benefit from this by collecting and discussing some issues we are all having.

I was think that this can be an image posting thread of battery status and performance.

Here is mine. (shown Below)

I've compared mine to yours and yours is definitely abnormal. I'd be concern too.

I'm also, well at the least I think I am, experiencing some battery issues and I would like to clear that up by examining other touchpad battery status' and issues.

Uploaded with ImageShack.us

What do you guys think about this graph? Safe and normal?

Again, let me know what you think about that idea. I look forward to your reply! See ya.

---------- Post added at 03:47 AM ---------- Previous post was at 03:41 AM ----------

Please Guys, I would really love to see your Batter status' and performances. I want to see what I'm working with here. Please and Thank you!
[TouchPad Q&A, Help & Troubleshooting] chicle_11:
Try the gapp fixer utility, it might fix your syncing problem. The link is in one of the development threads. Sorry I can't help you with your other problems. Good luck.
[TouchPad Q&A, Help & Troubleshooting] Nhialor:
Ye that fixed it, thanks man. Still though, battery isn't great.
[Thunderbolt General] legalxchech:
Running cm7 and having problems with the soft key LED backlight. Sometimes they are on, sometimes they are not. Sometimes when i turn on the phone they are on, after I unlock they turn off after a few seconds. Nothing I do can turn them back on after they turn off but they will turn back on randomly. Is this common? Is this a warranty issue?
[Thunderbolt General] legalxchech:
Has anyone else had this issue?
[Thunderbolt General] Nate14:
I've had that problem on all AOSP roms. Though luckily CM7 has an option to fix it. I believe it's under CyanogenMod settings and backlight settings. I don't quite remember. I'll have to check and let you know exactly.

Go to CM settings and then to Display. Select automatic backlight, scroll down and check use custom. You're going to go into edit other levels and in the right column you'll see buttons. The default is 30 and if you change the value higher you'll increase the button backlight and they'll stop randomly coming on.
[Thunderbolt General] legalxchech:
That worked perfectly! I never would have thought to even look there. Thanks a
[Thunderbolt General] antiseen:
Does it do this in complete darkness? A lot of roms (or maybe it's kernel settings, or both) use the light sensor to turn off the soft key lights when it's bright enough to see them but when you're in poor or no light, they stay on. It should save you battery and I actually like it.

Think the first rom I used was gingeritis and it had this feature and thought my soft key lights were burning out.

If you already know this or if it was happening in darkness, then ignore my post. Maybe some dust got in your sensor?
[Thunderbolt General] legalxchech:
It was dark enough that I couldn't read the writing on the soft keys so of figured something was up but I figured it out. Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] sarvankarthik6:
Hello

model no : GT-S5830

android version : 2.3.4

kernel version: 2.6.35.7-perf-CL561540

Wifi Error and Bluetooth unable to start

Please suggest to fix it.

Thank you in advance!
[Galaxy S I9000 Q&A, Help & Troubleshooting] zamiurratul:
i once had this problem too, the solution is quite simple.

if u r in stock ROM, then flash the ROM with odin again ( keep a back up before flashing )

and if u r in custom kernel and custom ROm then :

if u r in a custom kernel , then reflash it.

if problem persists, then flash 2-3 more times, or try a different kernel.

if still problem remains, flash the whole ROM again.

HOPE IT HELPS.
[Samsung Galaxy Nexus] Simer03:
is there a way to make the keys a bit bigger??
[HTC ChaCha] miguel11691:
I'm currently running the go launcher but seems a little laggy... which is the best