yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] avinashjirapure:
For google play services.... Provide all permissions from setting menu... & it will work
[Nexus 4 Original Android Development] deshmukhrb2000:
[MENTION=4217103]zaclimon[/MENTION] kernel is still stock one or u have integrated the custom one?
[Nexus 4 Original Android Development] mammenj:
Did you dirty flash from MM or clean flash?
[Nexus 4 Original Android Development] hk.happy:
Clean flash obviously :rolleyes:
[Nexus 4 Original Android Development] zaclimon:
The kernel is stock. I might do a test version of Quanta but I don't know when I'll do it.
[Nexus 4 Original Android Development] dramalicious:
How it's the battery life compare with M?
[Nexus 4 Original Android Development] ariesgodofwar:
So far, mine has been pretty poor compared to M, however, it is still a WIP, so very possible that the sources of drain may be eliminated once the sensors and other pieces are brought online. Once the foundation is solid, then the performance tweaks can be made. That said, it is smooth and fast for me.
[Nexus 4 Original Android Development] kryzeK:
Thank you, dude! I installed this app, cleared AGPS with it, waiting a minute and YES this works for me now.

But Weather Quick Settings Tile still don't works, so I installed a app called "GpsFix" to see what's is wrong. My GPS hardware is OK, Google Play Services location also. My problem now is my Android Network Provider.

Please, can you install this app and share a screenshot to see if the 3 location providers works fine for you?
[Nexus 4 Original Android Development] nitin.chobhe:
Can anyone confirm about the contacts sync? I installed v2 with pico open gapps and do not see contacts syncing

Nitin
[Nexus 4 Original Android Development] kryzeK:
Have you tried this?
[Nexus 4 Original Android Development] zaclimon:
Situation update

Hey guys, just to let you know a little bit about what's going on:

- Sensors have been fixed (Thanks [MENTION=4318865]DevSwift1[/MENTION] for the fix)

- Camera should be next (I'll work on it later today but I'm pretty confident)

- Same thing for MPDecision

The rom should be (I hope) stable enough in the next days. Stay tuned
[Nexus 4 Original Android Development] roomunho:
Works fine here with open gapps nano
[Nexus 4 Original Android Development] kol1124:
No words... Perfect bro! Keep it up! ✌

Wysłane z mojego AOSP on Mako przy użyciu Tapatalka
[Nexus 4 Original Android Development] paolocorpo:
You are wellcome [emoji3]

Inviato dal mio HTC One M9 utilizzando Tapatalk
[Nexus 4 Original Android Development] chusemaria1970:
Thanks a lot for All your work zaclimon.

Enviado desde mi AOSP on Mako mediante Tapatalk
[Nexus 4 Original Android Development] nitin.chobhe:
I tried that but didn't get this part "..and force sync on settings". I do not see "contacts" in Settings - Accounts - Google. I see only App data, Google fit data and People details. Am I missing something?

Thanks though :good:

This is great news man!

Nitin
[Nexus 4 Original Android Development] kryzeK:
"Contacts" appears on Settings - Accounts - Google for me a time after of install this apk. Install and give contacts permission for this case not already have.

"Force sync" is Overflow Menu > Sync now.
[Nexus 4 Original Android Development] kol1124:
Contact sync works good on my phone after clean flash ☺

Wysłane z mojego AOSP on Mako przy użyciu Tapatalka
[Nexus 4 Original Android Development] venu123:
I had the problem of contacts not syncing. Turn of autosync (uncheck box), then turn it back on.
[Nexus 4 Original Android Development] nitin.chobhe:
It worked after installing apk, going to settings - apps - Google contact sync - give permissions of contacts and then restart the phone.

Thanks for your help. This is my dd now :laugh:

Nitin
[Nexus 4 Original Android Development] orangek3nny:
Can you guys upload some logcats of the current build? Even if everything seems to work fine, it could be useful to fix the more hidden bugs.
[Nexus 4 Original Android Development] reisjpg8796:
hey guys... I have a little question for the developers. How can i make a build of this (or any) rom keeping the bug on the sensors. I want to have that bug because my nexus 4 sensors are dead and i cant install any rom 4.2.2+ the dead sensors causes bootloops i can only update with a rom that ignore sensors like this. This one is working pretty good for me. Can anybody help me?

Sorry for my bad english :silly:
[Nexus 4 Original Android Development] nitin.chobhe:
Attached is the logcat. Let me know if you need anything else. I would be more than happy to help :D

Nitin
[Nexus 4 Original Android Development] kryzeK:
Here my logcat: https://drive.google.com/file/d/0BzkwxIh2-kkYcmJvd0lFZXpYQkk/view?usp=drivesdk
[Nexus 4 Original Android Development] kamlesh08:
Do we need to wipe the data first or flash the zip first?

What should i do- flash the zip file first or wipe data first?:)
[Nexus 4 Original Android Development] dragos281993:
Lol. Of course you have to wipe the data + system + caches first. The OS needs to be installed on a clean system partition.
[Nexus 4 Original Android Development] kamlesh08:
Thanks. Actually in the guide above, wiping data is listed in 4 step after installing zip and Gapps. That's why I got confused.:)
[Nexus 4 Original Android Development] dragos281993:
Oh that's just the "data" partition. In that case you must respect the instructions. But make sure you wipe only that partition after flashing all the stuff. Before that, if you're installing this for the first time, a complete wipe (except for the internal storage) is recommended.
[Nexus 4 Original Android Development] kamlesh08:
Thanks. I really appreciate the help.
[Nexus 4 Original Android Development] fr3quency:
I just found the time to flash this beast. Went straight to v2 and I'm pretty impressed. The usual notable things in every new Android release are smoothness and battery. It is smooth for my tastes but not as Marshmallow and the battery usage is kinda scary. That being said, it's now my daily driver it seems and I like it. :) *insert cool Gintoki quote*
[Nexus 4 Original Android Development] damskrey:
Can anyone confirm that the setup wizard can auto rotate? my touchscreen is broken so i had to rotate the phone to press the next button in each marshmallow setup wizard:eek:
[Nexus 4 Original Android Development] popogijo:
Flashed V2 - very impressed. Rom runs good. Here's logcat - 1st one I've done so may be junk.
[Nexus 4 Original Android Development] nitin.chobhe:
[MENTION=4217103]zaclimon[/MENTION] in news :https://9to5google.com/2016/08/28/a...-oneplus-one-galaxy-tab-s-and-raspberry-pi-3/

;)

Nitin
[Nexus 4 Original Android Development] fr3quency:
Unfortunately I couldn't get a logcat using Kernel Adiutor, but I did get a dmesg. Don't know if it is useful but for the time being it's all I can do. https://justpaste.it/xu6w

Also the phone doesn't enter deep sleep, but stays at 384MHz.

Sent from my AOSP on Mako
[Nexus 4 Original Android Development] nitin.chobhe:
It goes in deep sleep for me. See attached screenshot

Nitin
[Nexus 4 Original Android Development] binder.marek:
For me, it goes deep sleep aswell ?
[Nexus 4 Original Android Development] xabier-bo:
Thanks zaclimon for your work!

Any chance to get sensors working?

The only thing I am missing at the moment is automatic screen rotation, which I need for some apps.

Said that, it's amazing having the N4 running nougat!
[Nexus 4 Original Android Development] ale29-09:
Are you planning to release a build with just the sensors fixed or you are waiting to get the camera fixed? I'm asking because I use my Nexus 4 just to play Pokémon GO (on my Xperia Z4 is actually UNPLAYABLE) and I just need GPS and the sensors working. :D

By the way, thanks for your hard work!
[Nexus 4 Original Android Development] avinashjirapure:
GPS is working in current build v2...
[Nexus 4 Original Android Development] ale29-09:
I know, but as I said I need also the sensors working. [emoji14]

For that reason I was asking if he's planning to release another build before he fixes the camera.
[Nexus 4 Original Android Development] kldoc:
Eager to see the commits on your github :D

Would seem too easy to be those selinux commits ?
[Nexus 4 Original Android Development] dragos281993:
For logs, you can use "Syslog" from the Play Store. It's pretty awesome. It let's you take whatever type of log you want and also it has a "live logcat" feature which does exactly what it says.
[Nexus 4 Original Android Development] haelmchen:
its is not rotating at any point. You'll have to wait for the next release.
[Nexus 4 Original Android Development] zaclimon:
Daily driver material?

Hey guys, this past week has been a bit tiring. (Was expecting some vacation and a bit of rest but got Nougat popping out of nowhere, thanks Telus!) That is without to say that I can consider this to be stable enough even though there are some caveats.

I must say also that you guys are heavy on the bandwith used on QuantaWorks. You guys managed to use over 260GB of over the last week XD. It shows that the Nexus 4 community is still well and alive.

Anyways here it is:

V3: (30/08/16)

- Fixed sensors (For you Pokemon Go people :p)

- Semi-Fixed Camera (Taking pictures works but video recording not saving and I'm a bit clueless. See below for details)

- Fixed MPDecision

- Enabled Doze

- Used GPU drivers from Flo's N developper preview

About sensors, as some of you may know, it looks like the use of Clang broke the use of our sensors, however we can force the part responsible of it to be compiled with GCC. The patch for you builders can be found here:

https://github.com/xyyx/android_bionic/commit/bb34389f42032b829cfe970c951bd527231d9302

About camera, I don't know what's happening since I have 2 possible theories. I can see that the OMX encoder has some issues. That said, it could be possible that our HAL needs to be modified for Nougat support as seen here:

https://source.android.com/devices/camera/versioning.html#hardening

If we use API1 HAL1, that's where it could get a bit tricky and can go harder than what I can possibly do. Flo doesn't have the same issue since it uses Camera2.

[MENTION=6117313]ganachoco[/MENTION] What's your insight regarding this? I know you had some issues with getting Google Camera because of Camera2.

Anyways enough talking. The build is available in the OP and I hope you'll be happy enough for the moment. Time for a little break now. :p

Enjoy!! :)
[Nexus 4 Original Android Development] hk.happy:
Mate, you rock, can't thank enough for your work !

Downloading the build
[Nexus 4 Original Android Development] bart.found:
Man, you're awesome!
[Nexus 4 Original Android Development] ale29-09:
Eheh, you are awesome man! Thanks a lot for your work!
[Nexus 4 Original Android Development] kol1124:
Love you ?❤❤❤❤

Wysłane z mojego AOSP on Mako przy użyciu Tapatalka
[Nexus 4 Original Android Development] kldoc:
Did you try Snapdragon Camera ? Still got to make a first build for Omni 7, but Snapdragon camera has replaced AOSP camera on Omni 6 for a while, works a lot better. Also, iirc, there are some selinux stuff to add, will check out later to point you the commits i used in the past :)
[Nexus 4 Original Android Development] ariesgodofwar:
[MENTION=5796730]dragos281993[/MENTION] incorporated the snapdragon camera into his PureNexus ROM. Nice little camera. I do recall him saying that he had to make some changes, perhaps he can advise as well.
[Nexus 4 Original Android Development] dragos281993:
If any of you tries to implement SnapdragonCamera, you'll need some commits from spezzi. He added some to the frameworks_base, frameworks_av, etc, so he's basically the one that made it possible.

Here are the github links. check the commits and you'll see what's related to the Snapcamera.

https://github.com/spezi77/android_frameworks_base/tree/mm2

https://github.com/Funny-Bunny/android_packages_apps_SnapdragonCamera

https://github.com/Funny-Bunny/android_device_lge_mako/tree/mm2

https://github.com/Funny-Bunny/android_frameworks_av

It might look a bit messy, but you'll find what you need there. But mainly, all this stuff is required to compile with SnapdragonCamera. Make sure you're always in the right branch of every repo (mm2). Modifications may be required, idk. I accidentally formatted the /home partition so I can't do it myself. Anyway, I hope you'll manage to implement it.

Edit: I almost forgot. There's some CM things in there too.

https://github.com/CyanogenMod/android_packages_apps_Camera2/tree/cm-13.0

Here's my local manifest file which I used the last time when I compiled PN. I didn't even bothered pushing everything to my repo. Take a look at it, look at the stuff I posted above, and you'll see what's needed.

https://drive.google.com/open?id=0B6SsZ9qokxalbEpoZEQtRnZtUFE
[Nexus 4 Original Android Development] zaclimon:
I haven't tried this one yet though if somebody could confirm me that it works with it, it could be pretty neat XD. Also I know that I'm missing some stuff (mostly init related as the other stuff are all for untrusted apps. And sys_ptrace is not allowed for mpdecision)

I'll make a little cleanup of my device tree so don't merge everything just yet. (if you haven't so already XD)

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Original Android Development] g33k0 b3lk0w:
Tried the ROM, love it, just can't Flash the Open gapps Pico version for 7.0, says I need 5.1.1 o.O
[Nexus 4 Original Android Development] roomunho:
-Full wipe

-reboot recovery

-flash Rom, flash gapps

-reboot
[Nexus 4 Original Android Development] sidnoit22:
Flash Micro Gapps. It works.
[Nexus 4 Original Android Development] italovsoares16:
-Wipe cache and Dalvik

-Flash Rom v3

It may be that the installation of the update? I'll have to pass it from scratch?
[Nexus 4 Original Android Development] zaclimon:
I believe that it's not even necessary to wipe the cache but that's at your own discretion. You're not obligated to wipe data upon installing the update.
[Nexus 4 Original Android Development] kol1124:
Confirmed ?

Wysłane z mojego AOSP on Mako przy użyciu Tapatalka
[Nexus 4 Original Android Development] granazis:
Hi to all on this thread and exactly tnx to
[MENTION=4217103]zaclimon[/MENTION] who started N building.Yesterday night i flashed the 2nd version of N by zaklimon just to taste it and noticed that there is no playstore app plus not possible to use my google account i used on M but only email(yellow folder) then i tried to return on any buckuped rom and exactly on latest by [MENTION=5796730]dragos281993[/MENTION],restored ok but when peboot to system its booted to twrp(3.0.2.0),tried many times plus the same happen trying to flash any rom zip,so ithink to solve is to flash the stock 5.1.1 from scratch.

Look please on attached twrp ss what i met trying to flash the rom(2nd build)

Any help or suggestion to avoid starting from scratch will be well appreciated,dont know if sideload flash the N build is a solution if yes may i try on 3d build?

Note:If possible to have to have an explanation why was possible to restore a nandroid backup on L(stock 5.1.1) running M and well worked and not from N to M? it would be useful to me just to increase my knowelge as my speciality in developing is equal to zero.

The rom clean flashed using open_gapps-arm-7.0-nano-20160828

Thanks in advance.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] rajdude:
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!

I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.

Is it possible to get root access without installing / flashing a new ROM?

I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://xdaforums.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605

Lots of geeky stuff there :) which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).

Unlock boot loader:

I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
[Xperia Z5 Compact Q&A, Help & Troubleshooting] civicsr2cool:
The only reason to use that guide is to backup ta keys for whatever reason you'd want to do that.

If you're after root on stock ROM the single easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. Solid marshmallow with root goodies. Xpower has everything and is deodexed and ready for xposed framework.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] rajdude:
just a little more clarification please?

Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM) :eek:

And I am looking up xpower...not sure what that is (yet) and why do I need it

I do want xposed framework though.

I wish there was a simple straightforward answer :)
[Xperia Z5 Compact Q&A, Help & Troubleshooting] civicsr2cool:
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] rajdude:
still a little confused

Ok thanks! So my understanding (so far) is :

We "must" flash a ROM in order to root a phone. Did I get that correct?

Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.

A little confused here...

I am a systems engineer (my day job). In Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......

We

never

have to install a brand new Operating System to get root access.

Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] civicsr2cool:
Android is Linux, to gain root in the ROM you have on your phone currently all you need is an unlocked bootloader to run SU, but then you'll be left with a phone that still needs a customized kernel to keep root and a DRM fix for the camera. Xpower 3.0 is that package.

You could really benefit from reading more. Google up on dm-verity and Sony Ric, and fastboot/adb for a little better understanding of what you're getting into without a pre compiled ROM. Messing around with any Android you'll have the majority of the same steps, unlock bootloader with fastboot, flash Supersu, customized kernel.. Etc
[Xperia Z5 Compact Q&A, Help & Troubleshooting] firdyRAY:
Why use a stable compiled ROM?

Let me list down and explain to you why it's best to use a stable compiled ROM. But first you need to understand these few things before you decide to unlock your bootloader and root.

Before Sony Z models kicked in, every rooted Sony device are still able to retain all the features that came together with the phone before it was rooted. When Sony introduce the first Z model, they start to create these things called DRM keys. DRM keys are unique algorithm (i guess i should put it that way) which is attached to every phone the same way an IMEI number is attached to every phone. In short, my DRM keys cannot be used on your phone and vice versa.

DRM key: It's a unique algorithm that holds all the unique features that an unrooted Sony phone boast such as camera quality, X-reality, High Res Audio etc etc.

The moment you unlock your bootloader, that's the moment your DRM keys will be lost. But don't panic, the wonderful devs on XDA have prepared a tool to backup your TA partition (a partition that contains your DRM key) for your own convenience if you want to relock your bootloader.

Then recently Sony/Android come up with new features called Sony RIC and dm-verity. (You may Google what these are all about but to my understanding it is placing limitations to people who root their phones to meddle around with the system settings of thier phone)

With all these "hurdles", it have taken some time for devs here to find a work around and like every fairytale ending, they manage to find a way.

Now you're wondering if you can actually root without flashing another rom. Good news for you: you can! There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting.

.. But ask yourself what's the point of going through the hassle of rooting and your phone is not tweaked for performance or for theming purposes?

That's when people flash roms and in Z5 compact's case, XPower is the best rom there is. It gives you all the performance tweak you need to make your phone lag free, it has a lite version that removes all the unnecessary system apps you can't delete without root, it gives you an option to add themes and framework from Xperia X with all those work around in place.

For your second question: why is there a need to install TWRP?

TWRP is a recovery tool which is a need for all rooted phone. It's also a tool for you to backup and restore your current rom so that you can rollback to the last working configuration if your phone went into a bootloop etc. Plus i believe all these guides require you to actually use TWRP to flash the SuperSU to successfully root your phone.

I hope this explains your doubts.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] rajdude:
Thanks a lot but...

firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts. :)

I googled Sony RIC and dm-verity:

I could not get find much on ric :(

Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.

So to compile what I have understood so far:

By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.

The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:

http://xdaforums.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100

First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?

Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA

Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.

So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."

Could you please post a link to that?

Thanks again!