yashsingh1/xdaforums huggingface dataset:
[ZenFone 2 Android Development] OfficerJimLahey:
No updates this weekend

As the title says, there will be no uploads for the short term.

I did a build last night, tried it out today, and came across big problems.

https://youtu.be/IjfynLDSPZ8?t=1m20s

As the description says, this was the second boot, which after the first, skipped through app optimization and then hung on "Starting Apps."

My phone narrowly survived as fastboot was non-responsive as well, not sure why. Luckily, gotta thank the CM devs for putting in insecure ADB on boot. I managed to adb reboot recovery while booting the third time.

So now I need to figure out what happened.
[ZenFone 2 Android Development] mapre64:
YouTube-link is invalid!

Warning

The request contains an invalid URL!

Advisory provided by Google and:

VigLink

Find out more about protecting yourself on the web at antiphishing.org and stopbadware.org.

tapatalked

Edit: works with Chrome ... sorry[emoji40]
[ZenFone 2 Android Development] OfficerJimLahey:
Yeah, was a malformed embed using vBulletin's YouTube button. Since I must have got the syntax wrong (guess it just wants the YouTube ID, nothing more), I made a link of it instead.
[ZenFone 2 Android Development] rex_perfect:
Dev

Hey dev.....where are you....??...we all are missing you......any boom...?
[ZenFone 2 Android Development] OfficerJimLahey:
Well, eight builds later (that's two full days CPU processing time), I am not much further ahead. First boot still hangs on "Android is Upgrading... Finishing Boot", which this is probably playing the role (as pointed out by the CM team):

--------- beginning of crash
E/AndroidRuntime( 7624): FATAL EXCEPTION: main
E/AndroidRuntime( 7624): Process: com.android.systemui, PID: 7624
E/AndroidRuntime( 7624): java.lang.NullPointerException: Attempt to invoke virtual method 'android.view.View android.widget.FrameLayout.findViewById(int)' on a null object reference
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:1129)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3929)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3900)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:652)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:887)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:110)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:62)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:228)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.ServiceMonitor.access$000(ServiceMonitor.java:49)
E/AndroidRuntime( 7624):	at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
E/AndroidRuntime( 7624):	at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 7624):	at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 7624):	at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 7624):	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 7624):	at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 7624):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 7624):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
I/ContactsProvider( 7601): Aggregation algorithm upgraded for 0 raw contacts in 66ms

They also said it's probably more of a Carbon issue.

UPDATE:

I heard back from Carbon, and they fast-tracked a commit for me that "without that commit you get a permanent SystemUI FC IIRC on MSIM devices.﻿"

The new build started about 10 minutes ago, which means I should still be awake by the time it's done.
[ZenFone 2 Android Development] OfficerJimLahey:
Working Build (Sept. 5th)

Well, after 10 failed builds, Carbon issued this commit, and saved my bacon. New release is up now. There should be a lot more stability now - I notice Adobe Acrobat doesn't force close anymore. Interested in what else is working better.

Change-log wise (being lazy because it's after midnight here), there is:

https://github.com/CyanogenMod/andr...mmit/c6a0a131c9027a0df341b7bb1dfce2af933b6499 (android_bootable_recovery)

https://github.com/CyanogenMod/android_system_core/commit/3c0e570fd28a132b2ee6c6fc73b50cb2a9702087 (android_system_core)

https://github.com/CyanogenMod/andr...mmit/b922f572d10a101f003b6ba39ae760d5fd12dd84 (android_bootable_recovery)

...to my forked projects (CM upstream patches). The rest are upstream to either the device identity, to Carbon, CM, or AOSP (see post two for changelog links).

Have a great day!
[ZenFone 2 Android Development] tusharind007:
thanks for your efforts
[ZenFone 2 Android Development] Ratedzelaya:
Been on this ROM for a couple days and saw a lot of graphical glitches everywhere. Other than that its a good ROM(daily driver)
[ZenFone 2 Android Development] OfficerJimLahey:
September 11th Build...

...is up on AndroidFileHost (my mirror). Having upload problems with XDA at the moment.

CHANGELOG:

- CM-zenfone2/android_device_asus_mofd-common

mofd-common: Reduce the brightness of the lowest auto-brightness levels

mofd: diable RS_DRIVER override

sensors: enable virtual sensors

- CM-zenfone2/proprietary_vendor_asus

mofd-common: enable virtual sensors

- CM-zenfone2/android_device_asus_Z00A

z00a: overlay: Update power profile from 2.20.90

- CM-zenfone2/android_kernel_asus_moorefield

display: Don't restrict the brightness level

- joelmaxuel/android_system_core

Pull Request:

Prevent integer overflow when allocating native_handle_t

sdcard: Turn on noatime for fuse mounted sdcard

sdcard: Properly handle deleted nodes

init: Fire a trigger when a class is started/stopped

Fix build break for multiple definition

fs_mgr: zram: allow specifying stream count

fs_mgr: When formating ext4 volumes, respect the length parameter

Camera: Longshot with Burst Functionality.

Merge tag 'android-5.1.1_r18' into cm-12.1

Revert "Charger: Add font to show real battery capacity in charger mode

Revert "libcutils/liblog: Add functions required by Huawei g620_a2 binaries
[ZenFone 2 Android Development] Nyks45:
Good bro
[ZenFone 2 Android Development] OfficerJimLahey:
Delay in the next build...

...as there was an issue with Carbon's Gerrit system.

It will thus be some time before CM upstream patches are back up to date.

Apologies for any inconvenience.
[ZenFone 2 Android Development] OfficerJimLahey:
September 24th and 25th Builds are now online...

...via AndroidFileHost.

A little explanation...

While Gerrit was broken, the CM devs added the fast charging UI, which included proposed changes to the CM tree. So while I was repo syncing, waiting for an upstream fix, I got an earlier build failure of healthd variables not being declared.

Once gerrit was back up (and after I found out that the branch has changed from lp5.1 to lp5.1.1), and in a frantic to get a CarbonROM build out, I reverted the offending fast-charge UI commit in the device tree, and finished my compilation. That's September 24th build in a nutshell.

After testing the core functions of the 24th build, I decided to sort out the healthd commit. I heard that git fetch wasn't doing as it is supposed to in applying the necessary commits, so I used an old standby. I forked the projects necessary as stated in CarbonROM's manifest (one was already forked), and applied the patches by hand. I then updated my local manifest, repo synced, and rebuilt. That's where September 25th build comes into play.

Build builds have F2FS support. I'm not testing it, as I bounce around with ROM's on my device so I don't want to potentially lose my data, but it is implemented as the CM team has, so the effectiveness of it depends on the recovery you are using.

As for other changes, please see post two. There were a lot in the grand scheme of things, and I feel too many small things to list here.

Happy flashing! :D
[ZenFone 2 Android Development] georgiem9:
cant swith off sim 2 or 1
[ZenFone 2 Android Development] OfficerJimLahey:
I think that's a preexisting problem, remembering from reading the CM thread. Seems like it's all or nothing (i.e. stuck having to toggle airplane mode). I only have one provider so I cannot really test the full extent of that.
[ZenFone 2 Android Development] georgiem9:
I find same problem on all 5.1.1 roms
[ZenFone 2 Android Development] OfficerJimLahey:
September 30th build is up!

Most notable for changes is the CM ZF2 team's redesign of the Quick Charge UI.

By the way, I am finally able to upload to DevDB, so downloading via AndroidFileHost is optional now. :D

Also, I see that the Bring-up Topic has more commits, I should have those integrated for next build (Turkey weekend ;)).
[ZenFone 2 Android Development] Calin:
Joel is the normal fetch process working?

I mean to cherry pick the commits from gerrit? Cause for the framework_base quick charge commit, i've been forced to modify the files for my own.
[ZenFone 2 Android Development] OfficerJimLahey:
Maybe because your FWB is different enough from CM it doesn't know what to do to merge.

I am in the same boat. I ended up forking those three projects (one of which was forked already) and patching the code by hand (copying and pasting on the github website). That means, whenever CM or Carbon commits an update, I will have to merge the upstream (there is six projects for me to check now, will soon be seven).

Luckily with Gerrit you can compare by patch sets, you just need to remember where you left off from when you applied the patches last time.

I realize this is not fully sustainable, because when the proposed Gerrit commits get merged, my local fork will (probably) not be able to accept the merge and if I have another commit topic in there, I will have to kill the fork, re-fork, and re-patch.
[ZenFone 2 Android Development] OfficerJimLahey:
October 4th build...13th...18th...25th...30th.

...is being uploaded as-I-write.

For changes, not much, except the stuff in the bringup topic (SOT meter always shows, differentiation of sensor ID's, and charger connect behaviour).

Unable to upload to DevDB agian, so be sure to check out AndroidFIleHost for download file!

UPDATE (why make a new post?):

Currently uploading October 13th build. AFH only once again, if DevDB gets fixed before next week I will hopefully get the latest uploaded locally.

Change-wise, took advantage of the latest frameworks_base changes in the quick-charge-ui topic (plus any other stuff that was updated in the background).

Enjoy! :)

FURTHER UPDATE

New week, new download. :D

October 18th build is online now, in both locations.

ONE WEEK LATER

Uploading October 25th build right now, going on AFH Mirror first.

Forgot to mention last week that we have gestures now. Just need to enable them (Settings > CarbonROM Fibers > Advanced Options)

Didn't really look at the device changes or the upstream changes today (only the CM topics, which have no new code). If I take a peek in a little while, I will update this post with the coles notes.

Enjoy!

FINAL OF THE MONTH

October 30th build up. I may slow down at this point, since focus is going toward Android 6.0 on many sides. I will watch the Carbon gerrit (lp5.1.1 branch) for any significant changes.

I have been fresh flashing for the past five weeks or so and then going back to a backup, so I haven't had much time to look around. I did today, brought my backup up to current. An app failed (Agenda Widget), that didn't fail with a fresh setup. Frustrated, and after I had some eyes on the logcat, I ended up switching to a different app (one that has been maintained for the past couple years).

The features I have been looking for are finally present: automatic call forwarding; edition of tiles (I wanted my sound toggle back). I notice you can enable onscreen nav bar and disable the hardware buttons (a later flash will make you turn the long press recents back on as well). Strangely enough, SlimPIE has disappeared. But, I didn't find it's experience all that consistent anyway.

There's a glitch with the "number in the circle" battery meter, that if you set to charge, a percent will appear next to the circle as well. But that may have been my fault when I committed the quick charge UI stuff. Speaking of UI, I finally tried out CM themes. Downloaded "Dark Material", works well (except that the in-call dialer is hard to see, but no big deal right now). And I mentioned the tiles earlier. When I tried to edit them before themes Settings would FC. Now, I have no issue.

Other than that, with two hour SOT since the latest flash (and a whole lot of flashing around since this morning - about 70% once I was done rebooting), I am down to 35% battery life.

Well, enough notes for tonight.
[ZenFone 2 Android Development] OfficerJimLahey:
November 6th build...15th...23rd...

...is currently on AFH and uploading to DevDB (XDA) as-I-write.

Two differences this time around. Firstly, you may have noticed in post two (or somewhere else) that the CM-zenfone2 github is now defunct. I am now pulling the device identity projects directly from CyanogenMod.

The other, is that jrior001 posted a proposed fix to the BlueTooth bug (BT shuts down after about three days - toggling won't bring it back - only a reboot will). As that change is not mainline yet, I cherry-picked it from Gerrit. So post two has a new section called CherryPick(s).

Other than that, Carbon FWB didn't change since the last build (android_vendor_carbon was the only Carbon project that did). As I said in the last post, things are starting to slow down now.

Cheers!

UPDATE:

Well, the BT fix didn't pan out. So I made a new build without the patch. Good timing, because the Android rollup updates came though to Carbon on the 9th or so.

As usual, new build in the Downloads section, the OP, and on AFH.

ONE MORE:

I didn't notice it until I went to copy the latest version on the device, but MicroSD wouldn't mount properly with the Nov 15th build. Nov 23rd build fixes that problem though, found in the usual locations. Also, vendor info is updated, which explains the noticeably smaller file size. Enjoy!
[ZenFone 2 Android Development] Aceofzeroz:
Heya, I wanted to thank you for the great Carbon builds of late which are really delivering more than ones before! :D I tried last week's build last weekend and I'm surprised at how much more stable, smooth snappy and battery efficient it's become! So far I haven't experienced any annoying bugs or anything outside the usual CM12.1 bugs. LED is working fine for those coming from Resurrection Remix. ;)

I haven't tested every single thing, which is where other people's reports can come in handy. I especially love the battery life in standby even with the stock kernel (<1% per hour), despite the usual Android OS topping the chart. For those who thought the rom was on hiatus, it's still being uploaded the AndroidFileHost.com so give it a try! :cool:
[ZenFone 2 Android Development] lumin25:
This Rom by chance has floating Windows?
[ZenFone 2 Android Development] Aceofzeroz:
Yeppy, working fine with notifications and other settings. :D:cool:

Sent from the Ace's MB865 using Tapatalk
[ZenFone 2 Android Development] bmwkeith:
Just flashed the 11 /29 build earlier today and it is running really well. Thanks for the update.
[ZenFone 2 Android Development] swaglordk:
How is this compared to Resurrection Remix? How;s battery life ? Any other benefits/improvements from this ROM?
[ZenFone 2 Android Development] OfficerJimLahey:
No idea, I never flashed RR. Little to no clue what other AOSP-based LP ROM's are like beyond CarbonROM.

For me, standby life is same as stock. When the device is awake, it's a little worse.

I have a mini review from October 30th (or 31st) when I flashed to latest (up until then I was sticking with an older version). As said above I didn't really try out other ROM's (with one 30 minute exception to help out a friend). What I liked was being able to edit the quick toggles (first time I tried it I got a FC, but did not have any issue after I applied a theme - don't know if that's related though).

I see that automatic call forwarding is built in now, but everyone probably has that.
[ZenFone 2 Android Development] OfficerJimLahey:
Moving Forward...

Time to break it down - queue the sad music...

Due to certain circumstances, I have been left to encrypt my device, on stock, without root access. Given the arrangement, it would not be feasible for me to test a build as it will either be very time consuming (set up a device from scratch for every "restore"), or have other consequences.

So I no longer have a development device, since my DD is too much my DD. I have considered buying a ZF2 Laser to make my new DD, but I cannot justify plunking another $300+ CAD less than six months from when I bought a phone I intended to use regularly for a few years.

I have arranged for a tester, but to ease his load I have changed the update schedule to once a month, with an intention that when Android 6.0 becomes mainstream (I see that consumption of CM13 has begun today), this project will be end-of-life (unless someone else picks up the reins - then I will happily apply DevDB permissions over).

This touches on my intent with CR 4.0 (CarbonROM based off of Android 6 Marshmallow)... I may play with building it in the coming months, but there will (likely) be no release of it from me.

So if anyone is interested in CarbonROM enough to build for it, here's your chance. For the build process I will be happy to provide assistance, since that is something I can still do in parallel.
[ZenFone 2 Android Development] happydad4130:
Have u found anyone to build or take over the project?
[ZenFone 2 Android Development] OfficerJimLahey:
Not yet. I do have a tester, and a December build in his access.

I don't want to pester the tester, ;) I will send him a nudge this weekend to see if he has looked at it.

December's build won't be too much of a big deal. CarbonROM development has waned early December (only the 6.0 has picked back up in the past week-and-a-half), so the security level patches for LP are still on November. Looked to have been about a half-dozen Carbon-related commits since the Nov 29th build. The CarbonROM team intended to put extra focus on 6.0 for the next little while, but if it becomes the case that LP becomes an abandoned branch, then I will cut my losses early (I intended to wrap up in May/June).

Hope this helps.
[ZenFone 2 Android Development] lumin25:
[MENTION=5720423]OfficerJimLahey[/MENTION]

Hi, dude did you couldn't build a last build with the latest changes and Asus?

I still prefer to use the custom 5.1.1 because of resources.
[ZenFone 2 Android Development] OfficerJimLahey:
Hello,

Vendor stuff looks to be still back in .139 version. I do have a build with the calling screen fixed (apparently) - interestingly enough, CM merged that fix in their stuff today.

I have a mid-December build on the testing block. The holidays sort of messed that one up. Think what I will do is try a build tonight (there were some upstream issues for some a couple days ago) and make that one available for the tester instead.

At any rate, something should be ready relatively soon. :good:
[ZenFone 2 Android Development] lumin25:
Thanks a lot bro.

If you need a tester you can count on me.

Great work.
[ZenFone 2 Android Development] OfficerJimLahey:
January 8th is up!

This should fix the call screen ugliness issue, a patch that has been in the source since early December.

My tester points out one glitch, and it may have been there a while... under "About Carbon", if you scroll down, Settings FC's. It's assumed that it's caused by a missing or corrupted image.

Enjoy nonetheless!
[ZenFone 2 Android Development] lumin25:
I've been looking forward for this great man.

I will test right away.

Thank you very much

Just a few questions.

COPPS will still work?

Xposed will still work?

I think so, but it never hurts to ask.
[ZenFone 2 Android Development] OfficerJimLahey:
What is COPPS? Do you mean CApps (I never tried) or Gapps (I suggest OpenGapps at this point)?

I never used Xposed with this ROM, never saw the need to (since it's often counterproductive). ;)
[ZenFone 2 Android Development] lumin25:
Yes, CAPPS??
[ZenFone 2 Android Development] mvp001:
Can I install this rom In a model Asus_Z00AD??
[ZenFone 2 Android Development] Calin:
Yes you can ;)

Yes the CAPPS are working
[ZenFone 2 Android Development] mvp001:
Excellent thanks.
[ZenFone 2 Android Development] OfficerJimLahey:
Final version up....

...on AFH as per usual.

Still looking for someone to take on the Lux challenge. I have heard of a lot of grief building this device for AOSP 6.0.1 (and CarbonROM is much like AOSP for Lux since they are not basing themselves off of CM this time). I am still involving myself with CarbonROM, just for another device (Nvidia Shield Tablet).

Given Carbon has halted development on the LP5.1.1 branch in favour of Lux (a little while back), and since earlier this week CM 12.1 for the ZF2 went EOL as well, I see no need in making new builds that are only updated by the odd upstream CM package. I have continued to maintain a Kitkat branch with security patches for an older device, but I don't feel like doing the same here. Not under current conditions.

So this is all. Hope you enjoyed the ride, and the ROM. :cowboy:
[ZenFone 2 Android Development] lamp216:
how about the SOT with this rom, im now on stock and wanna know if with custom rom have the Android System battery drain bug
[ZenFone 2 Android Development] razshahan:
need help

Hello guys, recently i factory reset and wipe disc from recovery mode, so my operating system is gone. I have twrp v-2.8.5.0 installed. i tried to flash UL-Z00A-WW-2.20.40.183 / UL-Z00A-WW-2.20.40.184/ UL-Z00A-CUCC-2.20.40.185 firmware (which i downloaded from asus official website) using adb sideload but it shows Error:closed . I checked and found that ADB is compatible with the version of twrp. previously i had a slimLP rom installed but i faced many issues with it. So i want to go back to asus firmware. on my phone box it is written that android TW but i can't find any TW firmware on asus website. So, anyone can help how can i get back to asus original firmware?? thanks.
[ZenFone 2 Android Development] OfficerJimLahey:
Sorry, this thread is for CarbonROM-related discussion (which according to above, you did not install). With that out of the way...

Pretty sure you need original recovery in order to flash the original ROM. As for finding the TW version, I haven't the foggiest. Maybe there is something in general or you can ask in Q&A?
[ZenFone 2 Android Development] Vinnibaby:
Por favor , faça pixel máster ficar compatível , obrigado.
[ZenFone 2 Android Development] razshahan:
Yeah, I had to use original recovery to install original firmware, that's why taro wasn't working. Now problem solved. Thanks
[ZenFone 2 Android Development] OfficerJimLahey:
PixelMaster requires the ZenUI framework, which I doubt will ever become available. Sorry.
[ZenFone 2 Android Development] giovan797:
Did I miss anything? I appreciate the feedback, and any thanks as well!

XDA:DevDB Information

[ROM] [UNOFFICIAL][LP 5.1.1] CarbonROM (Z00A), ROM for the Asus ZenFone 2

Contributors

joel.maxuel

Source Code: https://github.com/carbon-z00a

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.10.x

Based On: CyanogenMod

Version Information

Status: Beta

Created 2015-08-07

Last Updated 2016-08-09[/QUOTE]

Any prediction of a custom ROM to a version based on the stock rom MM 6.0 for Z00a? :D:D
[ZenFone 2 Android Development] OfficerJimLahey:
Please clean out the OP quote in your post. There is no need to quote the OP (a mention would have got my attention just as well).

As to your question (which i consider off-topic as this is a 5.1 ROM), I heard that 6.0 vendor blobs are being tested, but nothing new has been pushed to TheMuppets yet.