yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] bhundven:
What dao said, plus before I showed up a few members had already tried sending the phone to the cm team with no positive results.

When I started with cm7 and eventually cm9, we were having issues getting our device to work with the aries code, which now we know is possible, with a few snags (radio issues and a few others).

The battle plan towards an official build is to start by getting cm7 on the aries kernel/rom. This may not be interesting for users, but it ultimately is the same version as our stock drop. Which means it will be easier to get that version upstream and official.

That is also a good spot for me to stop and help out the SK4G guys, who have been stuck on froyo for a very long time, and their device is about 80% - 85% the same as SGS4G. So, I'm trying to get two birds with one stone.

Once the cm7 aries is done and official, we can get more help from the cm and others on getting to ics and jb. Because both devices are well and capable of doing so.

So here soon, you'll see either mine or m4xm4n's cm7 thread resurrect from the ashes of forgotten land with a new build that I am currently working on. CM9 will also get some updates, but very few as for right now.

I know... two steps forward... one step back. But my goal is to get official GB, ICS, and JB.

I just don't want to get the current version of ICS official because the code is riddled with Samsung madness that I don't want to maintain in the future.
[Samsung Galaxy S (4G Model)] Shinydude100:
Very nice guys

My sister has this phone, (I'm from the OG Epic 4G Forums)

And I was looking what CM version you guys had, I see it's CM9 Unnofficial, and to be honest, good job devs on what you've done!

Sending it to CM team is hopeless. I now how you guys feel. The Original Epic 4G was also left out in the cold with no hopes of ever getting Gingerbread or Official CyanogenMod Support. Thus, we had our own Epic Team for the Epic 4G, they proved to CyanogenMod what CyanogenMod couldn't help with themselves. And now, CyanogenMod is leeching off of the Epic's hard work on newer devices.

If you guys sent a phone to CyanogenMod team without any luck, I personally think you'd have better luck getting (some sort of help) that will aide this phone to getting official status on CyanogenMod if your userbase throw a couple donation dollars to the CM Epic Team and try to get ahold of our devs on our forums and see if they can add this to their list of phone projects.

Gl Guys! I'll be here to see how things are going because of my sister's phone!

I hope you guys get to enjoy JellyBean Goodness like I have on my Epic! One thing you guys have right now that we don't is battery-life. CM is still working on it, but for now, Jellybean is more Battery-Hungry than GB.
[Samsung Galaxy S (4G Model)] Fluidification:
OK, you can't just assume that it won't ever happen.

We are working on a kernel, which "WILL" lead us to official support.
[Samsung Galaxy S (4G Model)] Shinydude100:
Dafaq? Did you read my post? Read it again. Good? No? Read it again.

I said I know how you guys feel, my phone was on the same boat. It was UNOFFICIAL like your phone is RIGHT NOW. I ended it by saying that I wish nothing more than the best for it, and I hope you get Jellybean goodness soon. Good God, a user from another forum section shows support, sympathy and hope, and you get all defensive and think i said the entire opposite.
[Samsung Galaxy S (4G Model)] FBis251:
*hug*
[Samsung Galaxy S (4G Model)] m4xm4n:
additional hug. Thanks for knowing our feel, bro.
[Samsung Galaxy S (4G Model)] bhundven:
Yup, finally got some tools to do some better debugging (thanks GFXmyst!). We'll slay this SoD issue soon and hopefully the issues created by fixing the SoD issue get resolved quick. Then we can start cherry-picking to jb, and dealing with an even newer set of issues.

One step at a time.

Beyond that, you know me. Plenty of stuff going on in life, been doing very little with phone hacking lately.
[Samsung Galaxy S (4G Model)] bhundven:
As for the cm7 aries attempt, it was a failure, because the samsung_audi driver (for Onenand 8Gb storage) kept getting dma errors. So I've stopped working on that and continuing to try to figure out this cm9/aries SoD issue.
[Samsung Galaxy S (4G Model)] Fluidification:
shinydude, I am sorry. The way it came out in words wasn't how I meant it. I am just saying that yes, we also have something going on to try to get it official, and right now, it's just a WIP so CM wouldn't officialize it anyways.
[Samsung Galaxy S (4G Model)] magda623:
T-mo contact backup

Does anyone know why the T-mo app contact backup does not work on the ICS roms? I've tried two different ROMS and two different phones. Does anyone have a remedy for this problem?
[Samsung Galaxy S (4G Model)] jeffsf:
Likely since it uses T-Mobile libraries that aren't included. When you look at logcat I would wager the missing library is clear in the messages.

Posted from my SGS4G, thanks to Team Acid development
[Samsung Galaxy S (4G Model)] Rebel_X:
Although this question belong to the Q&A thread, but you can follow this link

http://support.t-mobile.com/docs/DOC-2976

It was the only way for me to backup the contacts from T-Mobile.
[Samsung Galaxy S (4G Model)] magda623:
Thanks to the few that responded. I just wanted to let everyone know I have resolved the issue and I will post it here.

Went to the GB 2.3.6 Repository and d/l'ed the two apks that were needed for the contact backup. Could not install them from Root explorer but it would let me move them to the folder. I rebooted into TWRP. Clicked on the advanced tab and went into file manager. Went into system and into the apps folder. Clicked on each one of the files and clicked on chmod 755 and ran the operation. Fixed permissions and rebooted. Once the phone booted up, contact backup synced right away and it gave me the option to sync again inside of accounts and sync. This is just an FYI for those that have a CM9 ROM that wants this feature back.
[Samsung Galaxy S (4G Model)] bhundven:
Ok lets skip over to aries development update:

You know I spend every little microsecond that isn't everything else going on... on this phone.

I reverted the kernel back to 613a13ca4c425b540eed43298a743ef0efa5f41f where I reverted m4xm4n's previous modem attempt and disabled rild in the device tree's init.aries.rc.

Huzzah! We can replicate SoD issue without the modem/ril changes!

What does this mean to you?

Well, the initial aries build with wifi never had this problem because the rild service kept the phone awake so it wouldn't sleep.

This also means that m4xm4n's modem/rild changes probably work.

This means that there is something else wrong with my aries port that is causing the SoD.

This is a major milestone, to be able to bless the modem changes as ok (for now) until we figure out what is causing the SoD.

Development is not dead here, just busy with other life issues.

Aries is still under development. The latest is still what is posted in the OP.
[Samsung Galaxy S (4G Model)] bhundven:
I pushed my device tree changes to disable rild.

I will be willing to post a bounty.

Figure out what is causing the SoD, and I will personally send you $20 (if not more, depending on complexity. Up to $200).

I've given this a good spin for the last 5 or 6 hours testing different builds and trying different gpio settings, and I don't think it has anything to do with that stuff. So if you think you can help... figure this bad boy out, and we'll all start paying a little more attention to what you're up to!

Do a personal build of cm9 aries by following the direcitons, but use my local_manifest.xml instead.

READY... SET... GO!
[Samsung Galaxy S (4G Model)] m4xm4n:
I'll pitch in $20 as well.
[Samsung Galaxy S (4G Model)] GFX.myst.:
You can count me in on that bounty as well. Not saying how much, but if you know me, you know how generous i can be. ;)
[Samsung Galaxy S (4G Model)] Tunderpimp:
I'll throw out a couple of bucks too

Sent from my SGH-T959V
[Samsung Galaxy S (4G Model)] turtlepa:
I have a few ideas, ill catch you on irc. Logcat doesnt show everything in the way u need it sometimes
[Samsung Galaxy S (4G Model)] hechoen:
I'll kick in as well. Most likely not as much as GFX. Lol Great devs and a mostly great community here. SODS are a PIA. Still getting them on my skyrocket as well. tried every kernel out there and none of them have completely gotten rid of them. Had one today. Looked at my phone and had 65% battery left. Put it in my pocket and looked at it again maybe an hour later and SOD. Rebooted to 26% battery left. So what happened in that hour? Wish I knew. Also wish I was near my comp so I could of logged it.
[Samsung Galaxy S (4G Model)] nazcalito:
I'll contribute $20 to this project too
[Samsung Galaxy S (4G Model)] bhundven:
I've been debugging with usb-uart, because the problem doesn't happen if there is any device holding a wakelock (hence, no suspend) or if usb is connected (its applying power, and the s5pc110 battery driver holds a lock as well as usb).

With usb-uart, I can see what happens to the point of the lock up. I've enabled some other debugging for power management and put in some printf's in targeted points in the power management. Maybe I'm just looking in the wrong spots or causing some kind of HeisenBug that stops me from seeing the problem I'm looking for. I don't see any process failing to suspend, but suspend happens very fast (0.1s - 0.01s?).

So it sounds like some callback isn't triggering and processing the suspend or the data or something else in the system related to the suspend platform data. Or it could be an issue with resume not working properly.

This board is a little different then the other 'galaxy s' devices. sk4g is about the same.

EDIT: I've also been working on getting internal uart. I just haven't had time for it. With that, it would be possible to use kgdb and breakpoint on the final suspend, and start backtracing and staring at code.
[Samsung Galaxy S (4G Model)] Rebel_X:
^ I have an idea, how about to modify or replace the suspend function with a dummy suspend function, and skipping *suspend* for specific processes or states that you use for debugging. Also I don't know if the kernel has to be written in C, but if we can use C++'s exceptions

to narrow down which area causes the bug, it can hypothetically help skip the crashing but without solving the problem..

Please ignore if it was silly idea.. I wish I could help, I know programming, but I have zero knowledge about Linux and android programming, let alone kernel debugging.. in fact I tried running ubuntu on virtualbox, but every time I try to use the cryptic su terminal it turns me off. :'(
[Samsung Galaxy S (4G Model)] bhundven:
Not really, it's on the right track. I have a few ideas I'll try, but I've had little time lately to mess with this stuff.
[Samsung Galaxy S (4G Model)] m4xm4n:
I'm thinking of implementing this patch in order to see which devices are taking the longest to suspend.
[Samsung Galaxy S (4G Model)] bhundven:
You should read the rest of the thread for that patch.

I haven't tried the initcall_debug parameter. I'm not at home so I don't have access to my sgs4g, but it would be interesting to get uart output.

I think the CMDLINE in the sbl by default is:

console=ttySAC2,115200 loglevel=4

So, I would change that to:

console=ttySAC2,115200 loglevel=7 initcall_debug

Post the log entire boot -> sod somewhere.

We should also compare "herring" logs with "aries" boot and system logs, with both CMDLINE values for both versions of cm9.

EDIT: actually, to anyone that builds their own, you can modify the kernel config to always use the kernel provided command line, but it has a side effect that will disallow you from getting into recovery. You can always dlmode with a usb jig and flash an mtd kernel without the fixed command line. It's just so much easier to change that stuff from the sbl. But you could also make different builds and obtain these logs. There are plenty of other kernel parameters that are useful, some in more specific situations. Make sure to read docs, and sometimes code, to make sure you know what the kernel parameter is doing and if it even works for arm processors or anything enabled. ;)
[Samsung Galaxy S (4G Model)] mrsubway:
Getting the same problem I get with every ICS Rom I've tried for this phone. No signal, no matter what sim card I use. The phone is unlocked. Wifi works, but no mobile network at all. Please help.
[Samsung Galaxy S (4G Model)] xaocon:
This belongs in the Q&A thread. Sounds to me like an IEMI problem but you will get a better answer in once you post in the right thread.
[Samsung Galaxy S (4G Model)] turtlepa:
Use guake
[Samsung Galaxy S (4G Model)] Kyndig66:
An old friend of mine is moving to Arizona and is giving me a couple HP 1RU servers and a Compaq server rack. I had a very brief exchange with m4xm4n on irc and he suggested that Team Acid might want it to use after the Aries kernel business is solved. So I would like to donate it to the team in order to help everyone. I live roughly three hours from you bhundven, so if you do want it at some point we can make arrangements to get it up there.

Wang Chung!
[Samsung Galaxy S (4G Model)] turtlepa:
U can reproduce the sod if u have two batteries I found out. I charge one phone sgs4g, then switch the battery with one I had charging on another sgs4g when it gets low. When I switch battery it will boot then after 3 min it will do sod then if I try turning back on it qill sod during boot. Works every time
[Samsung Galaxy S (4G Model)] o2do:
I just wanted to try and see if it worked flashed over cm7 and it did.

I lol'd because apart from constant acore crashes it is usable :-P.

Thanks for the build cant wait to do it right
[Samsung Galaxy S (4G Model)] Fluidification:
wipe system.
[Samsung Galaxy S (4G Model)] FBis251:
You're probably getting acore crashes because you didn't wipe data

Sent from my SGH-T959V
[Samsung Galaxy S (4G Model)] hunterwei:
This rom is almost perfect! Never had such a smooth UI before.

+1 Thanks a million!
[Samsung Galaxy S (4G Model)] raphifix:
Fantastic job! Very stable, and no noticeable lag.
[Samsung Galaxy S (4G Model)] bhundven:
Just gonna say this one more time... or *grumble*grumble* sixstringsg will have his way with you.

QUESTIONS/PROBLEMS?
[Samsung Galaxy S (4G Model)] bhundven:
Op updated with a new build. Please reread all three of the first posts. Read the post prior to this one. Don't ask questions here ;)
[Samsung Galaxy S (4G Model)] darkphoenixrsng:
I have installed the new rom and it's the best rom I've had for this phone.

So thanks all of you for your hard work!!!!!
[Samsung Galaxy S (4G Model)] mataflakitas:
Cm9 vs AOPK awesome

Enviado desde mi SGH-T959V usando Tapatalk 2
[Samsung Galaxy S (4G Model)] bhundven:
I appreciate that you like our work. But I asked for 2 things.

Don't ask questions in my thread

Don't thank, just hit the thanks button.
[Samsung Galaxy S (4G Model)] gparmar76:
I followed instructions exactly as written and the ROM works beautifulyl except for when I make calls, I can not hear the person on the other end. they hear me fine, but I can not hear them. The ringer seems to be working because I heard the ring fine when making a call to the phone. When using a voip app such as skype, however, everything seems to be working perfect. I have not noticed any other issue worth mentioning as of yet.
[Samsung Galaxy S (4G Model)] mierkat09:
Your imei is messed up. Consult the link for help. Please read the q&a first, because this is not where you're supposed to ask questions, and that question has been asked and answered a lot in the Q&A.

http://xdaforums.com/wiki/Samsung_Galaxy_S/SGH-T959V/AOKP_Frequently_Asked_Questions
[Samsung Galaxy S (4G Model)] bhundven:
It sounds to me that gparmar76 is having audio issues, not IMEI issues.

gparmar76, when you check your phone status, do you see your IMEI as all zeros? I'm betting not. If not, then this is a known issue and has been discussed in the Q&A thread.

Some of the AOKP FAQ entries can apply to CM9, but I don't recommend it.
[Samsung Galaxy S (4G Model)] gparmar76:
After some further testing, I have noticed the 3g to H change rapidly as well...my home is in a great spot for t-mobile and i always get full bars regardless of what room I'm in...my galaxy nexus always has full signal as well...but with the Galaxy S 4G I'm seeing strange behavior...it seems to be switching between 3G and H often...I don't think I got a bad download as mentioned earlier but if you guys think I should download it again, I surely will. has anyone else noticed the "no voice" issue during calls? It's intermittent as I made several calls and sometimes it works and other times it doesn't.

Lastly, I just realized that my CWM revision was 5.0.28...not the newer one that was installed with this ROM...could that be playing a role in any of the issues?
[Samsung Galaxy S (4G Model)] bhundven:
Sounds like you need to search the Q&A thread for CM9.

As I said before, the voice issue is a known issue. Search the Q&A thread (where the questions are asked).

This is a wip, and this is only the second build. Expect issues.

As far as your cwm goes, it maybe wise to heimdall the boot.img. After it reboots, when it gets to the boot animation, pull the battery. Boot to recovery. factory reset, wipe /system, and flash the update.zip again.

If you have more issues, checkout the q&a thread.
[Samsung Galaxy S (4G Model)] gparmar76:
These issues were non-existant when i was running stock T-mobile Gingerbread ROMs (2.36)...I will check and do further testing tomorrow and report back....I'm sorry if these issues were reported...I use a Galaxy nexus as my daily driver and the Galaxy s 4G is going ot be for my niece...I'll report back tomorrow after more testing compared to the Gingerbread ROMs.
[Samsung Galaxy S (4G Model)] bhundven:
Then I suggest putting stock on it.
[Samsung Galaxy S (4G Model)] hechoen:
But if I keep it stock I won't be cool. Man i really wish someone would create a cool stock ROM. Oh I see after a little research I just realized that Samsung already did!!!! I better just stick with Touch Wiz because it is the best.
[Samsung Galaxy S (4G Model)] Fluidification:
:confused: what?

Touchwiz is the worst.
[Samsung Galaxy S (4G Model)] P06o:
:eek: that was sarcasm...
[Samsung Galaxy S (4G Model)] pisherthefisher:
The HP touch pad also had a "sleep of death" issue on some of its earlier builds. Maybe you can ask those devs how they fixed it?
[Samsung Galaxy S (4G Model)] chazel3:
Also lenove k1 tab had sod. Now fixed.
[Samsung Galaxy S (4G Model)] foltz61:
The Nook Color had SOD also.
[Samsung Galaxy S (4G Model)] hechoen:
Yes plenty of devices have suffered from SODs. Before we name them all let's remember this is a DEV thread. So unless you have the fix for this particular SOD let Bryan and the rest of the team do their thing.
[Samsung Galaxy S (4G Model)] bhundven:
The point that is interesting about the SoD is that it's a porting issue, not a coding error.

Other device SoDs are caused by unbalanced wakelocks and workqueue management.

Our issue has something to do with resume from suspend is failing, or something failing during suspend.

I have a few different theories, but I just don't have time right now to do anything. Work, work...

But that's the good news. Gainfully employed once again. :D

Back to hacking embedded linux stuff. Gonna be learning a little more about rfid and nfc ;)

Once I get over a little hump of work to get some stuff going there, I'll be back to hacking on this stuff.
[Samsung Galaxy S (4G Model)] bhundven:
Regardless of what is wrong with aries, r8 is a pretty good release, although I think we need to do a sync and build. I've done a few cleanup things, but those changes were mostly cosmetic. I will see about doing an r9 build, which is just updating the cm code, nothing new from teamacid.
[Samsung Galaxy S (4G Model)] foltz61:
I think the point of naming these devices was so the devs could see what caused it in them and how it was fixed. It MAY have been the same as our issue.
[Samsung Galaxy S (4G Model)] pisherthefisher:
Sorry if this is a completely retarded idea, but have you tried changing the CPU governor to something else?
[Samsung Galaxy S (4G Model)] bhundven:
Yes.
[Samsung Galaxy S (4G Model)] bot42:
@ Fisher I don't know if you realize it but they are not talking about the regular release of CM9. Everyone is talking about the Aries kernel released a few pages back. The regular CM9 does not have the SOD problem.
[Samsung Galaxy S (4G Model)] m4xm4n:
Just so you guys don't think development is dead, I've been hacking away on aries in that past few weeks. I've ruled out a few things but haven't gotten closer to fixing it.

That said, I'm going to do another sort of code audit between our herring and aries trees in the coming days, now that I'm on winter break for a month and have a bit more free time.

Sent from my super fancy SGH-T959V with Magic Debugging Powers
[Samsung Galaxy S (4G Model)] norman68:
can't get pc to find mass storage cant get in download mode after flashing cm9 but everything else seems to work properly , kinda hard on battery drain but thumb's up guy's
[Samsung Galaxy S (4G Model)] Kyndig66:
Google drivers need to be used by your USB port.
[Samsung Galaxy S (4G Model)] LiquidPlatinum:
How does one revert to stock with no download mode. What if you bootloop or something messes up.
[Samsung Galaxy S (4G Model)] Cooptx:
Re: [ROM][MTD]CyanogenMod 9.1.0 UNOFFICIAL by TeamAcid[R8][Aug-30-2012]

Can't to my knowledge. To get to download mode:

1) Remove Battery, Sim and SD (basically turn off phone and remove everything you can)

2) Replace Battery

3) Hold Volume Up and Volume Down Buttons (not power button)

4) Plug phone into computer with whichever one click to stock you want waiting for you

This should work even with bootloop and/or bad flash.
[Samsung Galaxy S (4G Model)] n1vlek:
This should've been at the Q&A section and and follow Cooptx's instructions.....if you have more problems.....GOOGLE........sgs4g download mode and click on the first link....tells you different methods of getting to download mode.....
[Samsung Galaxy S (4G Model)] turtlepa:
Re: [ROM][MTD]CyanogenMod 9.1.0 UNOFFICIAL by TeamAcid[R8][Aug-30-2012]

This should be in q&a. But adb reboot download would do it.
[Samsung Galaxy S (4G Model)] bhundven:
Ok, Quick update.

Nothing really interesting in the latest release. I just nuked my repo and sync'd everything nice and fresh, figured I'd post a build with updates from CM.

My environment is now setup for me to start doing builds and work again.

Give this guy a spin, let me know what you find.

Enjoy,

-Bryan
[Samsung Galaxy S (4G Model)] hechoen:
First off thank you.

Second off I'd be stoked if I found a file manager. hinthint
[Samsung Galaxy S (4G Model)] bhundven:
You're welcome. Sorry this ain't aries... but now I'm going to have little bits of time to hack on stuff with m4xm4n and Beastmode.

I'm biased towards using Root Explorer.

I'm trying to keep the current build stock CM.

You guys keep getting push back from me, sorry. I just have limited time.
[Samsung Galaxy S (4G Model)] Beastmode:
Re: [ROM][MTD]CyanogenMod 9.1.0 UNOFFICIAL by TeamAcid[R9][Feb-25-2013]

Bhund just saw ur mess and replied but just in case my device tree and kernel are up on git :P
[Samsung Galaxy S (4G Model)] hechoen:
OK. I'll appeal to the hire ups. lol Having a file manager included just makes things easier. No WiFI? No cell data? No computer? No problem with a file explorer. Big problem without one.
[Samsung Galaxy S (4G Model)] bhundven:
Re: [ROM][MTD]CyanogenMod 9.1.0 UNOFFICIAL by TeamAcid[R9][Feb-25-2013]

Gotcha. Maybe in a week or two I can get time to help out Erik. We can solve better problems then teamacid cm9...
[Samsung Galaxy S (4G Model)] eollie:
Isnt the CM filemanager included with all builds now? I know its in all the jellybean builds.
[Samsung Galaxy S (4G Model)] bhundven:
Not in ICS. :(

Lets not get hung up on this. We'll move on from here.

This is just an update for those still using this build.
[Samsung Galaxy S (4G Model)] Rebel_X:
Bryan, I really love you!!! "No homo" :p I thought you abandoned us :)