yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] bhundven:
If you knew what all happened there for a few months, you'd have a different sense of the situation.

I'm currently touch and go for a little while, but I'm slowly ramping up to getting back to this.
[Samsung Galaxy S (4G Model)] Rebel_X:
I understand, Real life can be a b!tch, no rush man. We understand that you

do help when you have time.

That aside, Did you sync the latest changes from CM9? I see there are changes

for the sensors delay values recently in CM9 repo, but not in teamacids?!
[Samsung Galaxy S (4G Model)] bhundven:
Right, so I've been away for a little bit. I'm sorta needing a catch-up on what is different and sync up between the aries and teamacid trees, but I did nuke my working repo directory and sync'd everything fresh, so this has the latest changes from the cyanogen team. (:cough: anyone else on teamacid could do this too ;) )
[Samsung Galaxy S (4G Model)] FBis251:
I do it all the time ;). I'm glad you taught me how to use a mirror setup. Makes nuking and rebuilding the working directory so much easier.
[Samsung Galaxy S (4G Model)] lumin30:
Re: [ROM][MTD]CyanogenMod 9.1.0 UNOFFICIAL by TeamAcid[R9][Feb-25-2013]

There is an answer in the Q &A.
[Samsung Galaxy S (4G Model)] FBis251:
Is that the CM File Manager I smell? Wait a minute, it comes with themes too??? :D... *cough*
[Samsung Galaxy S (4G Model)] bhundven:
Yes, Thanks FB! (and click thanks on his post! all I did was roll a build and post it. update the op)

OP Updated, get R9.1 while it's hot.

Only changes was to add the CM File Manager. Please continue to be awesome and ask for help and post questions in the Q&A thread.

If you find a bug, provide a log. Clean your logs of passwords and other identifiers you wouldn't give anyone else. And post the log to the thread or to a file hosting service. The more info I get about the issue you found, the faster I'm able to reproduce the issue, and the quicker we can fix the issue to make it go away.

This build will eventually stop being updated. So this is my notice. Moving forward, we'll be moving on to jb.

Work on Aries is halted at this point. I'm looking into a different solution, and will provide more info as I can produce it.

If you have something that you can contribute to development, join us in IRC (in my signature) or post here! If you find a typo in the OP or trailing posts, post here and I will fix it right away.
[Samsung Galaxy S (4G Model)] FBis251:
Also don't forget to thank mcrosson over on his thread http://xdaforums.com/showthread.php?t=1982918

We used his CMFileManager ICS port, unalatered and thankfully he shared his source code with everyone :).
[Samsung Galaxy S (4G Model)] Rebel_X:
Possible Compass fix!

I went to stock using heimdall one-click to test the compass and it worked

after I did the Horizontal calibration. Went back to CM9 and it's borked.

So it wasn't hardware malfunction.

I think I have fixed the compass finally. If anybody can try and test to see if

this will work or not!

I found (a newer maybe!) proprietary drivers for the compass I took them from the Vibrant's

CM7 nightly builds. In Vibrant's forum, they had the same problem as us, the compass' needle

was stuck and not spinning.

But nevertheless I tried them and they worked, more importantly. they worked after each

reboot. (As I was missing around with the values inside 'yas529.cfg' but with every

reboot or calibration, it got different values so it wasn't permanent)

To try this, download the attached file, extract and push the 2 files

(geomagneticd & orientationd) inside:

- "vendor/bin/" ... and

- "system/vendor/bin"

(I use ES File Explorer with root access and mounting 'system' as writable, the

best file manager imo)

Overwrite the files there. After that it wouldn't hurt if you delete

'yas529.cfg' just to calibrate the compass. it is found inside "data/system"

It will be recreated after reboot. (If there is 'yas529.cfg.BAK' delete it too)

Then reboot your phone, and test the compass if it is working.

Note:

If the North is always pointing towards the west even after calibration.

You could use either "Smart Compass" to do Azimuth calibration +45.0 degrees.

Or you can use "Compass & Level by Maxcom" to calibrate the pitch & roll.

(GPS Status app might work too).

(BTW is there a good reason why there are two copies of vendor directory?

the one in the root, if you delete it, it gets copied back after each reboot from

"system/vendor"?)

Please report if this is finally fixed!

Edit: Just noted that MD5 matches between the old and new files! How is this possible?! I think has something to do with

starting/stopping the geomagneticd service. But who cares, at least it works for me, hopefully for others too.
[Samsung Galaxy S (4G Model)] bhundven:
Thanks! I'll add this fix to the next build!
[Samsung Galaxy S (4G Model)] Rebel_X:
Re: [ROM][MTD]CyanogenMod 9.1.0 UNOFFICIAL by TeamAcid[R9.1][Feb-27-2013]

Before you add this, please see if it works first. The MD5 thing puzzles me.
[Samsung Galaxy S (4G Model)] Theraze:
Yeah... every bit matches between the Jan 27 Fah-Q CM9 and those files. For that matter, same orient/geomag goes in the Fah-Q JBs, and their compass isn't... entirely... happy. :)

And... downloading the Acid CM 9.1 for Feb 27 and should have that done in... 3 minutes now. 28 seconds. Oh, how the seconds fly by. All 8 of them. Done.

Same results for Acid CM 9.1 (this). Files are identical, with only the hour different. Guessing it's time-zone drift, since the various TFQ ROMs (along with Raver's) are all from 2/28 1833 and this TA is 2/29 0333, 9 hours later but with minutes matching and size/contents the same.
[Samsung Galaxy S (4G Model)] bhundven:
All good info. I will definitely do my own testing with this. I believe there is a cts for this?

Don't they do cts in jb now?

EDIT: well, here is the compass sample app for 4.2.2_r1. You can find the other branches there as well. You could add more logging on directional change and add other debug info as needed to test the compass.

EDIT2: here is a sensor cts that tests the compass.
[Samsung Galaxy S (4G Model)] ddamian67:
From Stock to CM9.1 by Team Acid

I have been researching and this seem to be the most stable up to day ROM,

I am starting from Scratch, i have:

GB 2.3.6

BASEBAND T959VUVKJ6

KERNEL 2.6.35.7-T959VUVKJ6-CL694130

How can i get this ROM flash in to my T959v?..the steps from the first post is for already rooted phone, any suggestion will be greately appriciated
[Samsung Galaxy S (4G Model)] lumin30:
First thing to learn is there is a Q&A for questions regarding ROM's. Secondly, you can use the guide in second link in my signature to flash either AntonX's rooted kernel or Blastoff kernel, then you can flash then ROM. The kernels to download and flash are in the link provided in the guide. Read carefully.
[Samsung Galaxy S (4G Model)] ddamian67:
I have checked the Q&A and developmental forums there are about 4 post related to rooting the phone, i was asking for some sore of recommendation..."hey this one is good post to root the phone", Each post has hundreds of replies some time is kind of hard to determine or decide which to use.

I guest i just pick one, if i ask another questions i may get ..."learn to read the other 2000 and some posts what you looking for isthere some where!!.
[Samsung Galaxy S (4G Model)] TwitchyEye:
Just need to read the first post.​
[Samsung Galaxy S (4G Model)] ddamian67:
FYI

Release 9.1 and release 9 Video recorder not working for me, i get error "Unfortunately, Camera stop working"

When back to release 8, 20120830 video recording works.
[Samsung Galaxy S (4G Model)] bullriders:
Video player or YouTube not working. Its never worked.

Suggestion fix?
[Samsung Galaxy S (4G Model)] Theraze:
Reading. And a different kernel.
[Samsung Galaxy S (4G Model)] bullriders:
Got working video by installing MX Player and MX Codecs.

Built in player seems to be corrupt.

---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------

Install MX Player and MX Codecs make it Default.
[Samsung Galaxy S (4G Model)] turtlepa:
Did you successfully record a video and play it back?
[Samsung Galaxy S (4G Model)] bullriders:
Actually no. I don't use the video record.

I installed various apps and they all crash the same as stock app.

But with the MX player I can at least watch streaming videos from Facebook.

I tried 2 different YouTube apps and they crash also as thee stock app does.

I'll keep trying.
[Samsung Galaxy S (4G Model)] turtlepa:
Well. I guess the video problem is definitely kernel related. So if u wanna take videos... install release 8
[Samsung Galaxy S (4G Model)] ddamian67:
Please don;t abandon this project!!

This is a great ROM and it can be better

release 9.1 is goo but there is an issue with video recording.
[Samsung Galaxy S (4G Model)] turtlepa:
Try flashing hefe kernel
[Samsung Galaxy S (4G Model)] Mezabaru:
trying hefe. Hopefully it has better battery, currently using 9.1.0 until raver releases his update :3.
[Samsung Galaxy S (4G Model)] turtlepa:
Hefe definitely has better battery. It actually deep sleeps.
[Samsung Galaxy S (4G Model)] BitingChaos:
I see the "Hefe" kernel recommended, but the Hefe kernel thread (http://xdaforums.com/showthread.php?t=1837873) says that the kernel is already part of CM9.
[Samsung Galaxy S (4G Model)] TwitchyEye:
The latest cm9 release has a screwed up kernel.
[Samsung Galaxy S (4G Model)] m4xm4n:
Thanks to the efforts of noiphonehere, we've gained some traction in Aries, resulting in the eradication of the Sleep of Death and the issues with call audio.

We will now be moving forward with aries. noiphonehere's changes will be moved into bhundven's aries tree shortly, which will then be forked to the TeamAcid github organization.

However, there are a number of things to fix and stuff to integrate from herring before we release a build. e.g. There's some freaky stuff going on with CPUfreq that needs to be fixed, or else you'll all get mad when changing your CPU governor and clock settings. The FFC needs to be given the ol' rotation fix and I want to apply it in a different way than I have in the past. I want to keep the device specific changes to a minimum so that the Galaxy S 4G stands a better chance being accepted into the upstream Aries kernel.
[Samsung Galaxy S (4G Model)] BitingChaos:
That's awesome. I *just* got my Galaxy S 4G a few days ago, and it seemed like Aries was dead.
[Samsung Galaxy S (4G Model)] Fluidification:
Hey, Max, just posted an aries release.

The CPU Bug seems to be irrelevant on the latest kernel release.
[Samsung Galaxy S (4G Model)] bhundven:
It's been a bit, so OP is updated with a new ICS cm-9.1.0.

I'm still waiting on sim adapters to arrive so I can also test my builds, but here is a test build.

Not intended for daily use, yet.

Please send/attach/pastebin logs. I cannot test gps/cell/data until I get the adapters.

Be as descriptive as you can so we can stomp out bugs. :D :highfive:

Don't forget about the Q&A thread :)

Lets keep this development thread clear for bug reports and conversation specific to the following goals:

1) Get ICS mostly working properly

2) Try(*) to port the herring kernel for 4.2 and :fingers-crossed: maybe 4.3? (might need a lot of selinux patches)

3) Most likely getting gps and radio issues figured out on ICS will help us get those devices working properly with jb-herring and eventually jb+-aries.

Lets start with what we know works.
[Samsung Galaxy S (4G Model)] Theraze:
Regarding these, it would help to clarify these exactly.

First, what else are you hoping to accomplish with ICS, for 1? I believe that it was discovered that the main problem with ICS GPS was that it was missing one of the required build.prop flags regarding how to use aGPS. When does ICS officially meet 'mostly working properly' in ways that it doesn't do now?

Regarding 2, it's been done. The only problem that still remained, besides the same non-functional GPS that 4.1.2 also had, was that Wifi was... weird. You had to manually restart it, but if you did that, it worked fine.

As far as I'm aware, there are no more ICS Herring GPS issues. It works, and with the proper/missing build.prop bits replaced, syncs about as fast and reliably as Gingerbread did. Which, for me, was never that reliable, but that's the way my specific phone's hardware works.

To remind on the build.prop sections, that comes from the AGPS thread, section 13 of the notes. It was noted by hechoen in post 20.
[Samsung Galaxy S (4G Model)] bhundven:
Do I need to write out a contract and have it signed by the XDA Developer Committee? jk

I'm just doing what I do, and that's what I'm doing. But I love constructive-criticism. :)

Relearn the base by giving it an updated build. Going back through code that actually works to discover what is wrong in aries kernel or the aries android device repo that is causing gps and other components to act weird. Hopefully we can get a CTS against our platform and friggin finally get our device official builds before the galaxy s line no longer gets updates all together.

If you don't want me to work on that stuff, I can just spend my time on other things, if you wish.

After updating the code provided by upstream, testing that everything still works properly.

There are some people that still use cm-9 because gps still works. The last problem was that the new gapps for ics and gb couldn't be installed because our builds were out of date. I hope to have new gb build sometime soon.

And being able to diff a known good code base with the one having problems will help us discover what is different, so we can diagnose a way forward. Some of the issues I hear of with aries sound to me like device tree mis-configurations or just missing stubs to connect old interfaces to new ones. I'm also sure that there are issues caused by abi changes in 4.3 and selinux. Can't wait for 4.4 :silly:

Thanks for that link. I got the original agps and wifi working in cm7, and not to pull rank, but I'm sure I'll get them working properly again. Time for me to do anything has been a major factor against me. I'm getting more time and I have a linux laptop now. No more fighting my mac to make a build.
[Samsung Galaxy S (4G Model)] Cooptx:
Thanks guys :3 make me feel even worse that I just broke my S 4G, now I have to use a Vibrant D:
[Samsung Galaxy S (4G Model)] bhundven:
Just built a herring cm-10.1-20131102-UNOFFICIAL-galaxys4gmtd.zip.

Not ready yet. Still cooking. USB, Wifi, and and maybe much more doesn't work, but I just got everything together and actually building. So it boots! :D
[Samsung Galaxy S (4G Model)] mikaeldalc:
AWESOME! Just got this phone as a So-Called PLAY PHONE and im running the 9.1 test. Everything seems smooth so far. cant wait for 10.1
[Samsung Galaxy S (4G Model)] DickyG:
Great news to me also. Wife, children, and I have all decided to keep our S4g's. We have been happy with this phone and now that our contract is up, our monthly bill has dropped considerably. So...further development is very much appreciated...thanks.
[Samsung Galaxy S (4G Model)] bhundven:
I have to mention, the goal of getting 4.2.2 working with the herring kernel is to compare some code to get the ril, gps, and wifi stable on aries. I might never release jb herring.
[Samsung Galaxy S (4G Model)] Theraze:
Just to note: RIL and Wifi are already stable on Aries. It's only the GPS that doesn't work.

Herring 4.2.2 Wifi/GPS were problematic. Herring 4.1.2 GPS was problematic. I think RIL has been cooperating with Aries in both 4.2.2 and 4.3.
[Samsung Galaxy S (4G Model)] bhundven:
I've had problems with ril with at&t sim. I have heard some tmo users experience the same problems I was experiencing. WiFi works, but with poor quality.
[Samsung Galaxy S (4G Model)] Theraze:
Okay. I didn't want you to think I was telling you not to... it was mostly just that, for me at least, my calls (when memory isn't critical and apps are restarting) are more stable than ever. My wifi is as strong as it was on GB complete to fading out in the same area of my bedroom and coming back if I turn the phone JUST the right way. It shows lower, but that's just because of the T-Mo lying levels. :)

Was mainly saying that if you were trying to get them to work from scratch, there's already some things you can compare to. And if you happen to get them to work in a different way, then that gives comparables which might show how to do something else or shed light on how/why something is the weird way it is.
[Samsung Galaxy S (4G Model)] bhundven:
Exactly.
[Samsung Galaxy S (4G Model)] bhundven:
Got nano to normal sim card adapter in the mail today. So I just got done testing that with the new 4.2.2. Now I'm getting some pretty awesome boot loops :D

2.6.35.7 with 4.2.2 :P

EDIT:

haha:

<3>[ 86.947327] BUG: sleeping function called from invalid context at /build/galaxys4gmtd/jb/kernel/samsung/galaxys4gmtd/arch/arm/mm/fault.c:295
<3>[ 86.959130] in_atomic(): 0, irqs_disabled(): 128, pid: 975, name: rild
[Samsung Galaxy S (4G Model)] graycow9:
Back-lights on ICS?

I would quit using the newest releases of everything and come back to ICS... but one thing I noticed is that all ICS ROMS lack the mod for the button back-lights to turn off D: and I know they aren't too strong, but I cannot help but feel it kills my battery. If it isn't trouble, and I am not asking too much that is, could you include it if it were possible? o.o

Heck, I even know a way they could be improved ;D I notice that the mod allows for turning back-lights completely off .... but how about turning off just the lights themselves? Retaining their functionality?

Also, welcome back :) nice to see you around again.
[Samsung Galaxy S (4G Model)] bhundven:
So, the aries touchscreen, backlight and key lights are far more superior then the herring drivers!

The problem is, the herring drivers do the right things wrt sleep states and some how tie in stuff with the pmic.

This is the stuff I'm trying to figure out.

I found a neat tool to help though. I was previously trying to use SystemTap, but it has so many dependencies it is hard to integrate into the android build. The other night, I found ktap, but I'm not sure about what the minimum kernel version it will work with; being whether it will work with either the 2.6.35.x kernel or the 3.0.x kernel.

Also to note, if you aren't aware, the 3.0.x kernel series is EOL (End Of Life) on kernel.org. So things will get interesting when 3.0 stops getting updates on the aries kernel. I need to buy a jtag...
[Samsung Galaxy S (4G Model)] graycow9:
Nah it's probably more like a little nip behind my ear that won't go away. XD It probably isn't doing much to the battery, but it's one of those things ya know?

I'm not up to snuff with dev-talk so much of it is sadly jibberish to me /: I'm trying to get into it, just I haven't got much for guidance here... but I am definitely persistant! I was trying to work on that dang Sidekick still. I have to start somewhere else first though, so I think I wanna build AOKP..

I do appreciate all of the hard work you have put into this ROM. Excellent job! :)
[Samsung Galaxy S (4G Model)] champ1919:
I don't think that mashing the thank you button is enough for the work that you've done to this phone.

Yesterday I used it as a GPS on a 12 hour boat ride while running your rom. Flawless. Even had 4 hours of screen on time before having to plug in the charger.

Thank you B!
[Samsung Galaxy S (4G Model)] itzik2sh:
Not true. HebMiUi has this fix and every ICS ROM can have it once flashing Beastmode's proton kernel.

sent from me
[Samsung Galaxy S (4G Model)] bhundven:
Maybe he meant all but a few?
[Samsung Galaxy S (4G Model)] Theraze:
Or just flashing Hefe-KoD and disabling the backlights entirely. As another solution.

The bottom line is that the statement is not true... there are options to disable the backlights on ICS. :)
[Samsung Galaxy S (4G Model)] bot42:
Tried to put these logcats up yesterday.

Here is two logs hopefully showing the glitchy radio problem fingers crossed.
[Samsung Galaxy S (4G Model)] m4xm4n:
Front Facing Camera (FFC) fix is now in git. It'll be in the next build.

You'll be able to get back to taking MySpace angle shots for all your BFFs now.

Whoops! I only fixed preview. Saved images are still screwed up.
[Samsung Galaxy S (4G Model)] bhundven:
Glitchy radio fix is coming in release 0.4. ;)
[Samsung Galaxy S (4G Model)] bhundven:
Ok flash junkies. Release 3... *cough* now 0.3 *cough* is up on Goo Manager Beta and Sourceforge.

If you see JT, thank him for car/desk dock audio and data usage fixes!

Soon, fb will have an ICS based twrp! woohoo!

YEEEEE HHAAAAAA!!!! :cowboy:
[Samsung Galaxy S (4G Model)] FBis251:
Made me laugh.
[Samsung Galaxy S (4G Model)] mguelph:
On it, like white on rice..
[Samsung Galaxy S (4G Model)] turtlepa:
Extremely nice install for r03 without having to wipe data. It does system app update and i forgot to flash gapps. So i flashed an it remembered to optomize those apps on boot as well. Seems snappier then r2. Great work
[Samsung Galaxy S (4G Model)] Fluidification:
if you get a "starting applications" every boot, see if any /data app is constantly fcing like after a new flash with same data, Titanium B always fcs. Uninstall it, then reinstall it, then you should be good.
[Samsung Galaxy S (4G Model)] ipaq_101:
Bhundven this rom has been the smoothest rom yet, thank you.

I don't know what you did but it's snappy as hell.

I know you said that the radio would be improved in version. 04 but so far it's locked and works perfectly.

The gps still takes a while to lock and isn't accurate all the time, but it know that has always been the case with this phone. It sure if we can even do anything about it.

As always thanks, the gps is the only issue I have encountered so far.
[Samsung Galaxy S (4G Model)] bhundven:
Actually, this is one of those releases where I hardly did anything. All thanks go to jt1134, m4xm4n, and FBis251. I just added goo manager support. :)
[Samsung Galaxy S (4G Model)] flyers00:
Flashed the latest update this afternoon on wife's phone,wifi calling appeared to work since her phone has been connected to wifi. If its a false alarm about Wi-Fi calling, no big deal because everything is working great. Keep up the good work
[Samsung Galaxy S (4G Model)] mrshonuff:
Do anyone else have the problem with bluetooth in the car? I have to disconnect and reconnect if not it will drop off of bluetooth in the middle of a call. This did not happen when I first bought the phone but after I put gingerbread on there it started happening and it is still doing it on this rom.

(I have a 2008 Nissan Sentra)

Thanks in advance
[Samsung Galaxy S (4G Model)] Shortbus-Driver:
Go back to froyo

Carl
[Samsung Galaxy S (4G Model)] raphifix:
Hey guys: I have a log hopefully capturing the reboots on USB connect (on the 6/26 build). I'm not familiar with everything that's going on, but I believe that the error occurred somewhere in the bottom quarter of the doc. Let me know if I can do any other tests, as I don't believe I am the only user with this problem. Thanks again for your hard work! :highfive:
[Samsung Galaxy S (4G Model)] bot42:
Short bus that belongs in another thread called "need help rooting 2.2.1" with your other comment to Carl, here it doesn't really make sense at all. Unless I missed something.
[Samsung Galaxy S (4G Model)] bhundven:
Yup. I've seen a few complaints now where someone has said something like:

Well, this isn't a stock rom. We work on this stuff in our spare time (you know, when we aren't spending time with our families, school, or work).

If you want the features and stability of a stock rom, install a stock rom.

If you don't know why you would root your phone, and don't know why you would install a custom rom, and don't know how to get logs, then you shouldn't be rooting your phone and installing custom roms!!

If you have no clue... stick with stock.
[Samsung Galaxy S (4G Model)] Shortbus-Driver:
Bot42

#1 my signature is my name.

#2 I was telling the twit above my post to go back to froyo since he didn't have any issues with it but does with everything else.

Carl
[Samsung Galaxy S (4G Model)] FBis251:
No I'm pretty sure you were calling him "Carl". How dare you?