yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] gee one:
I suddenly feel inadequate... :( maybe I need to get an S4 with a bigger screen? On the bright side, I get great battery life.

sent while running with scissors
[Samsung Galaxy S Relay 4G] onebornoflight:
sec_pvs = 0

Hmmmm... won't risk swapping to 3.4 until the charging issues are worked out - that's why I was on stock until the 4.29 experimental nightly. Hoping to get the issues sorted out soonish. Thanks for all your hard work devs!
[Samsung Galaxy S Relay 4G] dillalade:
Gamma correction would be a great touch.

sec_pvs = 0.

I've been on a clean/fully wiped install of build 202 for several days now, below a list of findings, which are consistent in there nature :

A)

Can confirm that bluetooth when connected in my car drops connection when you are being called... the car rings, drops then re-rings (repeatedly)

B)

Incall sound is a little on the low side.

Advanced - Extra in call gain in earpiece sound does a lousy effort in my opinion - completely distorts the callers voice and is irritatingly too loud.

A happy medium would be nice to have.

C)

Noticed how the soft keyboard from time to time pops up smaller then usual... like the individual softkeys are considerably shorter then they usually are (hence harder to use.)

[This has occurred since 3.0 for me tbh & possibly happens only in Whatsapp predominantly.]

Thanks for the update Nard :thumbup:
[Samsung Galaxy S Relay 4G] Braccoz:
mine is sec_pvs=0
[Samsung Galaxy S Relay 4G] TheDigitalBug:
sec_pvs = 0 on mine
[Samsung Galaxy S Relay 4G] stephenclower:
sec_pvs = 0
[Samsung Galaxy S Relay 4G] gtmaster303:
For your reference, regarding my previous post

http://www.xda-developers.com/andro...ry-study-brings-about-surprising-conclusions/

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] dillalade:
That's an interesting read, useful.

I guess it was all placebo :thumbup:
[Samsung Galaxy S Relay 4G] Braccoz:
well i can't speak for current consumption, but i can assure you that undervolting has positive effects on heat generation, thus yelding higher performance by making it less likely to hit throttle temperatures

edit: now that i think about it, since no energy is created or destroyed, if there is less electricity converted to heat then there is consequentially less power consumption. so either the difference in power consumption is negligible considering the draw of all the phone's components, or that guy is simply pulling some bull****
[Samsung Galaxy S Relay 4G] Jason78729:
Undervolting Thoughts

Deleted
[Samsung Galaxy S Relay 4G] gtmaster303:
I didn't mean to derail this thread. If you guys want to talk about undervolting in general please start a new thread in the general section. Do not continue to post here please unless it's specific to our phone or development

Thanks

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] dillalade:
Just updated from #202 to #219.

Very grateful for the Deep Sleep & Charging fix ups (not all chargers however.)

:thumbup:
[Samsung Galaxy S Relay 4G] stephenclower:
I just had a random reboot when initiating a phone call through the Utter voice commands program, and I've pulled /proc/last_kmsg. It's 221K, so please let me know what the preferred method is to get it to you guys to poke through.

Thanks,

Steve

Forgot to also mention that I'm running build 219 from the main apexq build server.
[Samsung Galaxy S Relay 4G] :
You can submit your log through pastebin or you can Dropbox it or email my name at gmail dot com
[Samsung Galaxy S Relay 4G] Jason78729:
Nardholio: I cloned your kernel repository today and I've so far have the following governors working interactiveX, smartassV2, smartassH3, lulzactiveV2, and SavagedZen. Also added the Zen IO scheduler. I need you to pm me on how to submit the files for better review. I've got little programming experience but I can google with the best of them. Also I noticed with the kernel built earlier today the WLan modules now built in but I'm not having any luck getting it to come on. Also the colors look like they've improved. And I know that I should be using the nightly repository because your testing stuff out but I like to play with my phone too. Also I'm using one of the newer Linaro toolchains and so far I'm seeing improvements. The cellular signal seems much improved. It varies at my house but normally 3 bars is good but I've had a steady 4-5 since booting your kernel today.
[Samsung Galaxy S Relay 4G] :
Building wifi in the kernel instead of as a module just eats up memory and most likely will not be integrated into the main builds. It also requires user space changes. The user space repo on my personal git has the fixes you need. Right now I'm mostly working on getting the voltages correct for AVS and trying to fix wifi concurrency. Eventually you'll also get the newest prima driver but that's more of an under the hood thing, the version in there now works pretty well.

If we can convince lbcoder to fix the camera bugs that would be awesome.

Also we need to vastly decrease compiler warnings, i.e. unused variable unused function mismatched types so we can turn back on the strict compiler options the d2 weirdos like.

We're attempting to keep this kernel fairly vanilla, i.e. we never would have considered undervolting except it's actually an option from upstream to let the phone fine tune itself.

I'd encourage you to release your kernel separately. Be sure you tell people the proper user space to use, i.e. a kernel built for my test tree won't work on the nightlies from the main branch.
[Samsung Galaxy S Relay 4G] Jason78729:
I'm barely learning. Just learned how this past month. I'm not quite ready to host my own kernel. I can't even set up a repo on my computer without completely foo-barring it in the same week. I'm hoping at some point I can actually be of more help with the mainstream development. Gotta start somewhere.
[Samsung Galaxy S Relay 4G] stephenclower:
Thanks, Nard. An email is on its way to you with the log.
[Samsung Galaxy S Relay 4G] :
stephenclower: the bug you got is related to the voltage issues we're seeing.

So, a bit of background. Samsung messed up the efuses to read whether a processor was a slow processor and needed more voltage, so they put a bootloader flag in and a hack in the kernel to read it. On top of that, even nominal processors need a bit more voltage than nominal for the 8960 (we actually have the 8260a). Their solution resulted in typically ****ty Samsung code. They used their hack to assign the 0xfafa phones as slow, and then on top of that changed the nominal table so everyone received the slow voltages. That's right, they simply overvolted all the phones rather than fix it, or at least figure out what voltages they did need. We didn't bring the code over because we didn't know we needed it. But we observed 2 things when turning on AVS:

0xfafa phones were already substantially undervolted because they weren't being assigned the slow table. When we turned on AVS they basically got undervolted to the point of severe instability.

Nominal phones have been getting occasional undervolt related hangs with or without AVS.

So what we've done is properly detect the slow phones and assign them the correct table. And we've introduced modest, targetted voltage increases for nominal phones, rather than using the Samsung sledgehammer of overvolting everything. Then we turned on AVS.

So, this is hardly undervolting. In fact, we've had to raise everyone's voltages. Hopefully AVS will do it's job and smooth everything out, and provide a bit of power savings at the same time. And if you have a 0xfafa phone, I'm really sorry, you were very heavily undervolted before, you may actually see a decrease in battery life with AVS.

Got it? Not undervolting, although it may look like it at first blush.

I need testers for my test build 109: http://ls.infernix.net/jenkins/job/apexq-nardholio-3.4/109/

I need the following feedback: Stability and battery life differences, especially if you have a 0xfafa phone

Wifi driver has been updated to bleeding edge. Speed should be excellent. It still occasionally craps out when using bt for Pandora (when changing songs) or the like. I need feedback on differences from the main builds, especially when using wifi and bt at the same time for Pandora or a headset or the like. This is a huge thorn in my side.

Just for fun I've also enabled low latency audio, but I don't know of any way to actually test it.

(and by feedback I don't mean run it for 5 minutes and say it looks like it's working. Unless it actually crashes, in which case I want logs from /proc/last_kmsg, test it for several hours/days at least, do things you normally do, listen to pandora for awhile, whatever)

Standard bug list applies,

Front camera video switch bug/flash while video recording

car chargers

bt/wifi concurrency

You tell me.
[Samsung Galaxy S Relay 4G] stephenclower:
Nard,

Great; downloading now. Re the low-latency audio, is this only enabled for programs which explicitly request it, or is it system-wide? If the latter, I can let you know pretty quickly whether it's working as i rely on the Talkback screen reader to use my device. I picked up an iHome IDM8 bluetooth speaker from Wallgreens last week, and the main apexq builds were working beautifully with it and streaming a station from TuneIn over wifi. I'll let you know if I notice any difference with your custom 109.

Thanks,

Steve
[Samsung Galaxy S Relay 4G] gee one:
I'll give it a try tonight. I'm a light user, so if there is anything specific you want tested on a slow phone, let me know.

sent while running with scissors
[Samsung Galaxy S Relay 4G] chuckiev79:
Gps fails to maintain position in experimental build, had to go back to previous build. I tried to type in commands in terminal emulator but I get not found. Not sure what I did wrong
[Samsung Galaxy S Relay 4G] :
Stability and changes in battery life is all. We put you on the unmodified slow table. You shouldn't need any further voltage increases but let me know (you could probably stand to have them decreased a bit again, actually but I probably will not do that because undervolting is what I'm specifically trying to avoid)
[Samsung Galaxy S Relay 4G] :
None of these changes break GPS, I promise :) Anyway, at the insistence of lbcoder, most of the changes in my test branch have been pushed to the main nightlies, build 223 and up. Enjoy.
[Samsung Galaxy S Relay 4G] stephenclower:
Nard,

After almost a day of use, here are my findings with your custom build:

1. I haven't noticed any improvements to battery life, though my discharge rate feels to be about the same as before.

2. GPS is working fine; I used it on the way home from work last night and when I came back in today.

3. This might be coincidence, but my phone signal has been fluctuating between HSPA+ and Edge. Before, I would see 3.5G on a regular basis.

4. Related to point 3, I apparently received a call yesterday but my device never rang. I only knew about it because she left a voicemail. I tried duplicating that behavior but all other calls rang through normally.

5. Wifi performance definitely feels snappier. Woohoo!

6. Bluetooth and wifi performance don't appear any different with my IDM8 speaker.

Thanks,

Steve
[Samsung Galaxy S Relay 4G] :
[MENTION=5132711]stephenclower[/MENTION]: Your battery life may not have gone up but mine has. One thing in your report kind of worries me a little. Missed calls are a sign the phone is sleeping too deeply. We might have to raise voltages a bit more. I want to wait and see if this recurs though. (Hopefully nobody misses an important call because of this lol)
[Samsung Galaxy S Relay 4G] dillalade:
Jumped to 223, I'm noticing much reduced battery since 219.

Could be due to a cm10 theme I'm using but can't see how that can cause drain (I maybe wrong.)

https://play.google.com/store/apps/details?id=com.blackout1911.theme.BlackedOutTheme
[Samsung Galaxy S Relay 4G] janejunx:
I also had a no-notification missed call (got the voicemail, not the call) earlier today. Reverted to an earlier build.
[Samsung Galaxy S Relay 4G] killkillkill:
Those both sound like what happens when you lose cell signal. Cell networks are ALL notorious for failures of this type. Just being in the wrong place when the call comes in, interference from other devices, interference from solar radiation, cell network congestion, etc. can lead to this. In fact, the symptom of bouncing between hspa+ and edge STRONGLY ties in to possible network and/or signal strength issues. It will only bounce between the two networks if the hspa+ signal is weak or non-existent.

Unless it is easily reproduced (which by the sounds of things, it is *not*), and unless some fault shows up in the phone's logs and/or the phone reboots at the time of the call (kernel panic error), then I would very VERY strongly suspect that the issue is with the cell network and not the phone's software.

If you believe that there is some error happening to cause symptoms like these, collect your logs (/proc/last_kmsg if it reboots, dmesg if it does not -- but within a few minutes of the error happening), READ your logs for pertinent error messages, and ONLY IF you find pertinent error messages, report the issue. If you don't know if your phone rebooted, check the uptime by typing the command "uptime" into the terminal, and seeing if the phone restarted without your knowledge.

janejunx: you have left out very pertinent information in your report, such as (1) what is your approximate location? (2) what is your network service provider? (3) What build number were you using when you missed a call? (4) What build did you chicken out to? I suggest that you were extremely premature to change builds.
[Samsung Galaxy S Relay 4G] gee one:
I'm using 109- I can't tell about battery life yet since I've been using my phone much more than normal today in an area with poor signal.

I am using bluetooth and wireless at the same time and it seems fine.

I did notice a dropped call, but it happens every once in a while, even before I flashed the 109 build. I'm with t-mobile and was previously running a build from back in May, I think.

Things seem stable and smooth. I haven't noticed any reboots.

sent while running with scissors
[Samsung Galaxy S Relay 4G] killkillkill:
..... is 109 a nard 109?
[Samsung Galaxy S Relay 4G] gee one:
Yup, I figured it would have all of his changes.

sent while running with scissors
[Samsung Galaxy S Relay 4G] killkillkill:
Awesome. You're a fafa running avs on the slow table like it should be.
[Samsung Galaxy S Relay 4G] misteropinion:
Does the AVS code keep any statistics and is there any way to view them? I'm running the nard 109 and it has been good for me. I haven't tried the car charger yet.
[Samsung Galaxy S Relay 4G] John5788:
Has anyone seen issues taking a picture and sending it over MMS? I am repeatedly getting the "Service not available" message popping up when I try to text a picture I take via camera. I tested a few things and came to the conclusion that maybe the image compression isn't working and the MMS is trying to send the full resolution image. I resized the image manually and attempted to send and it passed.
[Samsung Galaxy S Relay 4G] stephenclower:
I'll admit that my observations were purely anecdotal, but that was the first time I have ever missed a call on T-Mobile with that phone. In addition, I started off with 100% battery when I left for work at around 7 yesterday morning, and after maybe 20 minutes of talk time, 10 of GPS, and another 15 or so checking mail and the like (which is pretty typical from day to day), my battery was down to 22% when I got home at around 8 PM. Normally, it's down to approximately 70. Something is definitely draining the battery, and I'm trying to determine what that might be. I hope it's a misconfigured app rather than the ROM, but time and better battery stats should tell.

Again, this was running Nard's build 109 he linked to on Thursday. I am running the 7/13 version from apexq for the weekend, but I can flip back to 109 when I head back to eork on Monday if it would be helpful in establishing a pattern.
[Samsung Galaxy S Relay 4G] killkillkill:
Giving the date of the build is meaningless since there are often several builds on the same day, which includes 7/13. Infernix was noticing earlier, some really bad charger behavior, it is my recommendation at this time, that if you suspect you may be experiencing charging oddities, to pull the battery, count to 10, and charge fully from a COMPUTER USB PORT.
[Samsung Galaxy S Relay 4G] :
d2 has MMS sizes set insanely high. I could probably adjust this down for apexq if there's enough call for it.
[Samsung Galaxy S Relay 4G] :
I need someone to test the following build with a variety of USB/AC chargers and also if you have a program like better battery stats that shows voltages that would be awesome.

http://ls.infernix.net/jenkins/job/apexq-nardholio-3.4/119/

I need the following tests: plug in/unplug, make sure the phone properly recognizes the proper state, ie LED on/off, charging animation, leave it plugged in long enough to see the battery percentage actually go up

Boot from off with the charger plugged in, same thing make sure it's charging and properly recognizes unplug.

This is an AVS on build. Very soon I will provide AVS off builds for people who need them. (Also if you have a 0xfafa phone and you would like an undervolted build like we were doing until recently I will provide that upon request)
[Samsung Galaxy S Relay 4G] misteropinion:
I had wondered about this. Is there some process reason why Jenkins can't put the build number is the final .zip name?
[Samsung Galaxy S Relay 4G] :
We'd need to install a Jenkins plug-in but infernix is on travel.
[Samsung Galaxy S Relay 4G] dillalade:
Will give this a whirl tonight and report back
[Samsung Galaxy S Relay 4G] John5788:
Is there a way to configure this myself to revert back to stock apexq sizes? It's pretty annoying to manually resize the images for MMS. I'm surprised no one else has seen this yet.
[Samsung Galaxy S Relay 4G] :
Just grab the messaging apk from an earlier build. The big question is why it doesn't work for you. What carrier are you on? If you can confirm it works with the earlier apk I might adjust the size. I haven't heard any other complaints though.
[Samsung Galaxy S Relay 4G] John5788:
I am on T-Mobile.

I will try the older APK. Additionally, I can email you 2 pictures straight from my camera that I tried to send over MMS that the network rejected to let you try yourself.
[Samsung Galaxy S Relay 4G] :
dilladale: don't bother with that test build. It exhibits the same performance as the main nightlies with the suspect chargers. After much staring at code and logs I realized why we've faced this exact same issue before with the exact same chargers (just that last time the problem kind of fixed itself). There's a hack in the apexq charging code to reassign the detected charger type automagically (probably due to a hardware bug). The problem is there is apparently a second hack somewhere else in the kernel we are missing to make it work right.
[Samsung Galaxy S Relay 4G] dillalade:
Ok.

At least you guys kinda know what's happening.

I must say I've been on build 223 for several days (flashed over 219)

And I am getting verrrry good battery... 20-28 hours 3 days in a row now.

Though I am using the s3 batteries (http://xdaforums.com/showthread.php?t=2333553) with that extra juice (I have modded 4 of them, and I currently charge them via wall chargers, so don't need usb charging as such.)
[Samsung Galaxy S Relay 4G] BrainSlugs83:
I am also on t-mobile, and outgoing MMS messages never arrive for other people. I never get any kind of failed response, but the other people show me their phones and the conversation is just like the picture message was never sent. Edit: Using Builds #224, and #229.

---------- Post added at 10:46 AM ---------- Previous post was at 10:34 AM ----------

Also, using #224 and #229 -- there are definite charging issues. Many times when I unplug the charger it still says charging...

Today, using #229, I drove for an hour, with the phone plugged into to a 2 amp charger -- nothing special, it doesn't send any signals or anything to the phone, I'm guessing those lines are left not connected to anything -- it's just a simple 12V to USB adapter, says it outputs 5v @ 2 amps -- and I had the phone connected the whole time -- I was using Audible over bluetooth to listen to an audio book, and Waze for GPS navigation -- during that hour the battery dropped from 90% to 40% -- it was like it wasn't even connected to the charger -- and when I unplugged the charger, the phone's red LED stayed on (I have mine configured for solid red, not orange) and it still said "charging" -- it's like whatever logic was detecting that it was plugged into the charger and was supposed to be charging the battery had crashed, and just left it in a "I look like I'm charging, but not really" state.

This is 100% repeatable. It happens every time I attempt to charge from something that is not a computer. I have to reboot the phone to get the charger logic to start working right again. :(
[Samsung Galaxy S Relay 4G] klokwyze:
Using #217. Just updated to the latest JB modem & bootloader. Wifi is working now and I must say it's much faster than before. Sweet.

Hopefully wifi hotspot works well. :good:
[Samsung Galaxy S Relay 4G] :
Because we "must" conform to d2, the devs there are balking at changing MMS size, even though they don't own us yet (dragging their feet they are). The official builds will also probably be AVS off for stability (works great for me but it's not for everyone, lbcoder is attempting to fix it)

Having said that, here's an mms.apk I compiled today with the same smaller sizes we used to use. Please report back if this works for those of you with issues. https://dl.dropboxusercontent.com/u/103520801/Mms.apk
[Samsung Galaxy S Relay 4G] :
Lbcoder's been fiddling with AVS, everyone who had issues with it, try the newest build (237)

On another note, I officially give up on the stupid car chargers. The GPIO Samsung used to bypass the FSA9485 doesn't work the same way on this kernel. I have a theory there's a better way to read voltage across the vbus but unless I know what it is I'm stuck. I'm probably just going to disable detection of them, since they don't work anyway.

(The technical explanation is this: USB has 5 wires. Smart chargers send a signal on D+ D- that they are proper chargers www.fairchildsemi.com/ds/FS/FSA9485.pdf

Even most "dumb" chargers can signal they are chargers by shorting or placing a resistor across D+ and D-. The dumbest of the dumb chargers just apply a voltage to vbus and hope the phone takes it. Samsuck placed a hack in the ApexQ code to read these (you'll notice in the pdf I linked to, Vbus bypasses all the FSA9485 logic and goes straight to the charger) but the hack does not work on this kernel. I'm just going to disable the hack. Get a modern charger that shorts the pins. Or modify your current charger yourself. http://xdaforums.com/showthread.php?t=709226 My recommendation if you need to get a new one, shop at a place you can return it in case it doesn't work.

Alternatively, you can wait for us to fix it. You may be waiting awhile though.
[Samsung Galaxy S Relay 4G] :
Please tell me if there are any other bugs not on this list

Bug list:

Minor glitch switching from video recording on FFC (switch to back camera before switching back to still images)

Flash while video recording

Pandora while using Bluetooth/wifi at the same time

MMS sizes set too big?

AVS screwed up for a lot of people.

You tell me.

Wontfix:

Chargers that do not send any signals on D+/D-
[Samsung Galaxy S Relay 4G] scaltro:
This last ROM (0718) is really unstable installed 6 hours ago, my phone already automatically reboot 10 times...

This happen with different apps or menu path.

It was pretty good the previous build numb (0711)

I just upgraded because I had issue with my SD card that a lot of time was not recognized