yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] Danvdh:
hmmm I'm trying to find out what this audio glitch is, can you be a little more specific?
[T-Mobile Samsung Galaxy S 4] mrvirginia:
camera/gallery is packaged together in 4.3. so when i loaded up the old gallery/camera, i tried to delete a photo but i still saw it there with root explorer. i'm thinking it's a permission in the firmware that is tied to the gallery app, which is why it doesn't work when we use Camera JB+ gallery app, because it's built essentially the same way.
[T-Mobile Samsung Galaxy S 4] Danvdh:
I deleted the question because I had a brain fart and replaced it with another :P
[T-Mobile Samsung Galaxy S 4] epsix:
[MENTION=2651267]mrvirginia[/MENTION] , how can you tell if front facing camera doesn't work on 720p?
[T-Mobile Samsung Galaxy S 4] mrvirginia:
turn your volume on the handset all the way up. now wait about 5 seconds or so. now hit up on the volume rocker again. at the very beginning of the beep, you'll hear some distortion. this distortion is present here and with dial-pad touch tone when you hit the first number.

pretty sure this deals with the audio_effects.conf file in system/etc

which points to some lib changes. if you do a diff compare from 4.3, you'll see what i'm referring to. i've been doing a lot of digging around today trying to get to the bottom of these last few nagging things

[MENTION=4830253]Danvdh[/MENTION] i honestly don't know a whole lot about where these system ui sounds come from. trying to research and locate.

when you switch to FFC, hit settings, picture size. there is only QVGA/VGA. there should be 1.5 and 2mp as well.
[T-Mobile Samsung Galaxy S 4] rockstarar:
Try it yourself! On the camera app the highest you can go is VGA for front
[T-Mobile Samsung Galaxy S 4] therourke:
thanks for the insights! I will will wait for your new ROM and try all these tips. Installation from scratch is my last hope :)
[T-Mobile Samsung Galaxy S 4] rockstarar:
[MENTION=2651267]mrvirginia[/MENTION], do you by any chance have a stock gpe kernel zip I can flash?

Edit found it you're the best
[T-Mobile Samsung Galaxy S 4] mrvirginia:
new changelog so far is just updating Exchange Email to 4.4 and *maybe* reverting to 4.3 camera. i would have to do extensive testing with the 4.3 camera on 4.4 to ensure there are no force closes. nothing wrong with current Kernel.
[T-Mobile Samsung Galaxy S 4] marscandybars:
Standard browser crashes if I try to launch incognito mode, WiFi tethering does not have hack so I am blocked from tethering on the unlimited plan and front facing can has VGA as highest resolution :/
[T-Mobile Samsung Galaxy S 4] LoopDoGG79:
I thought the unlimited plan came with 2.4 gigs of tethering? :confused:
[T-Mobile Samsung Galaxy S 4] mrvirginia:
i've said this quite a few times now.... AOSP Browser is a little rough right now. i didn't make it, i just put it into the ROM. this is just how it is right now for 4.4.

i JUST discussed FFC and VGA res.

WiFi tethering might get fixed when i update GPE CSCs.

this is the absolute last time i discuss the same issues. read and search the thread. it's really not that difficult considering i sit here and read pages upon pages upon pages on different threads to teach myself and learn.
[T-Mobile Samsung Galaxy S 4] nivekx9:
Its when you change the audio/speaker. If you click it once the sound screeches but from then on it changes smoothly, until the volume changer goes away and then it screeches on first press again.
[T-Mobile Samsung Galaxy S 4] laureanop:
I have unlimited plan and Wi-Fi tethering works fine.
[T-Mobile Samsung Galaxy S 4] epsix:
Darn.... It sure sux with QVGA /VA front facing camera. I video chat alot, wonder if we can use 3rd party camera from playstore till this get fix. :confused:
[T-Mobile Samsung Galaxy S 4] mrvirginia:
4.4 Cam to 4.3 cam

Restores 2mp functionality to FFC

this will delete your 4.4 camera and replace it with 4.3. i would backup both GalleryGoogle.apk and GoogleCamera.apk just for keeps sake for now before flashing this

http://apollyon-dev.com/extras/4.4_to_4.3_Camera.zip
[T-Mobile Samsung Galaxy S 4] mrvirginia:
i have updated Q/A some and will continue to do so as we go
[T-Mobile Samsung Galaxy S 4] epsix:
You're awesome buddy, thank you :thumbup:
[T-Mobile Samsung Galaxy S 4] RBalber:
[MENTION=2651267]mrvirginia[/MENTION] I would like to take this time to say thank you for all the hard work you do for putting forth a superb ROM for us users. I usually remain pretty dormant on the forums but read through everything everyday. I just now wiped and installed 4.4, I'm letting it settle in then rebooting. I appreciate you taking the time to answer the majority of everyone's questions though many have been asked over and over again. I know a lot of time, work, stress, etc... go into this.

To everyone else, please make sure you're searching the thread before asking questions. I don't know how many times mod's have asked this and have stated to check the Q&A or just the search tool. I've seen many MODS give up because they get frustrated with people. Just wanted to shout out that your work is appreciated. Thank you sir!
[T-Mobile Samsung Galaxy S 4] HenryTheUnicorn:
Please add how to disable notifications for the 4.4 update for us still on the 4.3 Virgin Rom.
[T-Mobile Samsung Galaxy S 4] roblxskye:
Nice work fixing camera issue with the 4.3 camera zip.
[T-Mobile Samsung Galaxy S 4] The Apostle:
This has been covered a few times. Check post 2813, or SEARCH.

sent from my jelly bean droid (SGH-M919)
[T-Mobile Samsung Galaxy S 4] a103:
Hopefully 4.4.1 will fix most of the issues for GPE devices. Just read it online so thought of sharing it -

http://m.androidauthority.com/android-4-4-1-kitkat-nexus-5-nexus-4-nexus-7-322102/
[T-Mobile Samsung Galaxy S 4] Dr. Fed:
As Mr. Virginia said, this is not rom related. I used to think so as well, because my phone could still wake up during a phone call (if I hit the power button) on 4.3 roms. The screen would still shut off immediately after answering, but I could force it to wake up. My conclusion is that 4.3 roms handle the proximity sensor differently than 4.4 roms. With 4.4 neither the power or home button can override the proximity sensor. As a result, if dust is causing it to shut off the screen as if the phone is next to your face, it is impossible to turn the screen back on until the other number disconnects. I may be wrong, but I'm buying some canned air hopefully soon and will test.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
they know they messed a lot of things up with this release for GPE devices specifically. I'm hoping before end of week we're on 4.4.1
[T-Mobile Samsung Galaxy S 4] JaZart:
Hopefully but it probably won't be for another week or two for the GPE. Could be as late as early January.
[T-Mobile Samsung Galaxy S 4] jmulla718:
Anyone having problems with gmail not syncing?
[T-Mobile Samsung Galaxy S 4] mrvirginia:
the article i read (not that one)

was talking about the HTC One so I think we should see it relatively soon. I hope.

when you have syncing turned on, you need to go into your Google account and enable gmail sync
[T-Mobile Samsung Galaxy S 4] cptsmidge:
I was, but I cleared data/cache for the Gmail app in the App Info area. That worked for me.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
added to Q/A section located on first page. it's now the first question and answer
[T-Mobile Samsung Galaxy S 4] therourke:
A warning for people...

It would be a pretty amazing coincidence if these things weren't related, but all these reboots may have knackered my phone.

It refuses to recognise the SIM card. I have tried everything, from alternate modems to completely resetting to Samsung factory firmware. My hope is that only the SIM card is broken, and was corrupted or something, but it might be the case that my motherboard overheated. I will only find out when I get my hands on another SIM. A waiting game.

For now I would recommend to anyone suffering random reboots to go back to 4.3. It's not worth the possibility that your phone gets balked
[T-Mobile Samsung Galaxy S 4] mrvirginia:
random reboots shouldn't be happening at all, though. i, as well as several other users here, haven't experienced it once.

issue with your sim card is unrelated and is complete coincidence. totally possible your phone has overheated, though. still unrelated to the ROM.

further, if you've factory reset to stock Samsung firmware, this is more evidence that it's your sim card haha. hope you get it sorted, mate.
[T-Mobile Samsung Galaxy S 4] Black SER:
mrvirginia my front camera only goes to vga mode and i'm getting a weird sound when i raise my volume..oh and do you know why my AOSP browser is acting weird? Totally kidding (phewwwww as you can tell I did tons of reading and kinda made me sick of the same questions asked over and over again. You are a very patient Developer.

Seriously thou...I'm about ready to jump into 4.4, but I have a M919 with Net10 (ATT). I saw an earlier post about modems and thats the tricky part for me. I'm currently using your 4.3 and loving it. My understanding is that so far the only bugs are camera related. I think I will hold out a few more weeks since 4.3 seems to be running flawless at the moment. Keep up the great work and glad to see your 4.4 rom has made so much progress since beta1.

P.S What is GPE? (Google Play Edition..maybe).
[T-Mobile Samsung Galaxy S 4] a103:
Yes GPE stands for Google Play Edition lol :D
[T-Mobile Samsung Galaxy S 4] Mralexander006:
If it helps knowing this at all, I have an M919 and use it with StraightTalk's AT&T LTE ($45/m unlimited, 2.5 GB LTE throttle). I did the whole flashing the modem.bin deal explained in the Q&A, and flashed the GPE CSC file thing, and my phone connects to the network fine, without me having to add the APN. StraightTalk != Net10, but they are similar AT&T MVNOs. Occasionally my connection to googles servers drops momentarily (while I keep my bars of network connectivity), but my understanding is that that is an issue on Google's end (?).
[T-Mobile Samsung Galaxy S 4] mrvirginia:
thank you.

for those that aren't on 4.4 yet, i would wait until 4.4.1 is rolled out. i believe it will fix most of the firmware issues that are currently present in 4.4.
[T-Mobile Samsung Galaxy S 4] H3adru5H:
I went back to 4.3. 4.4 just isn't as smooth for me and while the radio flash to MK2 gets rid of data drops, it's still somewhat wonky and I don't get service in places that 4.3 gives me. Maybe I'll give it another whirl in a month or 2.

Virgin 4.3 is perfect in my eyes and I average 20 hours with 3-5 hours screen on time. Stock kernel, no modifications to it, full or half brightness and no data disabled.

I do have a question though, is there a way I can get CMs messaging app working with this ROM? It'd be nice to have quick reply.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
again, 4.4.1 should iron out any issues that were introduced by Google/Samsung

you could try pulling it from a 4.3 AOSP ROM
[T-Mobile Samsung Galaxy S 4] H3adru5H:
Don't get me wrong I'm not complaining :) just sharing thoughts. It's really no biggie as I said I'm completely 100% satisfied with Virgin 4.3. Really is the best ROM I have ever used and I truly appreciate your work man!
[T-Mobile Samsung Galaxy S 4] The Apostle:
I am noticing that on 4.3 that Google Play services is eating to much battery. Is this because I have not yet disabled the 4.4 updater notification?

**not sure why the pics posted 2x**

sent from my jelly bean droid (SGH-M919)
[T-Mobile Samsung Galaxy S 4] mrvirginia:
nope, this is just because of terrible Google Play Services. CacheUpdateService is causing this wakelock. you need to download Disable Service from Play Store and navigate to it. every now and then this wakelock will pop back up. supposedly it deals with Google Wallet.

edit: where i mentioned this before and steps to take care of it

http://xdaforums.com/showpost.php?p=47653986&postcount=2353
[T-Mobile Samsung Galaxy S 4] therourke:
My phone is officially broken. Not a SIM issue, a hardware issue.

I am obviously disgruntled by this, but I only have myself to blame for messing about with ROMs and such like. I should just reiterate though that if you are having the same symptoms as me on 4.4 - i.e. random reboots - you MUST go back to 4.3 or another ROM immediately. It is quite likely that this issue is what broke my phone. I am now phoneless, until further notice.
[T-Mobile Samsung Galaxy S 4] sdmark:
Sorry to hear your phone died... I agree with the previous post though, I don't think this is ROM related. It could be purely coincidental that your phone (hardware) died while trying this ROM. Good luck with future phones. Don't let this stop you from rooting and romming
[T-Mobile Samsung Galaxy S 4] mrvirginia:
there is no proof that a random reboot had anything to do with your hardware failure. before you said you were having issues with your SIM. now you're saying hardware issue. it seems like you're quite uncertain as to what the issue is exactly :confused:

lots and LOTS of users had reboot issues in Jamal's thread and not one of them have experienced hardware failure. it's more likely that your phone just bit the dust. i would factory reset to stock and send it in under manufacturers warranty and keep everyone in the thread updated as to the actual cause of your hardware failure versus blaming flashing custom ROMs.

if you do not feel like keeping us up to date, please refrain from posting things that are untrue. thanks :)
[T-Mobile Samsung Galaxy S 4] therourke:
Fair enough, but I do think it's fair to warn people with reboot issues. I have an i9505 UK phone, and I have read many people on here with international phones having similar reboot issues to me. My phone suddenly stopped recognising sim cards. I have tried another sim in the phone and the problem remains. I have tried my sim in another phone and the phone recognised my sim perfectly, hence, my S4 hardware is knackered.

I will be getting a replacement/fixed phone and I will continue modding my phone. I will keep you up to date, but just be aware that if this happens to anyone else, then I did warn you :) Hopefully this is just pure coincidence, but that seems crazy unlikely. I will let you know.
[T-Mobile Samsung Galaxy S 4] RBalber:
Given that there are so many variables besides the "ROM" "MODEMS" you would have to overview your whole process on what you did. Everything from running Odin 3.09 in phone vs. pda as administrator and making sure it says pass on each step, to making sure you check the MD5 on zip file to make sure you didn't download a corrupt file could be culprits. I have a fully functioning 4.4 GE ROM from [MENTION=2651267]mrvirginia[/MENTION] working with the properly patched MK2 baseband. And besides the issues he's stated were present because of Google, there is no reason this doesn't work as it should work in its current state.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
if you're having SIM issues, the only thing i can figure is that the baseband flashing has had ill effects on your device. however, if you were able to restore to stock and have been able to confirm that your baseband is as it should be now, then there's no reason why anything contained within this thread would cause issue with your SIM card being recognized in your device. i personally believe your SIM tray in your device is defective and is likely what will be fixed upon return to you. i wish you the best of luck. again, please keep us updated.

for everyone else:

i will probably only be supporting T-Mobile M919 devices with the release of 4.4.1 due to the baseband/signal loss issue. i personally cannot keep track of firmware releases for other i9505 variants and thus do not know which basebands to recommend to International/ATT users. if you do not keep track of your own official firmware releases, i'm not sure how anyone could expect me to.
[T-Mobile Samsung Galaxy S 4] RBalber:
suweeeeeet good thing i'm on t-mo :p
[T-Mobile Samsung Galaxy S 4] mrvirginia:
exactly why support for other i9505 variants will be dropped on 4.4.1. i know for a fact that it works on our M919 i9505 devices. this thread was only originally intended for our devices but i expanded support because the users wanted it.
[T-Mobile Samsung Galaxy S 4] Fenny:
A good warning, I wonder if this has to do with the baseband/radio in the international version of the device. My guess is that if there is any relation to your SIM failing, then perhaps it is because your device rebooted while in the process of writing to your NV... maybe with a function that the software layer is trying to execute on the radio layer that does not exist on that radio version (this would definitely cause a reboot in a more extreme case)... But there is every chance that the two are unrelated.

*EDIT*

It makes me think though. :D
[T-Mobile Samsung Galaxy S 4] therourke:
I have a twist in my tale of woe, and a somewhat happy ending.

Today I have tried everything to fix my sim issue. Factory resets, flashing original samsung firmware (via odin .7), flashing modems blah blah. I was preparing my phone for a full factory reset so the shop would swap it, and I ran TriangleAway. When my phone rebooted it had found the sim card! What's more, TriangleAway did not work, my flash count still reads at 51 (a lot of modding).

Now, I am embarrassed :-$ but still wondering whether this is a coincidence. After a few reboots everything seems fine again. I have flash Virgin 4.3 and at the moment I have my phone back to normal(!)

What could Triangle Away have done to solve my sim issue? Did it reset and refresh something that my previous flashing had broken? I don't know. My sim issue started randomly this morning. I had been running my phone on 4.4 yesterday fine and woke up to the terrible 'no sim detected' message. i.e it didn't break straight after I had done any software changes.

Apologies for all this nonsense. I hope it is helpful in some way. My phone may break again. I will let you know.

And thanks to you mrvirginia for your patience. It's a shame you won;t be supporting other phones from 4.4.1. This is still the best rom I have used so far.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
it's an extremely curious case. there are always a plethora of variables to consider so it could honestly have been caused by a number of things. the baseband/radio thing is just what comes to mind since we're talking about SIMs and we're having to use, essentially, a baseband hack to get things working as intended.

i'm very glad to hear that your issue is now fixed. i can only imagine it must be a terrible feeling to think you might be without a phone.

i do not know a great deal about TriangleAway and how it explicitly works with S4 devices. maybe the developer of it could give you some more insight here. i think that you just had a bad flash of something somewhere and it caused issues. no need to apologize. i would never run something personally if i felt it were broken or unusable, rebooting included. i would never release it.

International/ATT users are more than welcome to flash 4.4.1 when i update to it. however, i cannot offer any help with baseband/signal loss issues for those users since i do not know which basebands to recommend from your firmwares. i do not keep a close watch on them. it is my opinion that a user should know this information, just like i know which firmwares are for T-Mobile (we only have 3 thus far). each other respective country/carrier should have, what, 4? maybe 5 different ones now?

further, i cannot test software i have packaged together and guarantee the integrity and functionality on a device i do not have in hand.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
thank you, Gerald! :highfive: i'm not sure who you are, but thank you.
[T-Mobile Samsung Galaxy S 4] The Apostle:
Again, Thanks

What a great program. As well as clean and simple.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
yes sir. it gets the job done :)
[T-Mobile Samsung Galaxy S 4] epsix:
Heard someone said about the crackling noise/sound when turn up the volume key? Well after I install viper4android sound enhancement app its gone and my sounds are awesome. I post it theme section check it out. This us what KitKat should be.:D:thumbup: and yes there's an IRS beat mod too.
[T-Mobile Samsung Galaxy S 4] HenryTheUnicorn:
Ty

Also I found out that u can also touch and hold the notification, wait for App Info to pop up, click it, then uncheck "Show Notifications".

or just go to Google Services Framework in the App manager, then uncheck "Show Notifications".
[T-Mobile Samsung Galaxy S 4] mrvirginia:
thanks [MENTION=3805293]marketingmike[/MENTION] :highfive:
[T-Mobile Samsung Galaxy S 4] mrvirginia:
thanks

this reminds me of something but i can't quite put my finger on it...

i'll try to remember your post tmw.

yes, that also works. i wasn't sure if rebooting enabled the notifications again.
[T-Mobile Samsung Galaxy S 4] HenryTheUnicorn:
Nope works perfect. You should add that as a second method in the QA, its faster to do and easier.
[T-Mobile Samsung Galaxy S 4] jmulla718:
Is it me or is KitKat is draining the **** out of my battery. Lol. I can't even last 6 hrs with out charging.
[T-Mobile Samsung Galaxy S 4] mrvirginia:
just you.

wakelock?

I just put my phone back on the charger from 7:20am. I was at 56%. mostly idle time today. tmw I'll stream spotify for an hour and report back

that was with 1hr and 50min screen on time
[T-Mobile Samsung Galaxy S 4] jmulla718:
Well I play games for about 1hr, check emails, social media web surfering music. Before I was coming back home after 6hrs with about 60% batt.

Also what is wakelock?
[T-Mobile Samsung Galaxy S 4] Danvdh:
Hey I will gladly answer this for you

In order to prolong battery life, over time Android devices will first dim, then turn off the screen,

before turning off the CPU. Wake Locks are a Power Manager system Service feature, available to your

applications to control the power state of the host device.

Wake Locks can be used to keep the CPU running, prevent the screen from dimming, prevent the screen

from turning off, and prevent the keyboard backlight from turning off.

with this being said, an app you installed is responsible for this OR the method you used to flash, you can start by downloading greenify free from the play store and use it to hibernate every app you don't running in the background ( do not hibernate apps you require notifications from)

hope this get's you going

Cheers!
[T-Mobile Samsung Galaxy S 4] jmulla718:
Thanks for explaining it well... Well on TW, I have the same apps I have now on 4.4 and I was getting way better battery life... other that is cool.. thx
[T-Mobile Samsung Galaxy S 4] GoreTan:
First of all, thanks for the great ROM.

I have a quick question - will the potential signal drop issues be fixed by the upcoming 4.4.1 ROM - that is - do I still need to flash a modem/radio if I experience the signal loss issue?
[T-Mobile Samsung Galaxy S 4] HenryTheUnicorn:
Yes u need to flash a modem/radio to fix the signal loss problem. It is in the QA in the first few posts.

Not sure about 4.4.1
[T-Mobile Samsung Galaxy S 4] jmulla718:
Hey should I switch to ART ?
[T-Mobile Samsung Galaxy S 4] Danvdh:
The volume down/up sound is a method in volumepanel.smali in framework.jar but I don't want to deodex to recompile framework I doubt I'll ever be able to ODEX again

then again I don't know why we are holding ART in such high regards when these ROM's are quite useless IMO without xposed and GB or at least some modules, I can see how good ART is on AOSP based ROMS with massive features already baked in, but let's be honest pure vanilla android is a little boring no?

hmm interesting, Dialer distortion goes away with "touch sounds" enabled, it's back without it enabled, this is very very strange