yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] raziel123:
I've got only got the LTE and 3g option,

No 2G option.

Anyone know how to add it on or if this has to be done at rom level by side?

---------- Post added at 12:18 PM ---------- Previous post was at 12:18 PM ----------

Also is there an option to disable backlight or change backlight settings for capacitive buttons?
[Galaxy S 4 i9505 Original Android Development] lekiaM:
I removed successfully the first line you mentioned, but now the volume is back to low and now i can't change it anymore for more loudness with the volume buttons. Aldo it doesn't matter because the functionality was not proper anyway (for 90 percent) . I guess i take my badly luck and wait for the next release:angel::cool:
[Galaxy S 4 i9505 Original Android Development] OathYvne:
But doesnt your plan need to have call forwarding?
[Galaxy S 4 i9505 Original Android Development] FerrarisIV:
I flashed rom again, wipe data + cache and i installed few apps.

I connected my bluetooth headset.

I made 2 calls, and I had these in call log.

I tapped on Airplane mode, everything were off (Data, wifi and BT)

my call log preserved the 2 calls.

I tapped again on Airplane and everything turned on except bluetooth

my call log preserved the 2 calls again

I turned on bluetooth and it paired with headset.

I checked history calls: it is empty now!
[Galaxy S 4 i9505 Original Android Development] vlk67:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

just edit it
[Galaxy S 4 i9505 Original Android Development] dantemustdie312:
Nooooo, I have successfully flashed stock ROM on my phone but still the camera won't load. Tried different tuts online and still can't fix it. Maybe my rear cam is broken :crying::crying:
[Galaxy S 4 i9505 Original Android Development] Rhoban:
That's odd, a test team member reported volume to be fine after removing

ro.config.vc_call_vol_steps=14 from build.prop.

Also, that line doesn't affect the actual loudness, it only affects the volume steps.

In other words, it was never supposed to make it louder, it was only there to give you the ability to fine-tune the volume.

It is a possibility unfortunately.

The general rule is: If it happens on different ROMs and Android versions, then it's most probably a hardware issue.
[Galaxy S 4 i9505 Original Android Development] blitz0:
The same to me - the sound is not louder after removing this line, just the same low level...
[Galaxy S 4 i9505 Original Android Development] ztlov926:
I'm trying to upload screenshot on this thread but I can't seem to figure out how to do it.
[Galaxy S 4 i9505 Original Android Development] ztlov926:
Wtf, now I just did it.
[Galaxy S 4 i9505 Original Android Development] lekiaM:
Jup that's what i mentioned also before:rolleyes:

Maybe [MENTION=5968293]side[/MENTION] can apply the same configuration settings as it Beta4 for the next Beta6 release? Or program the same settings? Don't know exactly what he meant by "pumping up the volume a little bit" at his github profile. I'm just wondering...
[Galaxy S 4 i9505 Original Android Development] side:
[MENTION=7976298]lekiaM[/MENTION]

its true mate.i increased the volume of all volumes (voip calls,calls,speaker etc)...i will test them all before release.

and yes its for beta6/snapshot2.

although i am thinking to wait for 7.1.2
[Galaxy S 4 i9505 Original Android Development] lekiaM:
Oki excellent! Huge thanks:good: looking forward:highfive::laugh:
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Don't get this the wrong way, but are you sure your hearing is OK?

I just called an automated service and volume was loud enough, even with that line in my build.prop.

I was holding the phone in front of my face (like you would do in normal usage) and was able to hear the message as if it was on speaker. This was on max volume.

But even on the lowest volume I'm able to clearly hear everything when I put the device to my ear.

So, people saying volume is too low either have a unique bug that affects only a few devices or a hearing problem.
[Galaxy S 4 i9505 Original Android Development] lekiaM:
If you asked me, there's nothing wrong with my ears anyway gehehe. It's just a comparison from Beta4 (which has outstanding volume controlling, sound boosting in kernel settings etc.. ) to Beta5.

(Personally for myself i don't want to make a big deal from it anymore. It's not the end of the world. :cool:)
[Galaxy S 4 i9505 Original Android Development] sjamie:
LMAO! The max volume without that build.prop line is much louder to me that it was with that line included. For me, the volume is back to "normal" (beta4) levels. I could still hear people with that line included but at a much lower volume. It was not to my liking and no, I'm not deaf. LoL

Actually, I have above average hearing abilities. :cool:
[Galaxy S 4 i9505 Original Android Development] ztlov926:
Am I just lucky?

I have no issue whatsoever with beta5, I came from jdc team aosp with video recording problem.

Call log history no problem, even of I toggle bt and airplane mode.

Volume and battery work fine.

Running non aroma beta 5, m919

Maybe it's the kernel, just saying
[Galaxy S 4 i9505 Original Android Development] sjamie:
Yes, you described the bug perfectly! :good:

Some of these bugs do appear to affect some users and not others. It is very strange.
[MENTION=5968293]side[/MENTION] is working on a very big update so let's keep our fingers crossed! :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] FerrarisIV:
Thank you.

I also advise another problem (then I stop, promise :P): when the device is off and I switch on, i can see now on the display, in corner top left , only 1 small yellow writing. Until some days ago I saw 1 yellow and 1 red small writing.

and when i manually try to restart it freeze. Have to do long press over power button

Why ?
[Galaxy S 4 i9505 Original Android Development] sjamie:
Hmm... don't know about that one... I see the yellow and red lines of text at various times but never really paid much attention to them. All I know is when the blue line of text appears, the device will boot into Recovery.
[Galaxy S 4 i9505 Original Android Development] jefffrom:
worked like a charm

worked like a charm sph-l720
[Galaxy S 4 i9505 Original Android Development] sjamie:
Yes, I agree! :good:
[Galaxy S 4 i9505 Original Android Development] lekiaM:
1st: Thats absolute normal. One of the reasons is that your are not running an stock firmware/kernel anymore;)

2nd: That's a known issue/bug with almost all custom/optimized Nougat ROM's:silly:

No need to worry.
[Galaxy S 4 i9505 Original Android Development] raziel123:
Browser bookmarks

[MENTION=5968293]side[/MENTION]

Browser is not saving bookmarks, doesn't let you select account to save either.
[Galaxy S 4 i9505 Original Android Development] akk29:
Doesn't 7.1.2 depend on Google releasing the source code which maybe a couple of months away? Or are you able to port stuff from the factory images of the betas?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I think that's what CM did when 7.1 released.
[Galaxy S 4 i9505 Original Android Development] saveprocess:
Does encryption work? If not can you explain why it is hard to implement encryption.
[Galaxy S 4 i9505 Original Android Development] 63ck0:
The blue line says "RECOVERY BOOTING...." while entering recovery.

The red line says "KERNEL / RECOVERY IS NOT SEANDROID ENFORCING" and appears on my phone when using a custom ROM / non-Stock firmware without having SuperSU installed (with SuperSU I do not see that line).

The yellow line says "Set warranty bit : kernel / recovery" and appears when using a custom ROM / non-Stock firmware or recovery, no matter if I have SuperSU installed or not. (As far as I know this message will let you know that now your knox warranty void bit is set to 0x1 if it was not already before; Samsung will refuse a warranty repair of your device if your warranty bit is set.)
[Galaxy S 4 i9505 Original Android Development] Creeper36:
.

I've been changing some of the graphics.

.

.

.
​
[Galaxy S 4 i9505 Original Android Development] Squallzz:
Some issues

For some reason after flashing this, my phone takes a bit longer to start and I can't login to Snapchat?
[Galaxy S 4 i9505 Original Android Development] qsenkcoon:
Can't login into every Google app with my acc

Today my phone had a random reboot and now i can't access the play store because everytime I must login and than the app closed without any error message. Please help and sorry for my bad english.

Btw. I have beta 5 installed with clean flash and everthing was fine til today.
[Galaxy S 4 i9505 Original Android Development] sjamie:
Pull the battery. Wait 30 seconds then boot up device. Should now be fine.
[Galaxy S 4 i9505 Original Android Development] qsenkcoon:
Thank you for the quick reply. i've tryed but it's still the same

I also have gapps reinstalled without success :(

I have added some pic's of the process.
[Galaxy S 4 i9505 Original Android Development] sjamie:
In that case, you may have to full wipe and reflash the ROM, unfortunately.
[Galaxy S 4 i9505 Original Android Development] lyjacky11:
You have to unroot first in order to log in to Snapchat.

I suggest you make a backup with Titanium Backup and reroot your phone afterwards.

Please click the button if this post has helped!
[Galaxy S 4 i9505 Original Android Development] Squallzz:
What should I do to unroot?
[Galaxy S 4 i9505 Original Android Development] demlasjr:
That's weird, snapchat always worked for me without unrooting my device
[Galaxy S 4 i9505 Original Android Development] Squallzz:
I just unrooted and I was able to login to Snapchat but now I can't figure out how to root again. :(
[Galaxy S 4 i9505 Original Android Development] demlasjr:
If you completely unroot through Supersu app, search for SuperSU package on xda and flash it through recovery and you're done.
[Galaxy S 4 i9505 Original Android Development] Squallzz:
This? https://xdaforums.com/showthread.php?t=1538053
[Galaxy S 4 i9505 Original Android Development] dev1t:
Same here L720T on Ting CDMA (Sprint). Is there a firmware or modem we can try flashing?
[Galaxy S 4 i9505 Original Android Development] nothingman1976:
Does this rom have root enabled by default ?
[Galaxy S 4 i9505 Original Android Development] newtonfoc:
Yes
[Galaxy S 4 i9505 Original Android Development] pegasx:
I had random reboot problems on stock rom 5.0.1. First I bought a new battery but problem had continued. So I decided to install LineageOS. It is really nice and fast. But I still have random reboot problem. Any suggestions? Thanks.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Check your power button.
[Galaxy S 4 i9505 Original Android Development] ztlov926:
Have you checked the battery if it's not loose, maybe the terminal is losing contact when you move the phone, try to put anything between the bottom of the battery and the phone.
[Galaxy S 4 i9505 Original Android Development] pegasx:
If the problem is related to power button, the problem should be loop reboot, not random reboot, right? The power button seems normal, how can I check it?

Old and new, could two batteries cause to lose contact? I do not think so, but I'm gonna try. Thanks.
[Galaxy S 4 i9505 Original Android Development] ztlov926:
It means that the battery is not the problem, check the terminals of your phone if it touches the battery terminals properly
[Galaxy S 4 i9505 Original Android Development] pegasx:
I have put a soft plastic part between the bottom of the battery and the phone. But still have random reboots.
[Galaxy S 4 i9505 Original Android Development] siginor:
Like [MENTION=8093553]pegasx[/MENTION] I have some trouble with random reboots.

Sometimes, when I click the power button, my phone shows the turn off menu and then my phone turns off (even if I click the return button to leave the menu). To reconnect the phone I have to take the battery off and put it back.

This happens two or three times a day.

Idk if it's a ROM problem or my hardware phone. Any ideas?

Sorry for my bad English.
[Galaxy S 4 i9505 Original Android Development] lekiaM:
I think it's a hardware issue, i don't think it's ROM related. A smartphone is like a computer, some internal stuff can be broken too. Or not functioning properly anymore like it supposed to do.:eek:

P.s think of all the miniscule things inside your device.
[Galaxy S 4 i9505 Original Android Development] andy hall:
There are some videos on YouTube about dodgy Samsung power buttons. They can get filled with fluff.
[Galaxy S 4 i9505 Original Android Development] ztlov926:
Definitely not the terminals then:confused:
[Galaxy S 4 i9505 Original Android Development] ztlov926:
Check this also just to be sure

:)
[Galaxy S 4 i9505 Original Android Development] ztlov926:
The terminals of your phone
[Galaxy S 4 i9505 Original Android Development] sheLby359:
I've installed the ROM, but im stuck on first boot. Screen is black and led is blinking all the time. I'm already waiting 20 mins, should I put off the battery or wait? :v

Guide says to put off battery only when led stopped flashing..
[Galaxy S 4 i9505 Original Android Development] Ldjcdo:
The terminals of these phones function by spring action to put pressure on the battery contact plates so that a good connection is insured.

To my mechanical understanding, your issue must be related to either the phone physical connections or to the power button.

To check if it is the contacts, with something similar to a credit card, that you are sure that is straight, touch gently the metal connectors. As they are more than two, a straight line will be defined. All of the contacts must me on the same line. If there is one that isn't touching the card, there's your culprit.

Years ago, the system was in reverse. The battery had clips that received solid metal contacts from the phone. They failed, as the newer contact planar Springs do. Everything mechanical has a time for wearing out, so check it out.

Enviado desde mi SGH-I337M usando XDA Forums PRO
[Galaxy S 4 i9505 Original Android Development] lekiaM:
Deleted

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

Thats a known issue for some devices (had the same problem). That's why you have to flash the Gapps 'after' you installed the ROM. So setup the "tap&go"settings first, go back to recovery and flash the Gapps, without wiping after installing. Also there's no need to wipe the ROM after installing to.

So;

1st wipe everything (not Micro Sdcard and USB OTG?) format data.

2nd install ROM (do not wipe after installing)

3th setup the "tap and go" settings

4th back to recovery

5th flash Gapps (also do not wipe after installing)

6th everything should be fine at booting
[Galaxy S 4 i9505 Original Android Development] sjamie:
It's definitely a hardware issue. My S3 has the exact same problem which was my motivation to get the S4.
[Galaxy S 4 i9505 Original Android Development] xell75:
Guys, it seems the endless reboot bug is Kernel related cause with the newest Sidecore Kernel the reboot is like normal and fast. :D
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Wrong.

It's random. The fact that it worked fine after you flashed sidecore is just a coincidence.

Sometimes it works and sometimes it doesn't. I haven't seen any pattern.
[Galaxy S 4 i9505 Original Android Development] side:
this is true.i will try to see whats going on on the next days(today-tomorrow etc)
[Galaxy S 4 i9505 Original Android Development] pegasx:
I guess it is heating problem. I put the phone on the table and started youtube videos. It has rebooted again after 5 minutes. When the head parts (left and right side of back camera) get heated, phone has random reboot problem. Battery does not get heated.

First I installed "L speed" and choosed battery mod. And then I uninstalled Facebook (nowadays people say Facebook's updated app has problems). After that I changed Launcher, Google Now to Pixel Launcher. It seems that problem is solved for now. But I'm not sure.
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
If it is really the power button, then before the reboot the power menu must be visible. If that is NOT the case it can't be the power button.
[Galaxy S 4 i9505 Original Android Development] raziel123:
[MENTION=5968293]side[/MENTION]

I don't know of any of you guys have the same issue, but YouTube sometimes freezes video, whilst audio continues playing,

Restarting YouTube and skipping to the section solves the issue,

Its intermittent,
[Galaxy S 4 i9505 Original Android Development] lyjacky11:
If you use SuperSU, you can use the Full Unroot option in the settings of the app (scroll down)
[Galaxy S 4 i9505 Original Android Development] jefffrom:
remove the sprint sim card worked for me the only downfall you will only have 3g data speed but talk text will work just fine
[Galaxy S 4 i9505 Original Android Development] xmicroman:
I have FreedomPop plus my Sim card is bad, turns out you don't even need a Sim card to get 3g. Fine with me free data up to 1gig I have WiFi every place I go.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Holding the power button long enough will simply shut down the phone and the menu will never show.

This is what would happen if the power button is stuck.

Therefore, my theory still stands. You're welcome to try it.

That is because you're playing videos at 1080@60fps. It should work fine with 720@60.
[Galaxy S 4 i9505 Original Android Development] pegasx:
Problem is not solved. It is getting worse.
[Galaxy S 4 i9505 Original Android Development] raziel123:
Bookmarks sync

[MENTION=5968293]side[/MENTION] is there a bookmarks sync adapter apk for 7.1.1?

I searched on Google couldn't find it,

I remember it used to sync stock browser bookmarks back in the days,

---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------

What's it caused by then?

I never for this on other roms

---------- Post added at 09:03 AM ---------- Previous post was at 09:00 AM ----------

I'm not playing videos at 1080 60fps,

My screen resolution is set at 720p (resolution changer) to boost GPU performance, video playback maxes out at 720p 60fps
[Galaxy S 4 i9505 Original Android Development] xell75:
I thought that 1080p @ 60fps problem only exist in S7 Ports when our devices calls "SM-G935F" in build prop? I never had such a bug with non S7 ports aka there the device just calls GT-I9505
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I have been having the problem on Lineage ROMs, so it's definitely not port exclusive.
[Galaxy S 4 i9505 Original Android Development] saveprocess:
This ROM bricked my device. I created a new thread about it.
[Galaxy S 4 i9505 Original Android Development] side:
http://prntscr.com/ecth8r

you really believe a rom can BURN your phone ?
[Galaxy S 4 i9505 Original Android Development] saveprocess:
That is a sticker over a giant crack on a front facing camera. Happened many months ago.
[Galaxy S 4 i9505 Original Android Development] side:
dont u think its a bit insulting, to believe that this rom can BURN ur device?
[Galaxy S 4 i9505 Original Android Development] saveprocess:
I didn't write burn, I wrote bricked, as in unusable.
[Galaxy S 4 i9505 Original Android Development] side:
you can simply flash the stock again .if u got problem with that,its not optcm's rom issue.

also keep in mind...

* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
[Galaxy S 4 i9505 Original Android Development] saveprocess:
I knew that, you don't have to lawyer up :D

I just want to fix my phone.
[Galaxy S 4 i9505 Original Android Development] lekiaM:
[MENTION=7839731]saveprocess[/MENTION] :LoL, the developer will laugh at you and hard. Come on man, how sad can you be to start a thread about your own selfness experience! [MENTION=5968293]side[/MENTION] is a well known qualified, devoted developer. Don't come blame him after you did something wrong. What will people think? Don't put something in a bad position please. Be a guy, and take your brick.
[Galaxy S 4 i9505 Original Android Development] side:
any evidence to prove that this rom bricked your phone?

are u sure that u fully wiped the device before the installation of this rom

its too shame to blame someone for something ,when u cant prove it.nevermind :)

case close-no hate at all

wishing u the best about ur device
[Galaxy S 4 i9505 Original Android Development] saveprocess:
I started a new thread to get help from someone to make my phone usable again.

I used crDroid before this ROM. I followed directions how to install it- clear cache and full wipe. I used this ROM for a few days, the last thing I was doing was looking at settings in Contacts app, specifically page where there is an option to record voice. Then phone froze and I had to take the battery out. I couldn't boot up the phone after that. There is a possibility that this is a previous hardware issue, but this happened 2 days after installing this ROM...
[Galaxy S 4 i9505 Original Android Development] lekiaM:
Deleted not relevant.
[Galaxy S 4 i9505 Original Android Development] xell75:
Hmm okay. But what is the problem with YouTube anyway? With for example Mx Player I can play 1080p 60fps smoothly so why it won't work on YouTube?
[Galaxy S 4 i9505 Original Android Development] eTaurus:
Connection speed?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I have no idea. Could be an app problem.

But I don't really care, I won't die just because I have to watch a video in 30 fps instead of 60.
[Galaxy S 4 i9505 Original Android Development] Buff99:
You have to understand how players work. Some, like YouTube and netflix use the system codecs. Some like mxplayer or vlc ship with their own codecs, often super optimised for their own purposes.

The setup for system codecs in lineage for S4 isn't very successful for some circumstances. All ROMs that use lineage source on S4 have this, including RR. I have tried to play with this a little but only succeded in losing audio sync.

From what I have seen adaptive bit rate or extremely high bitrate YouTube movies are problematic. FWIW my note 8.0 RR port has better YouTube performance than i9505....

This is a video I was using as a test case, 720p60 but highbiitrate.. Sometimes pauses on S4, solid on note 8

[youtube]bOEmTmfUwEw[/youtube]
[Galaxy S 4 i9505 Original Android Development] markiarom:
No framedrops at all here :D
[Galaxy S 4 i9505 Original Android Development] lekiaM:
Same here: https://m.youtube.com/watch?v=79ImZE0K7xc

No issues. Aldo i see a reduction in quality in comparison while playing video on my 2nd device with Beta5. I guess is codec related, browser related or kernel settings related? I don't know. Anyways, no stuttering (framedrops) issues on both ROMs:cool:
[Galaxy S 4 i9505 Original Android Development] Buff99:
I didn't say frame drops. Video pauses and sound keeps going as the original poster said. Use the YouTube app and make sure you force it to 720p as it will default to lower.
[Galaxy S 4 i9505 Original Android Development] lekiaM:
Will do using YouTube app.

But i meant the video(which i played also) worked for me also without pauses, without flickering, without stopping (and only sound hearing etc..) while playing in Browser.I couldn't find the right words for confirmation, so i thought "frame drops" where the right words for it.

[MENTION=1711160]Buff99[/MENTION] Edit: Confirmed. Strange. While playing the same video in the App at 720p60fps, same happens as you mentioned. Reducing to 480p, no problems.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I don't think the browser supports playing at 60 fps.

And at 480p it's not 60 fps anymore as far as I know.

So yeah, the problem is only YouTube videos playing at 60 fps.