yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Rhoban:
7.1 was not officially released as far as I know. There's a dev preview and then there's the Google Pixel software.

The 7.1 custom ROMs we have is based on either of those.

The official release of 7.1 will probably some time during December.
[Galaxy S 4 i9505 Original Android Development] Dr Goodvibes:
Galaxy i9505 AOSP 7.0 Battery use.

Model: i9505

Version: Android 7.0 (20160909 )

Telephony Signal: 100% or full signal all the time.

WiFi: Enabled all the time during monitoring.

LTE: Disabled.

The following is the battery use while using Android AOSP 7.0 at idle.

This is handy as it provides a base for battery usage when the phone is not used/idle.

Environmental changes in location and screen use can drastically change the usage.

GSM signal was 100% during the monitor period.

If you use the screen a lot and/or game and etc, the battery usage will increase and shorten the time until recharge.

This is also handy for future development as battery usage could increase/decrease with changes made in the future.

There is nothing worse for developers than people saying the battery usage is greater, with no supporting arguments.

Fig 1-2 battery usage over 6 days

Fig 2-2 Battery life average of 5days when generally left to idle and max screen on 53mins seen over two months
[Galaxy S 4 i9505 Original Android Development] Black Manta:
On android.googlesource.com the android 7.1 source code are published. At this time its's 7.1.0 release 7 build NDE63X.
[Galaxy S 4 i9505 Original Android Development] Hamid Chikh:
Can't Flash Stock GAPPS - Get google play services has stopped error -

Hi i get bad google play services behavior when flashin stock Gapps , this rom only work with pico or nano Gapps for me , any help ?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Just get the rest of the apps from the play store.
[Galaxy S 4 i9505 Original Android Development] mbaier:
Everything was OK but after few minutes touch screen stop.. And that's happening with almost all JDCTeam rooms... Any help..?
[Galaxy S 4 i9505 Original Android Development] Black Manta:
Do you really have an I9505 or a variant of it? Because I know the I9515 has a diffrent screen so that could cause this problem I think.
[Galaxy S 4 i9505 Original Android Development] mbaier:
yes I have 9505 , newest modem bootloader...etc
[Galaxy S 4 i9505 Original Android Development] Moritzio:
No need to quote the entire OP.
[Galaxy S 4 i9505 Original Android Development] Karls0:
If it happens with different roms, it's likely that the issue is on your side. What exact variant of S4 do you have? Are you 100% sure it is not refubrished phone from asian market? They may have some hardware differences, which explains this issue.
[Galaxy S 4 i9505 Original Android Development] Dr Goodvibes:
Samsung Galaxy i9505

I have a Chinese refurbished Galaxy S4 i9505 LTE phone and as sketchy as it sounds, it's absolutely OK on AOSP 7.0.

Initially when purchased, I had to strip mine down to reseat a daughter card on the MB to get the MicroSD card working and the NFC function of the battery was faulty, which required a battery replacement, but other than that, it is totally fine. :D

I've been running JDCTeam AOSP 7.0 for several months and now JDCTeam CM14.1

I have the latest modem code and quietly impressed Android 7.0+ is working so well on this phone.

If the ability to use the touch screen is failing, it is more likely because of other poorly written third party apps one has installed after the ROM or the screen digitizer is in the process of failing.

Touch sensitivity setting as default work fine unless one has started changing them. :eek:
[Galaxy S 4 i9505 Original Android Development] Pottertons:
For crying out loud.

I always thought that the SGH-i337m was just the Canadian alias for i9505. Seems i was wrong, which probably explains why things are a bit finicky upon installation of this ROM. lmao.

Sorry for the trouble people.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Try using the stock kernel. I heard alucard kernel may have some issues with a few screen models.
[Galaxy S 4 i9505 Original Android Development] mbaier:
can you give me a link from stock kernel please ?? Can't find stock for 7.0
[Galaxy S 4 i9505 Original Android Development] Rhoban:
It's on the download page.
[Galaxy S 4 i9505 Original Android Development] mbaier:
still can't find :confused:
[Galaxy S 4 i9505 Original Android Development] Kippy51:
https://romhut.com/addons/stock_kernel-dda27606-d0b5-479c-9fef-eddc5e55a96f

Sent from one of my Sammy devices.
[Galaxy S 4 i9505 Original Android Development] mbaier:
install stock kernel.. touch screen work ...but don't have root ..solution ?
[Galaxy S 4 i9505 Original Android Development] FernBch:
Check in developer options and see if there's a root access setting in there that needs to be adjusted or try reinstalling Su from Google Play
[Galaxy S 4 i9505 Original Android Development] FernBch:
I need one Sprint user who would like to test a new build to PM me for more info. First Come First Served!!!

Once the first person replies the offer ends and I will it announce here.
[Galaxy S 4 i9505 Original Android Development] FernBch:
No one is interested??

---------- Post added at 09:16 PM ---------- Previous post was at 08:55 PM ----------

I need to know if other CDMA users can have this!!!!!!
[Galaxy S 4 i9505 Original Android Development] FernBch:
Are there no takers? Sprint, AT&T, etc??
[Galaxy S 4 i9505 Original Android Development] Rhoban:
You have to re-root now. Just download the latest SuperSU zip (2.78 something) and flash it through recovery.
[Galaxy S 4 i9505 Original Android Development] pionee3:
my device is unable to wipe data, anyknows how to deal with it?

my device is unable to wipe data, anyknows how to deal with it?

my device is ks01ltektt and other things i can wipe them but only the data...

i'm stuck right here,plz anyone help?
[Galaxy S 4 i9505 Original Android Development] luiwii:
I have a jfltexx, it is not worth it, come nobody is encouraged, everyone is waiting for update and nobody is offered, thanks for the work jdcteam
[Galaxy S 4 i9505 Original Android Development] macwindows:
I have jfltecan (i337m) is that ok? than I can.
[Galaxy S 4 i9505 Original Android Development] hammer7t:
I am on AT&T and can help if you are still looking for testers.

Thanks.
[Galaxy S 4 i9505 Original Android Development] mbaier:
how to set power menu ???
[Galaxy S 4 i9505 Original Android Development] Kippy51:
Nog in AOSP; I used 'Simple reboot' app (Francisco Franco).

Sent from one of my Sammy devices.
[Galaxy S 4 i9505 Original Android Development] FernBch:
Thanks for understanding

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

My apologies, I forgot who is CDMA and who is not

---------- Post added at 01:51 PM ---------- Previous post was at 01:51 PM ----------
[Galaxy S 4 i9505 Original Android Development] -+BB+-:
Hi guys, finally it's time for our first Beta release! :) Here' s the changelog:

20161117 - Beta 1

MD5 - 99b143807a9f5077d61d5bc57e88e174

Kernel

Compile with GCC 6.0.1 + fixed compiling warns

General code updates

VoIP: more fixes + updates

Fixed sdcardfs

ROM

WIP: initial Xiaomi Gemini bringup

Ported + fixed all CAF code on our repos

Deskclock: temporary revert CAF additions until bootloop issues are fixed

Bluetooth: fix JFLTE bluetooth after CAF code merge

WIP: bring back browser from MM

Gallery2: switch to SnapdragonGallery + cm fixes/enhancements

jflte: Add support for Samsung extended AGPS

STweaks: fixed profile check

Fix SuperSU installation for block-based OTAs

SuperSU: update to v2.78SR1

Substratum: update to v470 (is needed a full uninstall/removing of installed themes and overlays!)

jflte: GPS: removed not used files/services

msm8960: audio: fixes for voip and calls

msm8960: display: fixes and improved portability

jflte: remove some QC encoders from codecs list

Update sources to Android 7.1.0 release 7

Dialer: add back call recording feature

WebWiev: update to latest stable and beta versions released by Google

jflte: remove unused graphics libraries

jflte: more fixes for VoIP mixers

Jflte: init: fixed boot and network for all variants

OMS: Reverted all old patches and merge updated code from TeamSubstratum gerrit

jflte: updated sepolicies

APNs updates

jflte: libwvm.so: fix library crash due to missing symbol

Bootanimation: updated for 7.1. Big big thanks to [MENTION=2026779]gadget![/MENTION] (xda)

Create 0 compression ratio jar files

telephony: Hack GSM and LTE signal strength

jflte: QMUXD: fixed acquire/release wakelocks

core: arm: remove deprecated -msoft-float in favour of -mfloat-abi=softfp

Xposed: jni: consider /data/app to the fd whitelist if Xposed is detected

IMPORTANT: A DATA WIPE IS REQUIRED, a dirty update from Alpha version could cause crash/issues on a lot of things

Here' s the download link: Download AOSP-JF-7.0 - JDCTeam_jdc_jflte-7.1-20161117-BETA.zip

Enjoy :)
[Galaxy S 4 i9505 Original Android Development] FernBch:
The reasoning behind me asking for one Sprint user do do a test was simple. The Sprint setup is closest to mine and if the same results are achieved all questions are answered at the same time.

It is an almost thankless undertaking sometimes. More than one developer and myself have spent MANY MANY hours working on a couple issues trying to get a new update out. Between that, life, family needs, and our jobs that pay our bills things have been busy of late.

I personally enjoy what I do to help [MENTION=5576897]-+BB+-[/MENTION], [MENTION=5968293]side[/MENTION], [MENTION=5795145]javelinanddart[/MENTION], [MENTION=3545504]smeroni68[/MENTION], and the entire JDC Team bring you what so many of you enjoy using. For Free.

Once particular set of issues was a bit tough to sort out and resolve. I myself have probably flashed more builds in the last 3 weeks than 99.999999999% of users flash in a year. Sometimes it equaled 10+ a day. One developer in particular said, and I quote, "Your poor eMMC". Out of what seems like 250-300 flash attempts 99% of them either froze at the Samsung Boot Logo, Bootlooped, or had no service whatsoever (most froze or bootlooped).

I have said it once before. I have a newfound appreciation for what the developers do. If it was not for them the beloved SGS4 that everyone wants the newest software for would either be on KK, a buggy LP, Crapwiz, or maybe even collecting dust in a drawer somewhere.

When you download and flash AOSP 6 or 7 or the OptCM13, 14, or 14.1 remember what they do for us. With out THEM our S4's would be left behind......

Also remember to tell them " Thank You"!
[Galaxy S 4 i9505 Original Android Development] elv1503:
Thanks for new release. I appreciate the work you and your collaborators do. Downloading and looking forward to installing.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
... I've quite in my mind your frustration on Sammy logo frozen... how many days... how many times happened... but finally thanks to devs all, we get the point and fixed... thanks [MENTION=5576897]-+BB+-[/MENTION], [MENTION=5968293]side[/MENTION], [MENTION=5795145]javelinanddart[/MENTION] for your time and dedication on this device and JDCTeam...

Now for users... we tested I9505 (Intl) and I545 (vzw)... so we hope that this development will work also for other variants... please, take in mind that can be that something is still not OK... let us know in case of errors, and give use the time to evaluate logs... then Enjoy our free time work!! :D
[Galaxy S 4 i9505 Original Android Development] FernBch:
Yea, it got frustrating at one point. Download build, flash, no boot, replace boot.img, repack, flash, no boot, edit line X in file Z, repack, flash, no boot.............. It seems almost hopeless at one point. Lol

I thought about tossing the S4 off a cliff once or twice (no tall buildings here, lol).

But persistence paid off. Or is it obsession???

One things is for sure though. I can hack a zip to try something in moments now. [emoji1] [emoji1] [emoji1] [emoji1]

Thank You Developers!!!!!!
[Galaxy S 4 i9505 Original Android Development] BeastMode6:
Is the new release for CDMA too? Us cellular user here.
[Galaxy S 4 i9505 Original Android Development] FernBch:
Try it and see. I'm CDMA and locked BL. The only issue I have is with STweaks. Since my bootloader is locked to have root I need to flash an older system based SU (2.52) and STweaks needs systemless root. Haven't figured out the workaround. Yet. But I have a couple ideas....
[Galaxy S 4 i9505 Original Android Development] BeastMode6:
Cool, ill take a stab at it in a bit. That really sucks about your bootloader man. So happy USC didn't lock down their GS4.
[Galaxy S 4 i9505 Original Android Development] Ricardo_Is:
[MENTION=5576897]-+BB+-[/MENTION] Thanks for Beta release!

Camera record still broken or fixed?
[Galaxy S 4 i9505 Original Android Development] Andrea :D:
Thanks! I'll try it tomorrow, is the camera fixed?
[Galaxy S 4 i9505 Original Android Development] riskyfuture:
Cheers -+BB+- keep up the good work
[Galaxy S 4 i9505 Original Android Development] Epic.:
Is Video Recording still not working guys?

EDIT: Recording doesn't work yet guys but the rest of the rom feels great so far
[Galaxy S 4 i9505 Original Android Development] Ricardo_Is:
Nice work [MENTION=5576897]-+BB+-[/MENTION]

Installed and feel my device flying like a rocket!
[Galaxy S 4 i9505 Original Android Development] lyjacky11:
I can't access developer options menu! Please help
[Galaxy S 4 i9505 Original Android Development] FernBch:
Setting>about phone and tap build number 7-8 times
[Galaxy S 4 i9505 Original Android Development] lyjacky11:
Thanks for your reply!

But when I try to click on the menu after I enable it, i get a black screen and Settings crashes.

Thanks
[Galaxy S 4 i9505 Original Android Development] fatboysh:
Everything i have tried works so far except swyping...jflteusc
[Galaxy S 4 i9505 Original Android Development] FernBch:
Clean flash or dirty. I don't have any issues with settings FC-ing
[Galaxy S 4 i9505 Original Android Development] cmert:
i am trying but camcorder not working
[Galaxy S 4 i9505 Original Android Development] Kippy51:
Maybe OP has to be changed??

In 'General Notes' it says "Theming: to apply OMS overlays to some apps, you need also to flash TBO GoogleApps-ThemeReady-LP-MM-N-v24.6.zip right after your Gapps package from recovery. This means to be clear: ROM + GAPPS + TBO". But there is a newer version: v26.0. And in what to download it says gapps 7.0. Shouldn't that be 7.1?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Done. Thanks for headup!:D
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Those are more like guide lines, not actual strict instructions.
[Galaxy S 4 i9505 Original Android Development] a.dev:
I just upgraded from the previous 7.0 version (where I used the stock kernel) but the 7.1 feels a little more jittery (ui lag). Is it the kernel, the frameworks or just me?

Btw, the installer fails to migrate (FC's google play), installing a new device works seamlessly.

Apart from these, nice work :)
[Galaxy S 4 i9505 Original Android Development] abuhisham:
[JDCTeam][7.1.0][18 November][OMS-Substratum] The Android Open Source Project NDE63X

how to enable the navbar in that version. i tried qemu.hw.mainkeys=0 like by the 6.0.1 rom but it doesnt work. is there any other way to enable the sofkeys?

Otherside thanks for the great work on that aosp build and the other roms from jdc team
[Galaxy S 4 i9505 Original Android Development] luiwii:
Videorecording is fix?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
But if the main instructions say to DO A CLEAN INSTALL... why you are posting that you have problems after an upgrade from previous version 7.0?
[Galaxy S 4 i9505 Original Android Development] bgibs1:
Im on Sprint and Im downloading it now. I will try and flash it this afternoon, I've got a golf tourny this morning and need my range finder for that. Is there anything in particular you need feedback from or just feedback in general?
[Galaxy S 4 i9505 Original Android Development] a.dev:
I did do a clean install: wiped everything except internal storage where the rom+gapps zips resided
[Galaxy S 4 i9505 Original Android Development] Andrea :D:
Flashed and it's very very good, nice job!
[Galaxy S 4 i9505 Original Android Development] dreccon:
I just did a clean install and I had no root access. Even tried to install the latest SuperSU zip which seemed to install fine but when I rebooted SuperSU was nowhere to be found. I also didn't find any relevant options in developer settings.

Weird or what?

GT-I9505 JDCT AOSP 7.0
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Have you installed the correct gapps package? If you have problem with playstore, it is included into gapps zip.

---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------

SuperSU icon is hidden on our rom. You can find it under AOSP SETTINGS menu -> JDCTeam Custom Settings... if supersu flash fine, rom is rooted as systemless.
[Galaxy S 4 i9505 Original Android Development] tecnomovida:
Clean Flashed !! all is ok... Great work!! Thanks!!
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Let us know if it flash correctly and if it works. That's all. Thanks.
[Galaxy S 4 i9505 Original Android Development] dreccon:
Yes, i noticed. It FC'd when I tried to select it from there. Then I installed SuperSU from Play and it said there was no SU binary.

GT-I9505 JDCT AOSP 7.0
[Galaxy S 4 i9505 Original Android Development] -+BB+-:
As wrote in the OP, camera is not fixed yet, camu is a temporary workaround for videos recording, tested and works fine :)

Boot is fixed for all supported variants, if your RIL is 100% working then we can consider our unified device tree fixed :)

That's strange, you should have SuperSU preference screen under Settings --> JDCSettings

Weird, i can enter in developer option without any issue.. What's the output of the log when settings crashes?

Have you tried this version and see if works? https://github.com/B--B/Alucard-Ker.../READY-JB/system/priv-app/STweaks/STweaks.apk

About SuperSU, the problem is related to SuperSU and not our ROM/installation scripts... Basically systemless SuperSU during flashing process extract the ramdisk from the boot image, then patches sepolicy and file context, add the services all needed stuffs and then repack the boot image and flash it to the device. On locked bootloader devices the process fails... I thought it was related to the fact that loki pacthes the boot image before supersu flash:

https://github.com/AOSP-JF-MM/platf...ls/releasetools/ota_from_target_files.py#L779 --> Here loki is executed

https://github.com/AOSP-JF-MM/platf...ls/releasetools/ota_from_target_files.py#L788 --> Here starts SuperSU flash

But i was wrong, i tried to run loki after SuperSU flash, boots fine for me, but when you flashed the test ROM the script failed because SuperSU failed even with the unpatched boot image... This means that SuperSU scripts has some kind of issue with locked bl variants... I will see if i can fix it on ROM side, meanwhile that version should work fine...! :)

That's because SuperSU was not installed, tiles should disappear if the app is not installed but i had no time yet to add the check: https://github.com/AOSP-JF-MM/platf...mmit/8da87a24c461b23584f73e2ed511c1220b678943
[Galaxy S 4 i9505 Original Android Development] FernBch:
Thanks for the info. I'll check it out. I did some reading on the different SU methods (system vs systemless). Apparently systemless does present an issue when it comes to locked BL devices. That said I think the issue is more a device specific problem on my end.

---------- Post added at 09:54 AM ---------- Previous post was at 09:34 AM ----------

Thanks Again for the info. The linked STweaks.apk works fine. I was going to pull one from an earlier build. I copied to /system/priv-app ad set perms to rw-/r--/r-- and rebooted. I can tweak some kernel settings now so I'll see what battery life improvements I can make happen.

---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------

I have an idea to try but I'll explain later.....

Worst thing I can do is make a soft brick, lol. Did that about 10 times trying different things kernel related in the last three weeks.

---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------

Ok, I545 users, there you have it.

I still have to flash an older SU "system type" root package from TWRP in order to have root. You can update SuperSU from Play just fine. The STweaks that [MENTION=5576897]-+BB+-[/MENTION] linked works fine for me now.

The issue is with SuperSU not the ROM. This may be an issue on the other locked BL devices as well but there is a workaround.
[Galaxy S 4 i9505 Original Android Development] dreccon:
I guess I just had a bad flash (although there was no error). I tried all over again and everything works fine now. Sorry for bothering you guys without a second attempt.

GT-I9505 - OptiCM13 - OF2 BL/modem
[Galaxy S 4 i9505 Original Android Development] smeroni68:
No problem mate... we test our builds before releasing them... ;)
[Galaxy S 4 i9505 Original Android Development] FernBch:
Not a problem. It's normal. At first I didn't suspect bad flashes when I saw no errors, too.
[Galaxy S 4 i9505 Original Android Development] abuhisham:
Anybody knows how to enable navbar please?
[Galaxy S 4 i9505 Original Android Development] elv1503:
"Substratum has detected it may be running on a dangerous.....may cause bootloops...". Is everyone getting this message?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Yes... it's due to the check on 7.1 core... no problem.

Xiaomi Mi5 Pro on AOSP 6.0.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] elv1503:
Thanks, but just to clarify,. Can I ignore the message?
[Galaxy S 4 i9505 Original Android Development] a.dev:
open_gapps-arm-7.1-pico-20161118.zip

GoogleApps-ThemeReady-LP-MM-N-v26.0.zip
[Galaxy S 4 i9505 Original Android Development] FernBch:
Yes. I did

---------- Post added at 11:39 AM ---------- Previous post was at 11:39 AM ----------

And the undervolting begins.....

Down one step each
[Galaxy S 4 i9505 Original Android Development] hammer7t:
Right...on AT&T, the built-in SuperSu failed to install. I was able to install v2.52 fine though.
[Galaxy S 4 i9505 Original Android Development] fatboysh:
I ignored it. Works fine
[Galaxy S 4 i9505 Original Android Development] elv1503:
Thanks
[Galaxy S 4 i9505 Original Android Development] FernBch:
Not too bad....

6 hrs on battery, heavy usage, 3.5 hours SOT, 34% remaining
[Galaxy S 4 i9505 Original Android Development] Strephon Alkhalikoi:
*chuckles*...I haven't restored my kernel settings yet. Thanks for reminding me.

Substratum is working perfectly. In fact, I went for a red theme this time around instead of the blue I use on my Nexus 6.

This may be an issue with Nova Launcher Beta, so take this with a grain of salt. If anyone can confirm it, great. Otherwise feel free to ignore. The only wonky thing I noticed regarding the ROM is with the wallpaper. When the lock screen wallpaper is different from the home screen wallpaper, the home screen wallpaper will shift to the left on every reboot. Swipe in either direction on the home screen and it immediately corrects itself. If you have OCD and don't like seeing this, setting the wallpaper to display on both lock screen and home screen resolves the issue.

Other than that, the only other caution is my standard one regarding the camera: install a camera app with its own binaries to avoid potential problems with the camera.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I was hoping that the "no problem" I wrote was the answer for your question!:D

EDIT: the message is an advise for legacy devices (stock roms that run legacy mode for overlays)

On custom rom it is not a problem, because the source code from substratum/OMS integration is managed build by build from devs.

Check here the last days commits:

https://github.com/AOSP-JF-MM/platform_frameworks_base/commits/aosp-7.1