yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] luistro:
work hdr in google camera in this build. for my only work in gpe 5.1
[Galaxy S 4 i9505 Original Android Development] ilfrick:
Confirmed on my end as well, I9505. Plus, WiFi gets disconnected when trying to turn on Bluetooth.
[MENTION=3545504]smeroni68[/MENTION] here's a logcat.
[Galaxy S 4 i9505 Original Android Development] luiwii:
HDR does not work Error brand camera but the camera does not close and can be used perfectly well that HDR does not work cámera google , camera stock work fine hdr
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Never had in our testing... What gapps you used?

Use the gapps package on Addon section (Open Micro of 20150914).

Follow this:

1) wipe cache, dalvik and system

2) flash rom and gapps in the same session

3) wipe cache and dalvik

4) reboot
[Galaxy S 4 i9505 Original Android Development] luiwii:
bluetoh working ,clean installation of all,connected 30 min.ok nissan juke works well without stoppages, connected and disconnected without problems
[Galaxy S 4 i9505 Original Android Development] luistro:
use hdr canot conect camera please fix
[Galaxy S 4 i9505 Original Android Development] Fat_boy555:
I used TK GApps. After clean install once again its seems to be working fine. I can't seem to figure why it happened on the first flash.
[Galaxy S 4 i9505 Original Android Development] luiwii:
Stock camera hdr work fine , google camera can't conect fix google camera

---------- Post added at 11:32 AM ---------- Previous post was at 10:49 AM ----------

compass seems to not work, I can not you go

Edit:

GPS test does not work but test works well with maps
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
I also had permanent problems with switching Bluetooth on. But i solved it - it is the same thing i wrote some weeks ago: when i use the latest opengapps, Bluetooth does NOT turn on.

When i use the latest TK gapps, Bluetooth works!

I checked it several times and for me it is reproducible.

What the **** has the gapps package to do with Bluetooth.

I did a 100% clean install btw

More things to this ROM: good work! :)

I only had to exchange the keyboard files again because Swype (gesture typing) is still not working and i need this.

In zip for this ROM, the default calendar app and the BasicDreams.apk were missing. I don't use the default calendar but maybe someone misses it.

Thank you for your work!

But i had some device freezes now. Nothing works anymore, only press the power button a long time.
[Galaxy S 4 i9505 Original Android Development] Fat_boy555:
I observed the freezes and nothing works except the power button.
[Galaxy S 4 i9505 Original Android Development] oran3e1:
What do you mean freezes? is this ROM stable yet? are you using the latest version?
[Galaxy S 4 i9505 Original Android Development] Fat_boy555:
Yes Im using the latest. Read above I reported abt the bluetooth bug earlier which I solved on the 2nd clean flash. the freeze just happened as Im typing this reply. I have no idea when it is going to happen and there isnt any response. Currently pulling the battery seems like the best solution.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Did you apply any UV to CPU or GPU?
[Galaxy S 4 i9505 Original Android Development] Fat_boy555:
I have UV to CPU. I'm going to revert them and observed. Will let you guys know if it still happens after reverting.
[Galaxy S 4 i9505 Original Android Development] droidblitz:
I also encountered this. Bluetooth and wifi issue..

wiped data cache system and converted F2fs data and cache

flashed the latest build + Open Gapps Pico...

Downloading the Open Gapps Micro 20150914 from OTA app

Will do another clean install :D
[Galaxy S 4 i9505 Original Android Development] a103:
Mate HDR doesn't work on any AOSP ROM so please don't use it. Also don't clutter the thread with similar issues. Use a better camera app from play store which has a working HDR.
[Galaxy S 4 i9505 Original Android Development] vinodr5371@xdaroms.co.in:
i just installed xposed in this rom i am getting boot loop mobile not getting on.how can i insatll xposed in this rom?
[Galaxy S 4 i9505 Original Android Development] droidblitz:
http://xdaforums.com/showpost.php?p=62889397&postcount=907

3) Xposed cause bootloop and is not working in this version, we will try to fix it in the next stable release, for the moment do not try to flash it
[Galaxy S 4 i9505 Original Android Development] ilfrick:
R: [JDCTeam][STABLE v1][5.1.1][RRO][17 September] The Android Open Source Project

[MENTION=3545504]smeroni68[/MENTION] I had done it the way you indicated, minus your point 3, when I first flashed the rom. I had used open gapps pico from sept. 18th.

Anyway, I did again, this time with pico gapps from sept. 14th, and I wiped cache and dalvik again (your point #3), before rebooting. Guess what? Bluetooth now works fine!

Can you tell us why???

Thanks a lot for your awesome work JDC team!
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
When you don't wipe /cache and the dalvik-cache, you get problems like that.
[Galaxy S 4 i9505 Original Android Development] r2089:
Freezes

finally ! I have the same ... But only with alucard_24 kernel ... I used cm 12 with alucard kernel freezes workd only power button and softkeys .... Stock CM kernel or googy kernel works fine ... CM 12.1 with alucard kernel same ... This rom same ... sometimes it works sometimes freezes ... Stweaks default settings . I have I9505 ... sorry for my bad english
[Galaxy S 4 i9505 Original Android Development] ilfrick:
Well, I had wiped system system, cache and dalvik BEFORE flashing rom and gapps, but I hadn't flashed cache / dalvik again after (why one would do that?).

Also, dalvik doesn't exist anymore in lollipop (cache does, of course).
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
If you have problems even after wiping /system and both caches, you'll need a clean flash then. Clean flash is the only way to ensure you don't get any problems upon boot.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
But the name of the directory with the precompiled ART stuff is still "dalvik-cache", that's why it should be wiped.
[Galaxy S 4 i9505 Original Android Development] chens23:
Has anyone gotten android pay to work on this ROM?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Is it working? That's not enough?

Just kidding. Well, normally a rom flash will clean all needed stuff during the flash script execution... but can be that during these operations something is left on some partitions.

Normally these wipes are not necessary... but the procedure I reported I called "clean dirty flash".

As most of you, I have a working phone and a real clean flash will create a time loosing to reinstall all (also called "laziness")...

So I always use this procedure to move away this time loosing.

As tester I flash at least once a day... and I need to be sure the result is 100% successful... and for me it is.

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)

---------- Post added at 09:00 PM ---------- Previous post was at 08:47 PM ----------

On some phones for unknown reasons seems that the kernel can produce strange behaviour... for this reason we are preparing the updated stock kernel.

Alucard phone is one of the most stable... belive me, I'm not kidding... and this brings dev to not be able to evaluate strange behaviour.

In the testing team we have several hardware, and also for us is difficult, because when we all do not have problems... for us is fine.

Btw: wait the stock, flash it and let us know if all is fine.

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] r2089:
---------- Post added at 09:00 PM ---------- Previous post was at 08:47 PM ----------

[/COLOR]

On some phones for unknown reasons seems that the kernel can produce strange behaviour... for this reason we are preparing the updated stock kernel.

Alucard phone is one of the most stable... belive me, I'm not kidding... and this brings dev to not be able to evaluate strange behaviour.

In the testing team we have several hardware, and also for us is difficult, because when we all do not have problems... for us is fine.

Btw: wait the stock, flash it and let us know if all is fine.

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)[/QUOTE]

But i need stweaks ... so i must use TW rom :(
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Without a phone like your, it's quite difficult to find the reason of the issue... if you think the solution is to go vs TW... you are free...
[Galaxy S 4 i9505 Original Android Development] Dior DNA:
Does this AOSP come pre-rooted ?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Yes... SuperSU inside...
[Galaxy S 4 i9505 Original Android Development] Dior DNA:
Coming from OptimizedCM-12.1-20150817-jflte, should I dare flashing AOSP-5.1.1-20150917-jflte dirty?

I mean, keeping /data but wiping dalvik-cache and /cache? Is this guarantied to give trouble or has anyone successfully done so? If it does not work, I can always try 2nd time with factory reset (and Titanium Backup restore), but I would of course prefer, not having to start from scratch (~300 apps).:cowboy:
[Galaxy S 4 i9505 Original Android Development] r2089:
it's not like that . I searched the whole forum and a total anything about it because I found not gave up. I will help solve this problem
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Absolutely Clean... cm is a different rom.

Inviato dal mio GT-I9505 su AOSP 5.1.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] Dior DNA:
Fair enough... Thanks for letting me know! I'll go clean. And huge congratulations JDCTeam for this ROM.
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
Bluetooth is broke on my end too. Posting logcat in a bit.
[Galaxy S 4 i9505 Original Android Development] :
Did u try clearing dalvik and cache, installing ROM and then erm, clearing dalvik and cache again? Apparently this helps but no one has given a reason why ;)

---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------

Also noticed Samsung Doze running in background. Has this been imported from M :)
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Will Android Pay work here? The answer is no. According to Google infos it works only on factory-preinstalled and unrooted Android, do not blame us for this!

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] Fat_boy555:
Im experiencing Camera Crashes when using the front cam. This is what how it happens. I use the front cam in the telegram app then after that if I were to open the google camera app to take a pic using the front cam then the cam interface will freeze and if I reopen the app i get the camera cannot connect message. Happens when I use WA or the front cam first then the telegram app. As long as the front cam was previously utilised and I open another app to attempt to use the front cam the above will happen.

Btw the freezing I previously reported hasnt happened since I posted but I was asleep for abt 8hrs or so. I will report if it happens with more extensive usage
[Galaxy S 4 i9505 Original Android Development] dilidani:
Hey guys! Having random reboots here. Using darkness governor, underclock to 1.67Ghz and -0.25 unit undervolt on cpu.
[Galaxy S 4 i9505 Original Android Development] Solace50:
For anyone with broken BT did you get Bluetooth Share service has stopped responding? For me the service died out and I believe its an inherent issue in the ASOP release by google.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
UV can give a lot of problems... please remove any UV and check on your stock voltages.
[Galaxy S 4 i9505 Original Android Development] luistro:
xposed v74 bootloop
[Galaxy S 4 i9505 Original Android Development] AmyClaraRose:
Did you select the right version
[Galaxy S 4 i9505 Original Android Development] smeroni68:
... That's quite strange!!!!...

There must be a reason why on release post, dev wrote on point 3 something...

http://xdaforums.com/showthread.php?p=62900416

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] jeffrey1296:
Wow

I logged in and everything to say, but it's really good to know people still support their good old gs4, keeps me from getting the gs6 or n5, the people that put there time and effort for this phone it's heart warming, thank you guys and keep up the goodwork.
[Galaxy S 4 i9505 Original Android Development] Fat_boy555:
Anyway I can help for this?
[Galaxy S 4 i9505 Original Android Development] Dior DNA:
BT issue?

This AOSP is obviously the coolest firmwares for S4 and I suggest to

call it 'Kelvin 1' (which is real cold!). Just to say: -THANKS- for the

software. But, after clean install I do seem to face issue where (as

others report) bluetooth cannot be enabled. I took a logcat which may

or may not help.

http://pastebin.com/46dNU6GX
[Galaxy S 4 i9505 Original Android Development] rushco:
Which one is better? This or [JDCTeam][5.1.1][17 August] Optimized CyanogenMod 12.1

This one has a newer build but the other one seems more popular.
[Galaxy S 4 i9505 Original Android Development] Dior DNA:
good question :)
[Galaxy S 4 i9505 Original Android Development] Kippy51:
Try both and decide for yourself ..... It depends on your preferences, what you like. AOSP is 'cleaner', less features. For me its is too clean ... (I sometimes install another rom, just to see what it does - momentarily on Angelcalibur's Saberrom). But waiting patiently for the next build of AntaresOne's Optimized-ROM. :good:
[Galaxy S 4 i9505 Original Android Development] :
Would say optimized as more features but AOSP is developed a little quicker.

Size wise it's about 40MB less but once you've added swype keyboard, music player etc there's not much difference.
[Galaxy S 4 i9505 Original Android Development] smstiv:
Ok now, the big difference is in the code. Optimized is based mainly in CM,

but increasingly the version code of AOSP is rewritten with the urge to stop using CM.

The optimized version comes with most of the features of CM (although some is removed precisely because of the optimization),

hence the difference of about 40mb AOSP.

AOSP is based pure Google with some CM code to adapt Android 5.1.1 in our S4 ....

"More or less AOSP is the Nexus devices stock rom without gapps." - OP
[Galaxy S 4 i9505 Original Android Development] interaser:
Hello,

thank you for this awesome latest build; everything seems to work okay.

on previous build after flashing the rom and gapps, after booting up and opening 1 time the Google+ app my rom profile picture and information updated by itself based on my Google+ profile.

After flashing latest build with full wipe the rom user profile does not update by itself (I flashed 2 times the rom with full wipe just to be sure)

Thank you.

p.s. by the way after lashing the rom I always flash stock opengapps...
[Galaxy S 4 i9505 Original Android Development] kapitanbasa:
yey! i got past the boot animation, but noticed, when I was prepping the phone, that my 3g signal dropped to E or nil from where I'm at, where I previously would receive an H or H+. Maybe I need to update my modem too?
[Galaxy S 4 i9505 Original Android Development] pwichhart:
I update my modem and bootloader just for the fun of it. Flash-aholic :sly:.

Works fine on my i9505 with latest bootloader and modem XXHUOE4.
[Galaxy S 4 i9505 Original Android Development] mulletcutter:
Flashing stock cm kernel didn't fix Bluetooth
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
Has there been a new build pushed out? I can't seem to install this ROM with MultiROM because it says that it won't install over a newer build when, to my knowledge, there is none.
[Galaxy S 4 i9505 Original Android Development] AmyClaraRose:
does this rom support rro layers
[Galaxy S 4 i9505 Original Android Development] morpheus302:
No

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] eddloschi:
[MENTION=5576897]-+BB+-[/MENTION] [MENTION=5464206]AntaresOne[/MENTION] This fails to install as a secondary ROM on MultiROM v32a because of the date check of the first line from the updater-script. I removed the line then zipped again, it flashes correctly and works perfectly as secondary ROM. Recovery log attached
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
Hey, mind sharing specifically which line I need to remove so I can run this with MultiROM?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
New build out!!! :D

20150619 - Beta #1

MD5 - 51b35865265ad3bfbc478c0d214070f8

ArchiDroid optimizations v4

Added MultiROM compatibility

RRO added and partially working: Contacts, Dialer and Settings need some changes. Everything else is correctly themed

Fixed BT/WiFi coexistence, now can be turned ON at the same time

Fixed back/menu keys lights (timeout set at 5 seconds, user settings soon available in Settings app. For now, enable/disable by writing "softkeys" without quotes in Terminal Emulator (available on Play Store))

Fixed F2FS for /cache partition

Fixed "First boot doesn't have sound across all the system if the external SD card is not in FAT32"

Fixed MicroSD card, all filesystems are mounted well and working in r/w

Init: use our specific init

Temporarily fixed "No SIM" on Keyguard (removed Carrier text)

Various kernel code updates

Various updates on audio/camera code

Various updates on BT/WiFi code

Download: https://romhut.com/versions/aosp-5-1-1-20150619-jflte-zip

I must say that @+-BB-+ is doing a great work, it's nice to work with him! :D
[Galaxy S 4 i9505 Original Android Development] -+BB+-:
Softkeys light has been fixed in latest build, regarding t9 search there aren' t sources related to t9 in aosp dialer repo... I read that it' s a nexus exclusive, let' s see what we can do...! ;)

Unfortunately, this is the only big bug.. Flash another kernel does not help, the problem is on bluedroid repo, aosp handle things in a different manner than cm, and a2dp does not work with our device, as you can see in our github i started to work on bluedroid, but no luck for the moment...! :( All the other bt functions works fine! ;)

---------- Post added at 02:35 AM ---------- Previous post was at 02:20 AM ----------

RRO is partially supported in latest build

Installation script needed some changes for work with multirom, please try latest version, should work without issue! :)

Thanks for your report, bug fixed :o
[Galaxy S 4 i9505 Original Android Development] mulletcutter:
So slow Bluetooth still exist?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Only for media audio (like music, sound of videos, system sounds....), calls work well
[Galaxy S 4 i9505 Original Android Development] -+BB+-:
As i said in my previous post yes, only when streaming music... I'm reviewing now the code in bluedroid to see differences between cm and aosp, but it will require some time... cm ported a lot of code from codeaurora, there are great differencies with aosp repo...!
[Galaxy S 4 i9505 Original Android Development] _DrizeX_:
Yaay. an update!

Let's try!
[Galaxy S 4 i9505 Original Android Development] -+BB+-:
EDIT: Anticipated by [MENTION=5464206]AntaresOne[/MENTION] :p
[Galaxy S 4 i9505 Original Android Development] mulletcutter:
OK, but like a lot of us, CM ROMs Bluetooth FCs a lot. Sometimes it takes a reboot to fix sometimes I wipe data on Bluetooth in TB. Stock is only rom that Bluetooth works great it, but I can only stand twiz so much. But take your time..
[Galaxy S 4 i9505 Original Android Development] misha0209:
thank you so much for the effort of making this ROM!!

wanted to flash it right away, but then i read the comments with BT audio, and since i use the phone with car BT allot... going to skip this one. patiently waiting for BT to be fixed :) since you're working on it maybe you can increase the buffer size, like you did for CM, so there are no dropouts for the more unique devices out there..

if i may, could you pls keep the audio code as clean/minimal as possible? the main reason i want to move away from CM/CM optimised, is because it just sounds worse than say the GPE rom with headphones. GPE is serious audiophile quality :D so i hope that AOSP will be just as good. hoping there will be no audio fx or anything similar. just good clean, no useless extra resampling/processing audio.

short question, did battery text, and such configurations make it into this rom yet?

again many thanks for the effort!!
[Galaxy S 4 i9505 Original Android Development] Mystikal57:
Hey antares, what's the difference with optimized CM12 ?

CM & you made different optimizations on CM12 which isn't in AOSP ? Then AOSP is less optimized than CM12 ?

I'm very interested in your work & like your optimized CM12 version very much.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Strange (or good), in this ROM the date format is ok for my country but in CM12.1 it is not.
[Galaxy S 4 i9505 Original Android Development] Dior DNA:
Anyone else has no bluetooth?

When I turn on bluetooth by moving knob left-to-right, it stays there a second and moves back right-to-left on its own. Meanwhile WiFi connection breaks (and comes back a few minutes later).

Here is another logcat http://pastebin.com/NmDux2Qx

note:

E/bt_osi_config( 6497): config_new unable to open file '/etc/bluetooth/ble_stack.conf': No such file or directory

this file is not there but was not there in CM either.

fwiw:

here are diffs between CM and AOSP bluetooth configurations

# diff gt-i9505-{cm,aosp}/system/etc/bluetooth/bt_did.conf

10,11c10

< # 0x001D = Qualcomm

< vendorId = 0x001D

---

> #vendorId = 0x000F

# diff gt-i9505-{cm,aosp}/system/etc/bluetooth/bt_stack.conf

39,40d38

< TRC_HID_HOST=2

< TRC_HID_DEV=2
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
If you read a few pages back, yes: some people have Bluetooth problems. For me i comes reproducible from the gapps package:

* If i install open gapps pico: Bluetooth does NOT work!

* If i install TK gapps pico: Bluetooth works!
[Galaxy S 4 i9505 Original Android Development] kaseykrehbiel:
I think everyone reading this should head over to Google Play and give it one star. They did a sneaky thing - Android Pay was not released on the Play Store as a new app. It was released as a Google Wallet update, so all of the 5-star ratings given to Google Wallet apply to Android Pay. It's down to 3.9 stars but we, as a community, need to speak much more harshly than that. Google needs to drop the requirement for the secure lock screen and change it back so that we modders with custom ROMS, root and Xposed installed can use it without trouble!

That being said, I did get Android Pay to let me put in my card on the GPE 5.0.1 ROM. It may work here, too. You have to:

1. Disable root in SuperSU (You do not have to completely uninstall it, just disable.)

2. If you are running Xposed (doesn't apply to this ROM yet I suppose), you have to flash the Xposed uninstaller. You do not have to remove any apps or modules, just flash the uninstaller.

Once I did that and set up my card, I re-enabled root and flashed Xposed again (it remembered all of my mods and settings and just worked on first boot thankfully.) I haven't tried to pay for anything yet but I'm hoping that will just work. If not, I'll be looking for other NFC pay options. Dangit Google. :-| ONE STAR !
[Galaxy S 4 i9505 Original Android Development] ccuchulain:
I couldn't get Android Pay to work after disabling SuperSU. I don't have Xposed.

This is a tricky situation for Google. If they turn their decision around, and let modders and such use NFC payments with custom ROMs, they would be criticized for having less security around their mobile payment. To the common user, NFC payment is already seen as weird and its security is questioned (although, all of us here know that it's secure, I'm talking about the general public).