yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy W I8150] reidzeibel:
Good luck guys, glad to see another development thread here :)

Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
[Samsung Galaxy W I8150] kemonine96:
Thanks.

I just finished up the last piece I wanted to have done before jumping fully into the CM9 build process. I managed to build the Ancora (standard galaxy w) tree and produce an ancora update.zip. This means I should be able to take arco's work as the base for the Rugby Smart. I even managed to find the Samsung open source release for the device so hopefully things will move quickly.
[Samsung Galaxy W I8150] kemonine96:
For those following the thread, work is being done but progress is slow, this is a new device for CM9 after all. I've been in touch with nicedream06 and we are both trying to make CM9 work. Between the two of us we've narrowed down the "no display at boot" problem what appears to be kernel support. There may be more beyond kernel support, but this is the big one at the moment.

To elaborate on the necessary kernel changes

The ancora kernel is missing the touch screen drivers and if you build the ancora kernel for the Rugby with the right drivers you won't even get a boot splash image...

The board identifier for the Rugby appears to be "apache" and not "ancora"

arco's kernel sources won't compile with a board type of "apache" currently

cm-kernel sources do not have an msm7x30 board type of "apache" defined
[Samsung Galaxy W I8150] arco68:
A couple of possible helpful pointers from me:

The default kernel config for your device is apache_rev00_defconfig. A 'make apache_rev00_defconfig' will generate a .config file for your device.

This is present in my kernel, but a successful compile with this will probably not be possible, as there isn't complete support for this device in it. Also if you're working on your own kernel, and can't get it to boot in ics, it's probably due to missing genlock patches. This is required in ics for qualcomm based devices. You can check the commit log for drivers/base/genlock.c and include/linux/genlock.h in my github, and implement that in your own kernel.
[Samsung Galaxy W I8150] kemonine96:
Thanks for the information. I discovered earlier today that your kernel tree does not have full support for the apache board type (lots of errors during build). Your sources and Samsung's sources are the only two places I've been able to find the board type listed as an option. I went so far as trying to find the qualcomm kernel sources, but couldn't find any. I was hoping I could avoid trying to figure out how to bring the apache board option into a newer kernel. I've never done kernel development work and I'm not sure where to start.

One interesting thing is reports that your Galaxy W ROM boots "properly" on the Rugby even though it uses the ancora board option. I tested this earlier and it's true. I was able to use the ancora_defconf along with specifying your kernel sources in the ancora BoardConfig.mk file to boot the Rugby. I even managed to see an ADB device on my laptop even though the Rugby screen never showed a boot animation or the desktop. Based on this discovery I looked at your ancora kernel config and updated it to use the LCDC S6E63M0 WVGA Panel driver (as listed in the original Rugby kernel configs) but the device boot loops. It takes about 3-5 minutes between loops. I don't even see the device via adb.

Given the Rugby boots the ancora_defconf but has no display output, do you think it could be a matter of getting the right or a working panel driver in order to achieve display output and avoid porting the apache board sources all together?
[Samsung Galaxy W I8150] arco68:
If you want to use my kernel, you should start with porting over board-apache.c, the LCD driver, touchscreen driver and the battery driver (drivers/power/apache_battery.c) from your stock kernel. The reason it wouldn't boot when you changed it to use a different LCD driver, is because you were still using board-ancora.c, which doesn't contain the initialization stuff for it. Or maybe try with ariesve_defconfig (Galaxy S Plus), as it has the same screen as yours.
[Samsung Galaxy W I8150] kemonine96:
You have made my night! I wasn't sure what I would need to focus next on or what I would need to look at if porting.

I'll probably give it a shot with the ariesve config first to see if it works, and go from there. If it comes down to porting (seems like the better option long-term), I will likely use your sources as a base since the underlying qualcomm platform appears to be the same. Though if you think I should start with another upstream (cm-kernel?) instead, I'm open to any guidance you're willing to provide.
[Samsung Galaxy W I8150] arco68:
Better stick with stock kernel or my kernel (based on stock), as Samsung made a ton of changes in the code specific for our devices. And I don't mean major things like LCD driver and so, but really small things all over the place. So starting with another kernel means all that stuff needs to be ported over, which is a major PITA.
[Samsung Galaxy W I8150] kemonine96:
I'm glad to hear you recommend working off the stock kernel or yours, the more I thought about it the more I realized using another kernel was going to be a bad idea, especially since yours is targeted at devices from Samsung using the same Qualcomm platform as the Rugby.

I started porting the apache board file over to your kernel today and just finished a kernel build. There were very few differences between the apache board and the ancora board files which helped me get the port done quickly. The ancora and apache boards are also very similar minus the obvious differences in LCD / touchscreen. They even share a number of the same sensor declarations.

Edit: Arco68: You are awesome. With your suggestions I was able to get the screen to work and get it booted. It still reboots a minute or two after showing me the desktop and It shows a phone crash that doesn't want to clear. But at least I made progress.

Edit 2: Arco68's frameworks-base tree looks to have solved the stability issue. Still some initial hurdles left on the kernel front though. Updates will be posted in the Rugby super thread (here) going forward. @Arco68: I owe you a 6 pack of beer, fifth of liquor, pound of coffee, pack of cigarettes, whatever your primary vice may be.

Proof:
[Samsung Galaxy W I8150] wathou6:
This looks like a great piece of work you have succeeded in, kemonine96. I wish I still had the Rugby Smart to help you in anyway at all. Devices like these are hard to find support. I hope that my luck with obtaining root and getting utkanos help build the first working recovery benefited you in developing this.

I plan to play with the Rugby Smart again whenever I get it back sometime in the future. Hopefully by then, this device will have much more support.
[Samsung Galaxy W I8150] kemonine96:
Your work with utkanos is what got me going. Between the utkanos recovery and arco's work on the ancora I was able to at lest get the LCD working. Unfortunately that is where I ran into a wall. I've been messing around with the kernel heavily and last night managed to un-do whatever made the LCD work :(

Hopefully this weekend I can rebase my changes off onto a branch and start my kernel hacking fresh. There are plenty of devices with the LCD / touch screen combo the Rugby has but merging the bits into arco's ancora kernel has proven tricky for me. This is the first real kernel development I've done.
[Samsung Galaxy W I8150] kemonine96:
Can anyone post the contents of their /proc/mtd file on a running version of the ATT firmware? I'm working on getting a new kernel build (see above posts) and would like to see if I can put together a kernel only update.zip rather than having to re-install full CM9 for testing.

From what I've read I'll probably need the contents of /proc/mtd in order to get it figured out.
[Samsung Galaxy W I8150] pkkilleru:
dev: size erasesize name

That's all my /proc/mtd file has in it and i'm running GINGERBREAD.UCLA4
[Samsung Galaxy W I8150] kemonine96:
Thanks, I ended up not needing the contents. /proc/partitions was enough for the work I was doing yesterday.
[Samsung Galaxy W I8150] Motorhead1991:
I look forward to progress on this! As a Rugby user and an aspiring kernel dev, I can't wait to lend a hand. Sometime soon I'll pull the sources down and see if I can a build.
[Samsung Galaxy W I8150] kemonine96:
I posted my sources to github (see the Rugby super thread) if you are looking for a starting point. There are 2 branches you'll want to look at "ics-wip" and "ics-brk". The ics-wip branch is me re-trying to get the touchscreen / lcd drivers working and the ics-brk branch is my initial efforts at making everything work. The ics-wip branch has a "working" lcd, it shows a series of purple lines (likely a refresh rate issue or a bad gpio table) that I was never able to resolve.

The way I approached the problem was to fork arco's msm7x30 kernel sources and compare the board-apache.c file to the one provided by Samsung and to arco's ancora board file. This met with some success but I also used the ariesve kernel sources from arco for the touchscreen / lcd components. The ariesve should be the same touchscreen and LCD while the ancora should be the same underlying platform. However, from what I could tell in the board file there are some differences between all 3.

Some other things to note:

The rugby board is "apache", you'll want to look for apache in the samsung sources

The standard cyanogenmod frameworks/base repo won't give you a stable boot, you'll want arco's frameworks/base repo for a stable boot.

I have setup a rugby device and vendor tree that is based on the ancora ones from arco, just modified for the rugby.

During my work I flipped between using the board-apache and board-ancora files

I believe I kept the apache naming for the device identifier and some other things

My published recoveries have a different device identifier than what the head of my sources use. You'll get validation errors if you try to install.

To Fix:

Setup the Rugby device descriptor to use a binary kernel (the 2.3 kernel is in my sources already) and build an updated recovery. Flash this recovery and you should be all set

Remove the asserts from the updater script and ignore the problem

If you need help with anything in terms of getting going let me know and I can hopefully help you out some.
[Samsung Galaxy W I8150] Motorhead1991:
Ah... the post that kicked off the campaign :D. For tgose not catching the teasers and hints, we're || < that close to having an alpha test ROM for the Rugby.
[Samsung Galaxy W I8150] M.Barakat:
Great work Kemp ;)

I followed the thread from its beginnings glass to see your progress.

after you finalise your work it will be not locked to AT& T SIM right?
[Samsung Galaxy W I8150] Motorhead1991:
That's what we're hoping. We're stuck trying to get the RIL (radio interface layer) working. After we have RIL connectivity, we'll fix the next major issue, the lack ot audio.
[Samsung Galaxy W I8150] kemonine96:
Check your PM's I found the system.prop from the CyanogenMod sources may not be 100% for our device. I think it is close though. Also based on a few things I have a feeling we haven't dug quite deep enough into the underpinnings. Will likely need some help soon.

I believe the phone will still be locked to the ATT sim even with the 3rd party firmware. You will likely need the network unlock (or sim unlock depending on who you talk to) code and a non-att sim card. I purchased an unlock code from http://unlockunit.com/ and it arrived within a few days. Worked w/o hassles. I've always had to call the carrier for an unlock code or purchase one from a re-seller online in order to sim unlock my ATT or T-Mobile phones. I'm on my 10th unlocked phone and it always took a special code regardless of firmware or rom installed.
[Samsung Galaxy W I8150] kemonine96:
Thanks to the cyanogenmod irc channels I managed to figure out how to debug and fix the baseband / ril / radio issue we were having with CM9 on the rugby smart. I also managed to fix the screen brightness issue that was occurring. Motorhead and I were able to successfully send text messages. Dialing works, but there is no in-call audio currently and I have no idea if the microphone works, but it at least dials and receives calls.

The code is up on github for the daring. An alpha will be released once phone calls are working with audio and microphone. Don't ask, I won't post a build until those are working.
[Samsung Galaxy W I8150] M.Barakat:
May be there is an other way :)

Thanks guys so much for the replies.

I just stumbled upon this thread:

http://xdaforums.com/showpost.php?p=17148825&postcount=334

May be we can save a buk or two ;D
[Samsung Galaxy W I8150] kemonine96:
I can confirm that there are enough differences between the Rugby Smart and the Galaxy W that any of the ROMs for the Galaxy W will not work for the Rugby without some somewhat significant alterations. Namely the kernel (drivers for audio, sensors, etc in particular) as well as a number of supporting libraries need to be changed out for a ROM to be workable.

There are enough "big" similarities that a Galaxy W ROM can be made to work with the Rugby. Check the super thread in a few days for what that ultimately means for a CM9 port.
[Samsung Galaxy W I8150] kemonine96:
I can officially say the normal Galaxy W port from Arco will not work out of the box on a Rugby Smart. Some under the hood work is necessary to make arco's work run on the Rugby.

After a couple months of hacking away I managed to get most of CM9 working for the Rugby. For those interested in the result head over to the thread I created for tracking progress: http://xdaforums.com/showthread.php?t=1940632
[Asus  Eee Pad Transformer Prime] acdcking12345:
I have had my prime for less than a month. My two things that I dont care for on it.

1. I am not a fan of the wireless range. I ordered a Wifi extender that I shall install later this week. Hopefully will fix the range. My older TF101 connected and worked well. My Prime. Not so much. :(

2. I have light bleed. Especially when I have a pure black screen to look at...I don't really see it otherwise.

So why are so many people *****ing about the Prime? I am missing something about it? I just cant find a reason to hate it and not buy an ASUS product again..
[Asus  Eee Pad Transformer Prime] ShelW:
Well, first off, let's hope you feel the same way a year from now.

However, I've had my Prime for about two months, and still love it!

I have excellent range with wifi (I have an Apple Airport wireless router, at my home) both at home and away.

I don't notice any particular excessive light bleed, and frankly don't use my GPS, other then wanting it to notify certain programs about my current location, which seems to work fine (I haven't noticed it NOT working, if, say, I open Fandango and want to find movies in my area. It seems to always show the area I'm in)

That said, I do realize that other people HAVE had major issues with their WiFi, with rebooting, poor GPS, etc.

It's a pity, because when the Transformer Prime is working properly, it's simply an amazing device!

I'd love to see Asus have major success with the T300 and TF700. I'm sure Asus didn't sit down and decide to develop a fantastic Android tablet, but hey... let's make sure it has several issues with it's wifi and GPS...

The Prime, T300 and soon the TF700's ability to dock to a nice keyboard, it's quad core processor, thin and elegant designs (all of 'em) show that Asus has put a LOT of work to put out a fantastic Android device! I, for one, am grateful, in spite of the issues they've faced! I hope they don't give up on Android Tablets! :D
[Asus  Eee Pad Transformer Prime] rorytmeadows:
This thread really should be merged with the Positive Prime Thread, but I agree.

The Prime is an excellent device. Every piece of technology has it's downfalls and the ones that I experience aren't all that bad for me.

If you check out posts by Gary Key, he explains that a lot of people are lying/exaggerating after following up with support tickets.
[Asus  Eee Pad Transformer Prime] Dagrog:
Have you tried bluetooth and wifi together?

Do you ever want a functioning gps?

Wifi by itself works but it's a lousy signal. My wife uses it and likes it but when you pat top dollar for a device it should work like a top dollar device. Also what do you expect Gary to say, it's a pos?
[HTC One X] nicholaschum:
Hi all,

I have a question. Is it normal if you bend the corners of your phone slightly, it causes a creaking sound to occur? No rainbow or screen mess ups appear, only some creak. Try with your phone and tell me your results, don't be so weak with bending, just try and see if you have the creak.

Thanks

Nicholas

Sent from my fingers straight to your face! :3
[HTC One X] brent8577:
why are people trying to break their phones? if you smash an lcd it does what it does. etc. use it like youre supposed to or stop complaining that it rattles, cracks, shatters, and bends. i dont get it. i paid a lot for mine i take care of it.
[HTC One X] nicholaschum:
No, I mean, when you put some pressure on the phone, for me, its the top right corner, when you push down on the top right of the screen, it will creak, but no screen ripple or screen distortion.

I do use it how it is supposed to be used, but then I still hear creak. Is it normal?
[HTC One X] nicholaschum:
Got it replaced within an hour. Got the second batch (SH24) instead of (SH23) which was my previous phone. Everything works now.
[Galaxy Note GT-N7000 General] thechints:
Hello All,

Here's my 2 cents on SODs and killing of it (even if only temporary)

I am currently on @Anti's Asylum ROM. Previous to that, I was on CM9 ver 7.

Had been plagues by SODs and had almost given up and was about to flash Samsung Stock ROM.

I was on Stunner previous to CM9. Once I was on CM9 and loving it, I came across this nasty looking creature called SOD for the first time in my life.

Threads suggested I should flash GB ROM back and do a clean install. @AndroidIndian was kind enough to walk me through all the steps and I did everything I had to. Then flashed CM9 back. Guess what, those SODDIN SODs were still there.

So, apologetically, I posted that I had to betray my brethren here and go back to Samsung Stock.

Then, @Tremorone PMed me to try @Anti's asylum, built on CM9 code. He said since I was trying to hold on to an AOSP thing, I should try it at leas once. In one last ditch effort, I did the right thing - flashed Asylum ROM over the CM9 ver 7.

Now, the interesting bit:

Initially, I was on XXLPT Modem (the latest one). Overnight, there was no SOD and I was a happy bunny. Next morning I got a long call (about 20 mins). Once the call was over, SOD !!!! Figured it HAD to be a modem.

So, I did the following:

1) I flashed LP5 Modem through Mobile Odin. SODs were less but the lockscreen froze up once.

2) Being the impatient prick that I am, after a while I flashed LB2 Modem via CWM Recovery.

SODs has drastically gone down on that. No SODs in the last 7 hours as a matter of fact.

I don't know if it's the ROM, LB2 via CWM or the combination of Steps 1 and 2 above, but seems like it has more or less solved the problem. Of course, it is still early days and I need to observe for a couple days more.

To everyone suffering at the hands of the SOD demon, I would suggest why not try Step 1, let the ROM settle, and then proceed with Step 2 (as above).

There's no harm in trying, right? And if it solves it, nothing more beautiful than it. Then you can go CM flash happy as soon as new builds start being avaialble.

Thanks to @Abhisahara for helping me keep the faith.

All the best SODding off the SOD.

Cheers.
[Galaxy Note GT-N7000 General] DV1510:
Well, I think I'm a lucky guy. I had never one SOD since I own a note. I have nearly the same flashing history like you. Flashed also many modems . I can't imagine why the devices are so different. The same thing I noticed with my old HD2. I hope you will find the reason/way to solve this f******* SOD issue

Gesendet von meinem GT-N7000 mit Tapatalk 2
[Galaxy Note GT-N7000 General] nuclearmonkeyuk:
I'm the same after flashing cm9 I had one screen of death on the lb2 modem.. I flashed lp6 just because.. After that I used cm9 for a week with not one sod before flashing ics official
[Galaxy Note GT-N7000 General] andreww88:
My SODs stopped after I flashed .19 Stunner with LP5 kernel and LP6 modem. I haven't had one since then (**knock on wood**). I am on stock ICS now with the new modem, not CF-root kernel though. Strange how variables are always so different though.
[Galaxy Note GT-N7000 General] virgopunk:
Hmm,

I've flashed several modems since being plagued by the SODs. I'm on CM9 nightlies and am using LP6 from LB2. The SODs have gone down with the newer modem since I was getting 5 or 6 a day! But, I still get at least one or two a day now. I'll try with the latest LPT or LR1 and see if these make any improvements.

They are a bit of a mystery though since there never seems to be any consistency to what is actually causing the sleeps.
[Galaxy Note GT-N7000 General] anilisanil:
I always flashed modems through Mobile Odin and flashed every single modem available for note, but still had SODs.

So I wiped everything and reinstalled the ROM and did not restore data and I did not have SOD.

I have data backed up on Google, it restored my apps (through play store), contacts and wifi access points, so I was kind of OK, since I did not lose out much. But thats just me!
[Galaxy Note GT-N7000 General] MR.change:
I tried LB2 ,LA4 ,LPY Modems ,and had one SOD in two weeks time while on CM9 build#3 and LA4 modem.

LB2 modem iks very good and I'm using it right now with the latest nightly with no SODs what so ever.
[Galaxy Note GT-N7000 General] virgopunk:
I've flashed modems using CWM and still get the SODs. I'm beginning to think these are not directly related to the modem. I did a clean install of GB from Imilka's CM9 (Chinese leak) then Chainfire's rooted kernal and then on to the CM9 nightly. I didn't copy any system data but I did use TB to resinstall my apps (against advice I know). I had no SODs on Imilka's rom but they appeared following install of CM9 nightly.

I guess I'll try a clean install again but I hate having reconfig my phone everytime since I change so many things via Apex, Minimalistic Text and Folder Organiser apps.

I'm hoping though that we'll get to a nice update on CM9 that will resolve the problem eventually.
[Galaxy Note GT-N7000 General] tamarian:
I think SOD is WIFI related (not just modem). Since upgrading to ICS, different ROMs, I had many of them on all ROMs and modems, until I set my WIFI to never sleep and disabled any battery saver trying to make it sleep when screen off. That solved it for me. Then started testing battery savers, most of them brought SOD again, until I tried battery defender, which seem to work without SODs.
[Galaxy Note GT-N7000 General] drfranz:
Had lots of SODs in the past on CM9, none for 3 days since I installed nightly 20120515 and LPT modem. Fingers crossed :)
[Galaxy S II Themes and Apps] Tyrany:
Can someone please post the Apk? I can see it with market enable but i have country restrictions so no download

thanks
[Galaxy S II Themes and Apps] Wezi:
Mint.com currently only supports US and Canadian financial institutions only. Do you still need it?

Also check out this link for a modded market which will remove country restrictions

http://xdaforums.com/showthread.php?t=1650116
[Galaxy S II Themes and Apps] bartoloandre98:
https://play.google.com/store/apps/details?id=com.skplanet.mintmarket
[Galaxy S II Themes and Apps] Silesh.Nair:
http://db.tt/oU3Uxfc7
[Flipout and Charm General] sin1884:
im on a pay as you go plan, unlimited everything including data, but thats only on this cheap pantech regular phone.. i went to the AT&T store and they unlocked my Android (mb508 Motorola Flipside) so i can use my go phone sim in it, but cant use internet since its a smartphone, even though i have unlimited everything for 50 a month, id have to pay 25 extra a month for just 1gig of data.

is there anyway i can get around this because this is absolutely ridiculous.... any help would be greatly appreciated