yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] jhford:
Your signature includes "N10." Is that Nexus 10? I see Nexus 9's on eBay but no 10s. 32GB and LTE? Opinion?

I'm back to Oreo which seems to be free of the reboots. Have you tried the RR version? Opinion?

I just checked the battery on my deb and it looks like I'm getting about 3 hours total which seems pretty bad. Suggestions?

Thanks
[Nexus 7 (2013) Android Development] lollyjay:
Judging by the size of the rom I assume it doesn't include gapps?
[Nexus 7 (2013) Android Development] rlw6534:
I installed it on my Flo with a fresh GAPPS nano from today. It successfully booted and I'm playing with it now. I did notice that several of the "Resurrection Tools" are force closing the app... otherwise no major issues yet.... I am repartitioned with sysrepart_1280_120.zip from the first post and using f2fs on /data and /cache...
[Nexus 7 (2013) Android Development] followmsi:
The force closing of RR tools is common issue on few devices .. got several reports already.

If the settings are patched/fixed there will come a new RR version.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
No .. just PE does include gapps.
[Nexus 7 (2013) Android Development] rlw6534:
It's very, very cool that you are building PE and RR Pie for Nexus 7. Greatly appreciated!
[Nexus 7 (2013) Android Development] lollyjay:
RR is running well. Other than the few settings that fc, it is very stable. I have had no reboots as of yet.

I will begin checking battery life as soon as it is fully charged.

Fwiw i have EXKM installed and set zram at 512mb and swappiness to 100
[Nexus 7 (2013) Android Development] Bingley:
I installed PE 22 and worked fine, felt a bit janky, and also none of my play store purchases would appear or install, so I flashed the pico opengapps and it worked straight away. Left tablet on all day to update itself and it didnt hence the flash.
[Nexus 7 (2013) Android Development] warp_zone:
Previously I used stock rom and the compass worked correctly, but after installing PE 1/22, the compass has problem...

(It is always pointing to North)

I tried to other ROM but it does make no sense at all, so it seems to be hardware issue.

Reconnecting internal flexible cable doesn't fix this problem. thanks.
[Nexus 7 (2013) Android Development] JT1510365:
Dear followmsi thank you truly from the bottom of my heart for the amazing work that you do you truly mean so much to me and to the rest of this wonderful community we have here on xda:) I am so happy that you are working on pie for us and i am glad that our nexus 7s still have some active development going on. I will be doing some testing on your pe and rr roms tonight to see if any of them are better than crdroid nougat which is one of my fav roms and is currently the one i am using. I want to ask a question if i may ask. Would you be able to bring us either one of these roms which are aosp extended pie or liquid remix pie? I would love to see either one for our nexus 7 2013 but if you can't i totally understand:) Cheers:)
[Nexus 7 (2013) Android Development] abhifx:
Liquid remix has stopped development recently so that is out of the question.

Maybe we should make a poll as to which rom should be regularly updated. dont think its feasible to build and maintain so many roms.

i could be wrong though.
[Nexus 7 (2013) Android Development] JT1510365:
Then why is there this thread which is liquid remix pie for the s4 i9505 which was updated very recently i will put the link to it below:) I am running this on my s4 right now and i love it:)

https://www.google.com/amp/s/xdafor.../jdcteam-buffday-pie-release-01-t3877778/amp/

https://xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-buffday-pie-release-01-t3877778

Yes your right a poll seems fair! I wouldn't want the OP to be burned out on mantaining so many roms so i agree with you on this one:)
[Nexus 7 (2013) Android Development] ReBat:
Thank you for all your work! Really appreciate it. The one thing that breaks the PE deal for me is the lower quality of the audio which is probably due to the CAF graphics/audio/media sources. The sound in version 8.1 is crystal clear but in the PE 9.0 version it has some faint crackles and is less clear, which becomes very obvious when I use my hi-fi earphones. Therefore I restored 8.1 because the sound is very important to me. Do you think that a 9.0 version (with or without PE) with pure AOSP sources and similar audio quality as in 8.1 would be possible? I don't really need the PE stuff and a pure AOSP would be best for me.

Besides the lesser audio quality the latest PE version worked fine. No reboots or crashes.

The RR version, which forces some apps to shut down, has the same, lesser audio quality as PE.

Thanks again!
[Nexus 7 (2013) Android Development] abhifx:
The news came yesterday only. The news was on telegram channel.

Edit: Here is the screenshot
[Nexus 7 (2013) Android Development] m0crt:
Qcom h.264 codec decoder

Super work being done here. Thanks very much.

Question re codec.

I’m getting reports from the Moonlight application regarding a lack of h.264 decoding support. That application seems to rely on the qcom h.264 codecs.

This likely an app issue that they must deal with or is this something I can adjust / add to the r30 pie install I ran through yesterday?

Thanks

Mo
[Nexus 7 (2013) Android Development] followmsi:
Are you talking about Bluetooth audio quality or via cable ?

Just added the AptXHD codec stuff .. was missing in "new" sources.

Part of next ROMs.
[Nexus 7 (2013) Android Development] followmsi:
Correct - h.264 (avc) is missing BETA3 .. was a problem and is fixed now.

But soft reboots are still happening on AOSP sources.

PE and RR ROMs do have h.264 too.
[Nexus 7 (2013) Android Development] followmsi:
ROM

For tesing CAF sources I was thinking about AEX too .. prepared the device tree already.

RR, PE and AEX are using all the same CAF sources -> Lineage sources

Did not check Liquid ROM now.

Let's explain "my" current situation !

The last 2 years I was making classic Version for flo/deb - pure AOSP sources with some patches to make it work.

Monthly builds and some minor extras - just "classic".

Now in Pie the AOSP sources are not working as they should.

We were able to patch some stuff but we still have soft reboots on "classic" sources.

Currently the CAF sources are looking more stable for flo/deb.

The CAF sources are manitained by Lineage - for a lot of ROMs.

I will not integrate CAF sources into standard AOSP version .. for this reason I want to go for another custom ROM soon.

And we are still testing Pie.

Due to new job and other reasons I will have much less time in 2019 for all my Android stuff - for all devices !

For this reason I do "push" a bit at the moment to make the device sources ready !

When/If the device stuff is ready we can basically build "every" ROM.

And the sources are looking good now .. still some minor issues left.

As I need to reduce my Android time in 2019 I will go for just one ROM only !

Still not sure which one .. PE or RR - and no need to decide it now.

But :)

For another device we have similar situation with AICP ROM.

As the device soures were prepared another user has opened his own thread and publish the AICP version now.

The community has regular AICP builds but I am not involved anymore.

[MENTION=5653319]JT1510365[/MENTION] are you willing to build monthly AEX ROMs for flo/deb ? :)

Just have a look here ..

https://github.com/AospExtended/manifest

and here ..

https://github.com/followmsi/manifests/tree/flo-deb-aex-pie

Hope you have a better understanding ..

Cheers
[Nexus 7 (2013) Android Development] ReBat:
Audio quality via cable with high qualitiy Hi-Fi headphones.
[Nexus 7 (2013) Android Development] lollyjay:
"As I need to reduce my Android time in 2019 I will go for just one ROM only !

Still not sure which one .. PE or RR - and no need to decide it now."

My suggestion is RR. It is working very well for me.
[Nexus 7 (2013) Android Development] followmsi:
If you install aosp beta 3 .. Sound is "good" again ?
[Nexus 7 (2013) Android Development] jhford:
Thanks for this post. I have been testing all deb versions, and now have a clearer overview as to your game plan, me thinks. So, forgive the stupid question, but aren't the two classic versions, with which I started, the most stable daily driver choices for now, based on your post?

Thanks

Edit. I forgot to say that I'm currently running OREO, because PE still continually reboots on my debs, and the only problem I've noticed is that Chrome and Chrome Beta frequently stop which I didn't notice on the Classic versions.
[Nexus 7 (2013) Android Development] ReBat:
Sound was better with it but I did not spend much time with aosp beta 3 because of frequent reboots.
[Nexus 7 (2013) Android Development] followmsi:
One quick test ..

Change your system/build.prop

Form 1 to 0 ..

audio.offload.disable=0

Not sure if it will help .. and not sure if and when we can improve audio.
[Nexus 7 (2013) Android Development] followmsi:
Classic Oreo is considered as stable .. All the rest we are just testing now.

You are welcome to join testing :)
[Nexus 7 (2013) Android Development] abhifx:
My humble suggestion is drop aosp and instead build two roms if that is convenient.

PE or Lineage for less customisation but stock feel and one with good customisation like AEX or Havoc.

I would prefer Lineage but PE is such a hassle free experience, no gapps headache. Just flash and done

Rest is too complicated, RR, havoc, aex etc.

If its just one rom then my vote is for PE
[Nexus 7 (2013) Android Development] MikiGry:
PE seems simple and easy but (at last for Redmi Note 5) battery life isn"t great on it + one build is kinda big (gappps included). I vote for LOS 16

In my opinion as for now sources that give maximum stability should be taken and one simple rom (LOS 16 for example) should be chosen. After dealing with most critical bugs (in our case random reboots and UI glitches) variety of roms based on previously fixed sources can be extended
[Nexus 7 (2013) Android Development] rajsris:
For me, I've been on followmsi AOSP rom since he first started over two years ago. This is mainly because of the stock feeling of these roms, the way Google originally had the Nexus os. I now vote for PE forgot the same reason, as today's "Nexus" is a Pixel. The latest PE rom is super stable for the media consumption I'm doing on the tablet these days: YouTube, videos, Spotify, e-reader, while still giving those great Pixel features.

My main downside is battery life on PE is worse than Oreo 8.1.
[Nexus 7 (2013) Android Development] ReBat:
Thank you very much for your willingness to help despited the limited time you have available. I guess you are talking about the build.prop in the PE version, right? I will re-install it to try out your suggested change.

Edit: It seems to be a little better, but there are still crackles (not as many as before) and now my favourite sound enhancing software, VIPER4Android XhiFi, is also not working anymore. Another version of it works but is less good. Anyhow, it seems that the audio can be fixed in v. 9 and maybe you can implement it once we get to a final version. Thanks again for all your help!
[Nexus 7 (2013) Android Development] spocoeric:
I'm liking PE, but I just can't get over that damn google search bar.
[Nexus 7 (2013) Android Development] Bingley:
Install a new launch ie Nova
[Nexus 7 (2013) Android Development] yattodettaman:
[MENTION=5480152]followmsi[/MENTION]; [MENTION=7912782]Den147[/MENTION]

Let's make Wifi Display Working.

This rom has miracast : https://xdaforums.com/redmi-note-4/...eries--other-development/rom-crdroid-t3843665

and these are the commits that make it working.

https://github.com/crdroidandroid/a...mmit/83574428b79e94b6eaaf4bd694a3214cb9f4c6a3

https://github.com/crdroidandroid/p...mmit/c1025ba034f1dbafe930fe617c328a989ffe6fab

What do you think about ? can we take vendor libs from that device ?
[Nexus 7 (2013) Android Development] daedric:
Quick one: are your Flos and Debs entering deep sleep ?
[Nexus 7 (2013) Android Development] lollyjay:
My flo 32 on RR is around 2%/hr
[Nexus 7 (2013) Android Development] daedric:
My 32gb Deb running PixelExperience_deb-9.0-20190118-1236-UNOFFICIAL get's 0% DeepSleep.

Perhaps it's the LTE module...
[Nexus 7 (2013) Android Development] spocoeric:
Then I get no dark mode on the google now page. So frustratingly close to a perfect UI. :)
[Nexus 7 (2013) Android Development] misterchambo:
Yes. I'm getting great battery life on my Flo with the latest PE.
[Nexus 7 (2013) Android Development] spocoeric:
I can also report random reboots on my deb using PE. Seems to happen consistently from the lock screen.
[Nexus 7 (2013) Android Development] MikiGry:
I know that this can be a huge security risk but maybe disable lockscreen completely for a while
[Nexus 7 (2013) Android Development] ranaxda200:
I faced just opposite and back to omni. Drainage has stopped now.
[Nexus 7 (2013) Android Development] daedric:
Deb or Flo ?
[Nexus 7 (2013) Android Development] ranaxda200:
Flo
[Nexus 7 (2013) Android Development] followmsi:
Mido is snapdragon 625

The other links are from snapdragon 845.

Not sure if it will work on flo/deb/duma.

Did you test the blobs and config on duma ?
[Nexus 7 (2013) Android Development] followmsi:
Yes .. will have a look into deep sleep in the next time.

Flo seems to have same issue.
[Nexus 7 (2013) Android Development] taw62:
I'm running PixelExperience_flo-9.0-20190122-0001-UNOFFICIAL.zip since it was released and had 98 % deep sleep over night with 2 % of battery loss in 8 hours (flight mode).
[Nexus 7 (2013) Android Development] ranaxda200:
Here the same problem on oreo too on Flo.
[Nexus 7 (2013) Android Development] yattodettaman:
No. I didn't try yet
[Nexus 7 (2013) Android Development] misterchambo:
Ranaxda, what app are you using to show deep sleep,etc?
[Nexus 7 (2013) Android Development] FletchF:
Can I dirty flash PE over AOSP v3? (Assuming, of course, that I have already sufficiently enlarged my system partition.)
[Nexus 7 (2013) Android Development] the1dynasty:
Just flashed PE on FLO and it runs amazingly well... Wireless charging works too... Idk if that was answered yet lol... No issues so far that I can report other than minor jankiness on some animations... Thanks for keeping this tablet alive... I use it for my TV remote!!
[Nexus 7 (2013) Android Development] peterpv:
Those screenshots were made using EX Kernel Manager, the app works fine even if you don't use the EX Kernel :cool:

The Deep sleep is a bit hidden:

Menu => Tools => CPU Times

Menu => Show Deep Sleep

enjoy :)
[Nexus 7 (2013) Android Development] abhifx:
Have you done anything special to make it "sleep like a baby"?

Either the rom is ok or my battery is getting old as i have huge drain.
[Nexus 7 (2013) Android Development] lollyjay:
I don't have many apps installed. That's all I know. In use, battery drain is excessive (around 12% per hour):p
[Nexus 7 (2013) Android Development] Bingley:
Lots of niggly bits, but one thing that currently annoys me is the sound picker - I can't choose a ring/notification/alarm tone without the sounds app crashing and dropping me back to the settings
[Nexus 7 (2013) Android Development] followmsi:
gdrive - clean up !

No more space left on gdrive .. need to move old ROMs to androidfilehost.com ..

My last AOSP Nougat and Oreo ROMs.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
AospExtended

As I want to test it myself .. let's share it as well.

AospExtended-v6.2-flo-20190128-2034-UNOFFICIAL.zip

AospExtended-v6.2-deb-20190128-2141-UNOFFICIAL.zip

Tested the flo version with gapps pico and magisk 18.0.

Have a test yourself ..

Enjoy :p
[Nexus 7 (2013) Android Development] misterchambo:
I'll bite. What is AOSP Extended?
[Nexus 7 (2013) Android Development] drewski_1:
Despite it's name, it's a Custom ROM. I used it a few years ago on my Shield.

Tried to optimize, but not heavy on customization. Maybe "Lite Custom" would be better description.
[Nexus 7 (2013) Android Development] daedric:
Might be the LTE module/ril then...
[Nexus 7 (2013) Android Development] Ruggerxpunk:
PixelExperience doesn't install with a Keyboard, so I can never connect to WiFi, because the voice input doesn't allow input on that screen.

Has anyone found a way to install this ROM with a keyboard? I used the latest OpenGapps.

Classic 9.0 keeps telling me it's 'Preparing for setup...' in the notification bar.

Has anyone run into this or know how to remove it?

Thanks!
[Nexus 7 (2013) Android Development] daedric:
Yes it does. Do not use Gapps with PixelExperience, gapps are baked in.
[Nexus 7 (2013) Android Development] warp_zone:
I tried stock rom again and the compass works fine on it.

But it is broken on PE and AICP rom...

There seems to be some difference on hardware between people here's and mine.
[Nexus 7 (2013) Android Development] Bingley:
...or do. I installed PE and play store wouldn't sync and let me access any apps I'd purchased. Flashed pico gapps and works fine.
[Nexus 7 (2013) Android Development] warp_zone:
I examined whether the compass works or not on several roms.

Stock (marshmallow) : OK

Lineage (Nougat) : OK

Official AICP (Oreo) : bad

followmsi's AOSP (Oreo) : OK

followmsi's PE (Pie) : bad
[Nexus 7 (2013) Android Development] abhifx:
If you are using compass app from play store to check, the latest version uses a legacy mode which is not working in pie. disabling the same makes the compass work.
[Nexus 7 (2013) Android Development] warp_zone:
I used "GPS Status & Toolbox" and "Google Maps" app to check it, and the compass didn't work on these apps.
[Nexus 7 (2013) Android Development] Nomad1600:
Nice! I used AEX about a year ago. Had a really clean look and worked great on FLO. I have been resisting trying your Pie ROM (btw, many thanks for continuing development on the aging tablet) and running UA currently but I will give this a go. Again, many thanks!!
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] can you report on your testing of AOSP Extended?
[Nexus 7 (2013) Android Development] JT1510365:
Hey lollyjay I hope your having an awesome day:)

Just in case followmsi doesn't give you an answer here's what I did to install aex ROM:)

1. Resized system partition using clamors script

2. Did a clean flash and full wipe and installed Aex ROM

3. Flashed latest open gapps nano package

4. Flashed magisk 17.3 because magisk 18.0 causes issues like bootloop

5. Booted successfully

I am using AEX ROM pie currently on my nexus 7 2013 and it works really well for me and everything works except compass and 60fps in YouTube videos. SO for me its a daily driver:)

Thank you so much followmsi for aex ROM and your hard devoted work we appreciate you so much:)
[Nexus 7 (2013) Android Development] followmsi:
Oreo and Pie are using same sensors hal ..here we have missing SENSOR_TYPE_SIGNIFICANT_MOTION in code.

For this reason we have "light sleep" only.

Also the command "dumpsys deviceidle" will show we don't have required sensor for deep sleep. (mMotionSensor=null)

If "light sleep" is working fine you can get up to 14 days standby on flo device.

If you have battery drain on wifi, test to move to 5ghz wifi.

In my case I get light sleep on 5ghz better, 2.4ghz wifi does not always let sleep my flo device.

Still testing Pie on flo ..
[Nexus 7 (2013) Android Development] followmsi:
It's ok .. like it.

PE forces the Pixel feeling .. aex feels more AOSP.

Of course, everything can be changed on all ROM.

Don't expect any decisions about "my" future ROM now ..

Cheers

Still wait for an answer :)
[Nexus 7 (2013) Android Development] JT1510365:
Hey followmsi any chance we could get a fix for the compass in aex pie cause currently that's the only issue I saw other than 60fps in YouTube videos but that's a hardware limitation so nothing we can do about that:)
[Nexus 7 (2013) Android Development] Booroner:
I am using AEX ROM pie currently on my nexus 7 2013 and it works really well for me .

Thanks
[Nexus 7 (2013) Android Development] taw62:
I switched from PE to AEX and I must say it's even better! Thanks to [MENTION=5480152]followmsi[/MENTION] for your effort!
[Nexus 7 (2013) Android Development] FletchF:
We're you able to dirty flash over PE?
[Nexus 7 (2013) Android Development] lallolu:
Is there any kernel with double tap to wake?
[Nexus 7 (2013) Android Development] MikiGry:
720p 60fps should work fine. Our hardware is strong enough for that
[Nexus 7 (2013) Android Development] Booroner:
[

QUOTE=lallolu;78812993]Is

there any kernel with double tap to wake?[/QUOTE]

As far as I know, this takes it, download auditor kernel and configure.
[Nexus 7 (2013) Android Development] JT1510365:
Mmmm thats wierd it works sometimes for me but on most videos i watch on youtube it has trouble with 60fps

---------- Post added at 12:46 AM ---------- Previous post was at 12:43 AM ----------

The only kernel that would work with pie and doubletap2wake would be elementalx but sadly flar2 has not released a pie version of the kernel yet:(

Edit: ignore this post
[Nexus 7 (2013) Android Development] MikiGry:
It"s not perfect, but works. When CPU is busy with something else its starts lagging for example, but most of the time i"m able to play 720p 60fps videos from yt vanced. On LOS 15.1 at least
[Nexus 7 (2013) Android Development] lollyjay:
Just install EX Kernel Manager. It gas dt2w in gestures
[Nexus 7 (2013) Android Development] ipdev:
The kernel has support for DT2W.

As noted, you need a kernel manager to enable it.

Kernel Adiutor

Kernel->Wake->DoubleTap2Wake (Select Half)

FK Manager

Kernel setting->MISC->DoubleTap2Wake

EX Manager

Gestures->DoubleTap2Wake

Cheers. ;)

Edit:

Android 8 (Oreo), 9(Pie) and 10
[Nexus 7 (2013) Android Development] JT1510365:
Just download kernel auditor from google play and select wake from menu and then select apply on boot and half for dtap2wake I can confirm this is working on aex ROM which I am using:)
[Nexus 7 (2013) Android Development] JT1510365:
Thank you for confirming this my previous post was wrong:)
[Nexus 7 (2013) Android Development] spocoeric:
I dirty flashed AEX over RR. Kept getting com.google.phone has stopped. A clean flash resolved it
[Nexus 7 (2013) Android Development] Booroner:
AEX ROM is very stable for me, we hope more compilations for the improvement of battery and security patches.

Thank you for keeping our Nexus up to date and for your great work [MENTION=5480152]followmsi[/MENTION]
[Nexus 7 (2013) Android Development] taw62:
Yes, I uninstalled Magisk, wiped /system, dalvik, cache and then flashed ROM, GApps and Magisk and surprisingly it worked ;).
[Nexus 7 (2013) Android Development] abhifx:
Hey guys... How is th battery life on aex? PE is draining a bit too much then desired

---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------

@followmsi

Any chance for wireless display to work? It seems Lineage has reimplemented the same for pie. But i guess our drivers are a bit too old.
[Nexus 7 (2013) Android Development] lallolu:
I did not know that. I was using Elemetax on oreo just for this reason. Thanks a lot.
[Nexus 7 (2013) Android Development] JT1510365:
Battery life on aex seems to be a lot better than the latest stock ROM that came with the device which was marshmallow so I recommend aex to everyone over RR remix and pixel experience:) Plus it has several customization options and has only the options you need:) It doesn't overwhelm you with options:)
[Nexus 7 (2013) Android Development] prsa01:
Dirty flash (with system wipe) from PE to AEX, open gapps Pico, magisk 18. All went well.

VERY early impressions - like it so far. Will report when I have an idea of battery life, etc.

Update, 1 day use battery life seems very good. Feels like less drain than on PE.

Thanks very much for making these available!
[Nexus 7 (2013) Android Development] FletchF:
Just switched from PE9 to AEX. Based on very limited testing, the "freeze and then reboot" problem is gone. Very nice. Is there an old version of Netflix that is known to work?
[Nexus 7 (2013) Android Development] JT1510365:
Ignore this post