yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] s3icc0:
1st observations after few hours

Hi devs/Antares,

So here my first observations after transition from CM11 to CM12:

1) First boot for me was very fast (like 2-3 minutes) - it was a surprise as on 4.4.4 comming from dalvik to art almost burn my phone down and took at least 15-20 minutes.

2) After 7 hours (sleeping) I have 22% Misc battery consumption - and I am on EXT4. (running stock + gapps)

3) ROM is pretty good considering the fact it is still in development phase - I am more or less missing 2 things - Autobrightness and Torch app. I had no chance to test calls and multimedia over BT yet.

4) I read there are some issues with alarms - for me the alarm was working just fine in the morning

I think I have a new daily driver!

Much appreciated!:good:

EDIT: Finally found one issue with root not working for me - now trying various methods to re-root - will see in an hour
[Galaxy S 4 i9505 Original Android Development] klukiyan:
battery drain

Hi

I have nk4 bootloader/modem, did a clean install. Phone doesn't go into deep sleep

some android process always keeps it awake

Surprisingly, when this rom was android 5.0, the battery was great and much better than on 4.4.4.

But now on 5.0.1 I started having constant phone awake status :(
[Galaxy S 4 i9505 Original Android Development] N!KE26:
Both autobrightness and torch are available. Autobrightness in settings torch in quick settings.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I installed fresh downloaded build 7 hours ago and I dont see quick settings and i dont see torch ... searched the phone several times :confused:

LOL - I found torch in quick settings - but it is not showing immediatelly but after some little time - and then it is not shining ... :(/

Anyway I also have a problem to gain root - I flashed superSU 2.40 after instal of rom and now I reflashed it, tried installing binaries several times but still no root access for me :(

seems I will have to reflash with system format - just to be sure
[Galaxy S 4 i9505 Original Android Development] moffe:
Well, latest build does not seem to be that stable. I get random "crashes" and random reboots, dialer crashes, bluetooth stops working at least against pebble watch. Seen also some error messages like bluetooth sharing stops working. On the the 9.dec build I did not have any issues (except the slow bluetooth streaming). Still this build is usable and AntaresOne has done really good jobb!

Not sure if this is CM or this ROM related, I wonder about the space used on my device:

If I count all usage space it's around 5GB, that would mean around 4GB should be free. But still there is only 800MB.

And also if you look at the color grey it shows almost half free. It's not 800MB of 9,13GB. :confused:
[Galaxy S 4 i9505 Original Android Development] N!KE26:
Pull two times from top down to get quick settings.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I know how to get there ;)

torch icon is there - but not immediatelly - it takes the icon a little more time to show up and anyway it is not doing anything :(

about autobrigtness - I have no autobrigtness settings - just the options: Adaptive brightness and Adaptive backlight, but I cannot set the autobrigtness behaviour (curve).
[Galaxy S 4 i9505 Original Android Development] TLK3:
Same. Are you formatted F2FS? Sorry if this has been discussed in just getting caught up on thread. First time I noticed issue was today.

---------- Post added at 03:02 AM ---------- Previous post was at 02:57 AM ----------

This had happened at least twice for different builds. F2FS is broken on external SD, then gets fixed.

For me, F2FS is great on external SD. I notice a big difference when dealing with thousands of audio and image files. Or very large videos.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
lost root

I know I mentioned this few post before, but here is more detailed overview:

After install of rom andreflash of SuperSU 2.40 I had a root after the very first boot - I did my usual settings in STweaks (just some frequencies etc ...) when I tried to launch STweaks again there already was the "No kernel support" notice. After that I am getting the notification to update SU binaries. I tried to do that by reflashing SuperSU, updating binaries through SuperSU app (both normal and recovery way), but still not able to get root back.

What am I doing wrong? Tried to search this thread for an answer but not successful. Any help appreciated!
[Galaxy S 4 i9505 Original Android Development] TLK3:
Just boot into recovery and use adb. F2FS on external SD is fine unless you actually need to put the card in a computer for some reason. Works well for me.

I just wish it wouldn't get broken every other build. :)
[Galaxy S 4 i9505 Original Android Development] s3icc0:
So I go into recovery - reflashed rom and gapps but when trying to reflash SuperSU I get the error about not being able to get to VoId ... and recovery rebooted itself - now I am in bootloop. Seems I will have to start over from Sammy stock.
[Galaxy S 4 i9505 Original Android Development] BoroChief:
The root confirmation dialog bug is back.. but this time with the preinstalled root, not SuperSu. The first two times everything worked perfect, but now I can't again press the allow button.. However, I already found a workaround (last part of the video) if anyone has the same bug.

MOD Edit: video removed due to being "private"

Edit: sorry, chose "not listed" but forgot to save. Here again :)

[YOUTUBE]NfKA1M-3NPM[/YOUTUBE]
[Galaxy S 4 i9505 Original Android Development] sanshinron:
15/12 build:

F2FS on sdcard is not working - card is seen in recovery but not in system.

I have 2 questions:

Since Galaxy S4 GPe builds are out, will stuff from those firmwares get incorporated into this rom/cm12, resulting in more functions or better performance?

Will we ever get RAW (DNG) picture support in CM12? I've heard it's not even available in GPe roms, even though our camera module is supposed to be able to output RAWs.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
bricked ...

I don't know what is the reason, but the phone is in bootloop, I cannot get to recovery and that all just due to reflashing the Chainfire's update SuperSU 2.40, at least the download mode is working

So in the morning I said this wil be my daily driver, but it definitelly will not be my daily after all!
[Galaxy S 4 i9505 Original Android Development] jamesmcuk:
So if you take battery off and replace then turn on with vol up pressed, releasing both when blue text appears at top left it ignores going to recovery and carries on booting until it boot loops?
[Galaxy S 4 i9505 Original Android Development] s3icc0:
The blue text is there for a very short time (what I remember it stay longer before) and the phone vibrates and start booting again normal way .... I tried holding buttons shorter time, longer time, removing battery everything ... now I am trying to boot normal it takes ages and then the logo stops rotating and I can wait 15 minutes and nothing happens - then phone reboots. I think this is Odin time :( but not sure I will be willing to go directly to this CM12 or I will get back to 4.4.4 :(
[Galaxy S 4 i9505 Original Android Development] jamesmcuk:
Bloody hell didnt know that could happen when the recovery hasn't been altered. Sounds like the recovery isn't even there. Just out of interest did you get any erros when flashing any of the files. At least then if I ever see them I know not to reboot until I get a successful flash.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I had the error with superuser .. something about not finding VoId (or similar - it was only for rly short time so I don't know the complete sentence), anyway ... I left the battery out for some time and I get to recovery - formated /system reflashed everything and now it is already upgrading apps ... so I will let you know about the root status after first few reboots

EDIT: OK back ON :) I can live again :), anyway superuser binary needs to be updated - I will rather wait for someone to help me figure out how as all classic methods failed before.
[Galaxy S 4 i9505 Original Android Development] TLK3:
Why are you reflashing supersu.zip when it asks you to update binaries? Just update the binaries.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
not working ...

I tried the "Normal" way then reboot - no success

I tried doing from CWM - no success

So I tried reflashing SuperSU - no success

I don't want to go with fixing root from recovery as some reports it can cause problems

any advice appreciated
[Galaxy S 4 i9505 Original Android Development] TLK3:
You didn't format /system. That's all. Boot recovery, wipe /system, flash ROM, flash gapps, flash supersu (or root in philz under advanced), boot, run supersu, update binaries, reboot, and enjoy.

Next time post in Q&A. This is for development related issues only. You're just having installation problems.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Exactly how I did it first and also second time ... binaries don't stick :(

sorry posting here - thought it is more development issue as I did everything exactly according to OP and e.g. what you said here
[Galaxy S 4 i9505 Original Android Development] tkruijer:
Hereby my promised donation... A couple of beers for you [MENTION=5464206]AntaresOne[/MENTION] (6R3460323Y098340Y)
[Galaxy S 4 i9505 Original Android Development] SeraphSephiroth:
I believe that 800mb is for apps/system addition etc, as opposed to standard storage
[Galaxy S 4 i9505 Original Android Development] Chibbo:
dunno if it's mentioned before but there is no way to unmount usb otg, it messes up my flash drive when I unplug
[Galaxy S 4 i9505 Original Android Development] franzyroy:
It's in the case of a installation (rom update), that! But he didn't talk about of installation.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
nevermind - I moved the OT to the Q&A and some advice is already on the table - hope it will work
[Galaxy S 4 i9505 Original Android Development] BoroChief:
had a similar problem...

could you take a discusage screenshot?

edit: discussion continued in Q&A
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
Please [MENTION=5464206]AntaresOne[/MENTION] , why did you add the CM updater ? it still running in the backround ... thanks ;)
[Galaxy S 4 i9505 Original Android Development] moffe:
Thanks...this solves the issue. Android system should show how the data is used like this.

Much easier to understand what is using what. :)

Seems chrome is the worst of the apps. :) And system data is using 2881
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Please post stuff not related to development in Q&A thread here

Building an update, now sms/mms bug on CDMA variants should be fixed. Active display is inside and some other fixes/updates
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
My bad lol, I forgot to remove it after I updated sources
[Galaxy S 4 i9505 Original Android Development] N!KE26:
Do you mean by active display the new ambient display in lollipop? Cant wait on the new version. :D
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No matter, you will remove it later (in the next)! ;) :laugh:
[Galaxy S 4 i9505 Original Android Development] PONKiE:
Since the last update to 15/12 my phone has not been asleep. There are kernel wakelocks for msm_camera and msm_hsic_host (checked with BBS). The msm_camera one has been keeping my phone awake 100% for the past 6 hours. Is anyone else experiencing this?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Possible, the latest sounds to consume more for me too.
[Galaxy S 4 i9505 Original Android Development] _phil07_:
When I try to power off my phone, it stays awake. I have to pull out the battery for like 10 seconds so that it doesn't boot up again. Is this only a problem on my phone or of the rom? (Latest build 15/12/2014 and I did a clean install. I also posted that in the Q&A section, but there was no answer)
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
I just tested it. Mine powers off as usual.
[Galaxy S 4 i9505 Original Android Development] Greatness_GH:
Have you checked the "Quick Boot" option under developer settings? If it is checked, the the device doesnt power off. I dunno (yet) if it's a bug, but it's been like that since 1st build.

I hope this helps
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
^^ Ya, that might be a feature actually, as the description of "QuickBoot mode" states: "Put device into QuickBoot mode instead of normal power off". Wonder if anyone knows if that behavior is wanted or in fact a bug.

Edit:

Okay Google helped here:

" [...] One such feature on the OnePlus One is QuickBoot, similar to the Fastboot mode found on certain HTC devices. Under this mode, the phone enters a low-power mode instead of completely switching itself off, which allows it to boot back up in less than 5 seconds when the user powers back it on again. [...] "
[Galaxy S 4 i9505 Original Android Development] yurividal:
Guys, what does this mean??

Mini heart attack...

http://review.cyanogenmod.org/#/c/82035/
[Galaxy S 4 i9505 Original Android Development] jd1001:
It's just a repository being dropped. I don't think it is anything to worry about.
[Galaxy S 4 i9505 Original Android Development] michelino.chionchio:
Maybe couse they are deunifying the developement
[Galaxy S 4 i9505 Original Android Development] munkyvirus:
It may be the final part of degarbaging the kernel they started around M10
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I still use that repo for my unified builds, I don't want to de-unify GSM/CDMA variants

By the way, the update is ready with some new tweaks/improvements inside... ;)

Uploading
[Galaxy S 4 i9505 Original Android Development] jd1001:
You're a legend!
[Galaxy S 4 i9505 Original Android Development] archangeles:
Error executing updater binary
[Galaxy S 4 i9505 Original Android Development] Mkfish:
I get no service with the rom installed. Shame because everything else is looking so damn good!
[Galaxy S 4 i9505 Original Android Development] kassaaam:
Flash the kernel that's why you're getting no service
[Galaxy S 4 i9505 Original Android Development] rboy28:
I think a small notice at the 1st post isn't a bad idea for RIL (to make clear what it is for (radio, service, data)) :)
[Galaxy S 4 i9505 Original Android Development] arth.nrick:
Yep:good:
[Galaxy S 4 i9505 Original Android Development] johannes140:
Rom in alpha state still beeing developed!

Guys, please excuse my rant upfront;

this is a DEVELOPMENT release in ALPHA state - what do you guys expect??? As genius as it is of [MENTION=5464206]AntaresOne[/MENTION] to manage to build a booting rom for our device, please accept that this is NOT suitable as a daily driver and that those of you, who do not know what for example RIL is, cannot really help with the development/debugging/providing of bugs/logcats etc.

It makes me angry and sad at the same time to see a good developer getting ambushed by all these small stupid questions that could have been answered by a simple Google search by every single one of you for yourselves.

This is not, what this thread - or xda in general - should be about. So, please, think about yourself, your questions before posting.

Thanks everyone ...
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
New build out!

Check OP for download and post #2 for changelog.

Please report here any bug you find, so I can keep track of them.
[Galaxy S 4 i9505 Original Android Development] Zenzr:
Flashing now! Is is better to clean install or can I dirty it over the last one?
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Will this work on VZW now?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
It's better if you do clean install passing from an Alpha to a Beta, but you can also just install new zip and do wipe cache
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Loki patch to flash kernel is inside, but untested. Please try on your device and report here :)
[Galaxy S 4 i9505 Original Android Development] znel52:
Confirmed working on my verizon s4. Just make sure to loki doki after you install ROM and Gapps. Lollipop is sick! Huge thanks to the dev.
[Galaxy S 4 i9505 Original Android Development] malybru:
Mod Edit

Thread cleaned

May I remind everyone that this is a "Beta" ROM

It is not yet a daily driver.

Things that do not work are listed in the first post.

If you do not understand the terminology used , you should probably not be using this ROM.

Please help the Developer by using the BUG REPORTER , instead of pestering him in the thread

Thank you

malybru

Forum Moderator
[Galaxy S 4 i9505 Original Android Development] tkruijer:
[MENTION=5464206]AntaresOne[/MENTION]

Working on the 20141119 version:

- Sound works

- No overheating (some users report that their phone is overheating...)

- Root works(checked with latest supersu 2.25)

- Camera, pictures and video recording is working (with sound).

- GPS

- SD Card works (probably fat32, dont know how tot check xd)

- Video works

- Youtube works

- Downloads doesn't FC anymore

- Alarm clock does it's work (timely also works)

- Changing language doesn't FC (someone reported this in earlier version)

- Closing all recents in the task switcher doesn't FC systemui anymore.

- My device wasn't 'compatible' with Instagram on previous version. Works now!

Not working properly/not available

- RIL (Duhhh)

- Huge battery drain (because of "Miscellaneous")

- Home button wake-up doesn't work

- The brightness slider in the quicksettingsmenu is kind of laggy, but nothing to worried about.

- IR Blaster

- Camera HDR isn't working

- Gesture typing isn't working

- Guest mode only opens my profile.

- Settings/Display/Advanced Settings gives no action at all. Someone else reported having a fc when pressing Advanced Settings

- Screen pinning works. Getting out of the pinned screen doesn't. Had to reboot to get out of the pinned screen, LOL. (holding the backbutton and overview button at the same time doesn't work)

Also, I have read in different forums that it should be possible to add a pincode or unlockpattern to the pinned screen. When you pin the screen, a screen should popup, asking you if you want to add a patern of pincode to unlock the pinned screen. I only get the option of unpinning the screen with the back and overview button.

- Ambient Display isn't a available option in: Settings/Display.

- Google Trusted Places is not yet available in Smart Lock (Should be available through the latest available Google Play Services (http://www.theverge.com/2014/11/19/7245375/googles-trusted-places-just-made-my-life-so-much-easier)

(Will edit if I find more)

The ROM is smooth, amazing work!

(I flashed 1119 over 1117, so no clean flash here).
[Galaxy S 4 i9505 Original Android Development] devilyuri:
is root working in the 2nd build?
[Galaxy S 4 i9505 Original Android Development] ahoslc:
http://review.cyanogenmod.org/#/c/78172/

Did that make it into this build?
[Galaxy S 4 i9505 Original Android Development] noremac258:
Root worked in the first one, I'd only assume it'd work in this one to.
[Galaxy S 4 i9505 Original Android Development] KyPbP:
Apollo works, and here I have GPS does not work. Then try to put the firmware over the previous alpha

Last beta supersu works fine http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Galaxy S 4 i9505 Original Android Development] BakedTator:
Will deberry said RIL is working an hour ago...

https://mobile.twitter.com/fitsnugly/status/535205733676351488
[Galaxy S 4 i9505 Original Android Development] cbanks3:
Gaining root on 20141119 release

If you don't have root access, try flashing this zip in recovery: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Galaxy S 4 i9505 Original Android Development] BakedTator:
Is there any way for you to keep the builds unified?
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Thank you :highfive:

Hehe... guys I don't use CM device tree from the beginning, mine comes from it and is modified (that's why I have unified builds)

If I want or I need to de-unify (for example, RIL incompatibilities), I do it

If I don't want to de-unify, I don't do it

Simple :good:
[Galaxy S 4 i9505 Original Android Development] BakedTator:
God I love you man...you earn the dev of the year award!!!!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
TWRP with F2FS management support updated to 2.8.2.0

Download: https://www.androidfilehost.com/?fid=95857557620393248

OP updated
[Galaxy S 4 i9505 Original Android Development] djbootleg:
i got an error 6 when trying to install the latest december app pack listed on the OP. the rom installs perfectly but the apps dont. I am using phils touch 6 recovery.

I am not sure whats going on but I had used the 11/29 build with the gapps from back then before it was PA-GAPPS and it worked fine.

Now I come to see that the apps link is dead. I will try using the latest version found here.

http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900/page28
[Galaxy S 4 i9505 Original Android Development] Greatness_GH:
But with our current build, that feature does NOTHING. I guess it's yet to be put in effect.
[Galaxy S 4 i9505 Original Android Development] reb1995:
Are you using the last version of the recovery? Some earlier versions of cwm/phils touch don't work with PA gapps - as stated in the OP for the PA Gapps...
[Galaxy S 4 i9505 Original Android Development] djbootleg:
I am using version 6. It worked before, and it also worked/works with PA apps when installing Dirty Unicorns 8.2
[Galaxy S 4 i9505 Original Android Development] woooson:
I had same problem with ext 4 and f2fs I'm using philz recovery

I installed ROM manager and fixed permissions worked both times to enable me to run tb

Hope that helps
[Galaxy S 4 i9505 Original Android Development] reb1995:
There are different versions of "6"... I'm using 6.23.9 with no issues....

https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
In the reality I'm active from september 2013 lol I was a Galaxy S Advance developer and I'm still a Team Canjica member (my "old" team)

Because I have already applied two and half months ago but they refused me, since I did not meet all the requirements (I needed and need to make more projects, and keep them active with a consistent activity in latest 3 months). I'll make many more stuff in coming months, then reapply for RD on April 2015

By the way guys, that kind of questions should be made on another place lol not dev/q&a thread, where?
[Galaxy S 4 i9505 Original Android Development] PterGriffin:
GApps package for Lollipop

link is broken!
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Another! ;)
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Thank you for the report, fixed.

Upload of today's build almost completed, stay tuned here for the next 20 minutes :good:
[Galaxy S 4 i9505 Original Android Development] franzyroy:
For info, these Gapps doesn't work with DualBoot, but no matter, I'll take those to my link.
[Galaxy S 4 i9505 Original Android Development] TLK3:
Fixing permissions allowed you to mount an external SD card formatted F2FS? I don't see how that's possible but I'll try. Usually F2FS not working is something kernel or ROM related.