yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] followmsi:
Some more easter eggs :D

Only for reference I did made new Lineage and PE builds - based on "my" AOSP sources.

Just testing lineage-16.0 on flo ..

lineage-16.0-20190421-UNOFFICIAL-flo.zip

lineage-16.0-20190422-UNOFFICIAL-deb.zip

PixelExperience_flo-9.0-20190422-0737-UNOFFICIAL.zip

PixelExperience_deb-9.0-20190422-1048-UNOFFICIAL.zip

All repos and manifests have been updated now !

To finalize the switch of the sources there will come one last RR build for reference in the next time.

For ROM devs:

[MENTION=6005084]ripee[/MENTION] [MENTION=7166349]turbolukex5[/MENTION] [MENTION=6508440]liamtw22[/MENTION] [MENTION=5653319]JT1510365[/MENTION] ..

Pls check updated manifests first !

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

los-16.0-aosp -> https://github.com/followmsi/manifests/tree/flo-deb-lineage-16.0

pixel-piel-aosp -> https://github.com/followmsi/manifests/tree/flo-deb-pixel-pie

rros-los-16.0-aosp -> https://github.com/followmsi/manifests/tree/flo-deb-rros-lineage-16.0

aosp-p (classic) -> https://github.com/followmsi/manifests/tree/flo-deb-aosp-p

If you keep your existing roomservice.xml file you continue building on "old" sources !

Just replace complete roomservice.xml file and do "repo sync --force-sync" aferwards.

For Havoc, Liquid and any other ROM you will need to create new branch based on "los-16.0-aosp".

Or use any other "*-aosp" branch - all the "*-aosp" branches are used now !

We need a few kernel changes .. new branch too.

Tracking "own" "hardware/qcom/display" and also "hardware/qcom/media" now.

Switched to "my" old blobs.

All the changes are included in updated manifests !

Happy building !

Enjoy :p

EDIT:

We are still searching ROM dev for regular PixelExperience builds for flo/deb :)
[Nexus 7 (2013) Android Development] dealpapa1:
is lineage the same as ripee's gdrive? the file size are different.
[Nexus 7 (2013) Android Development] misterchambo:
Thanks so very much for the Pixel Experience update, followmsi! My favorite out of them all! Fewest issues, easiest install, Gapps included, etc!
[Nexus 7 (2013) Android Development] a8ksh4:
OMG, [MENTION=5480152]followmsi[/MENTION], you do some awesome work. I'm stoked that the compass stuff is good now. I'm trying the Deb pixel experience build in my car tablet driving around tomorrow to see how the navigation does. Woot!
[Nexus 7 (2013) Android Development] curiousde2002:
USSD Codes

Anybody managed to send USSD codes on Deb?

I used this module [Xposed][MOD][Android 4.4+] SMS, USSD, tethering and native SIP for Nexus devices up to Oreo ROMs successfully but on Pie there is no xposed framework.

I'm using a prepaid SIM card presently and would need this feature urgently.

I guess it's not possible to include this feature in the ROM:D
[Nexus 7 (2013) Android Development] JT1510365:
i could probably mantain pixel experience pie rom for flo and deb and build monthly builds and i will create a thread for it:)
[Nexus 7 (2013) Android Development] abbazaba:
Where do I download the Pie version of ElementalX for the N7? ( "ElementalX-N7-7.02-Pie-20190319" )
[Nexus 7 (2013) Android Development] followmsi:
[MENTION=6005084]ripee[/MENTION] will continue building regular Lineage builds.

my lineage builds are just one time builds for reference/testing.
[Nexus 7 (2013) Android Development] followmsi:
Yes, you need both.

Otherwise build error.

Found a typo bug in RR deb branch .. forced pushed the corrected version today.

Just finished the test builds for RR.
[Nexus 7 (2013) Android Development] followmsi:
Pls check the "KERNEL" folder ..

https://drive.google.com/open?id=0By6p5AdQfavBUlhsLWFHZThGTnM
[Nexus 7 (2013) Android Development] followmsi:
As said before .. one last RR ROM to finalize the switch of the sources.

This is a snapshot of the current sources ..

RR-P-v7.0.2-20190423-flo-Unofficial.zip

RR-P-v7.0.2-20190423-deb-Unofficial.zip

Enjoy :p
[Nexus 7 (2013) Android Development] followmsi:
Thanks !
[Nexus 7 (2013) Android Development] JT1510365:
No problem and i also ran and compiled my own build of Resurrection Remix ROM pie for flo if anyone wants to use my version feel free to test! Compass and hw decoding should be fixed because i am using your new sources so huge thanks to you followmsi! Sorry but i won't be making a rr remix pie build for deb users but i am currently almost finished building aicp pie for flo! Hopefully it builds and if it does i will create a thread for it! Then i will work on bringing us carbon pie and aosip pie to our nexus 7 2013 as well as more roms if i have the chance:)

Oh and aicp pie will come to deb as well:)

Download here:

https://www.androidfilehost.com/?fid=1395089523397950753

---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------

Thanks after i work on aicp i will work on aosip
[Nexus 7 (2013) Android Development] peterCR56:
i've had this problem since stock rom

it will work ok for a few days then wont rotate, have to reboot or boot into recovery to get it to work again

The problem started since Android Marshmallow for me, i've been hoping these current updates would "cure" it, but unfortunately not :(
[Nexus 7 (2013) Android Development] JT1510365:
Actually I can't build and maintain pixel experience because I don't have enough space on my hard drive due to pixel experience including gapps so I can only build other ROMs so we will have to find someone else that can do it:)

---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------

Yeah your issue is hardware issue and you need to take the tablet apart and fix it yourself or take it to a repair shop but rotation is never a problem for me:)
[Nexus 7 (2013) Android Development] followmsi:
Just for info ..

vendor/gapps requires approx. 1 GB disk space .. not more.

You do not build gapps .. you are using a bunch of prebuilt gapps apk files.

You increase system.img size by including those gapps.

https://gitlab.com/PixelExperience/vendor_gapps

As well .. the manifest is configured to pull latest revision only - of all the apk files.

Exactly for this reason -> to save disk space on build machine.

Just have try .. you may still take over PE later on :)

Cheers
[Nexus 7 (2013) Android Development] JT1510365:
Thank you I will look into it:)

Edit: is there any way I can contact you I am running into problems with building the ROMs I wanted and unfortunately you disabled your pm. I really need your help as I really want to create more ROMs for everyone but I can't seem to get them building. If you have the time feel free to email me my email is jontran95@gmail.com and if you have telegram or Skype we can chat on there:) Hope to hear from you soon:)
[Nexus 7 (2013) Android Development] sir_bazz:
Dude, thanks so much for PE. So friggin happy to see another update.

Cracked the screen on my deb early this month and only got it replaced today so will install the new PE and begin testing tomorrow.
[Nexus 7 (2013) Android Development] EclipseGT:
I just flashed twrp-3.3.0-0-flo.img to upgrade from twrp-3.2.3-1_UA-flo.img and now i don't show to have a Vendor partition. Will this be ok to run AEX or will i run into problems without this partition.
[Nexus 7 (2013) Android Development] Buratei:
I flashed the march version of ElementalX kernel but not getting OTG+charging. Is there a setting to be turned on, or perhaps OTG cable needs to be re-plugged in?
[Nexus 7 (2013) Android Development] followmsi:
PM is not blocked .. never been.

In case of problems send me a PM with your telegram info.

Enjoy your weekend !
[Nexus 7 (2013) Android Development] Buratei:
Since I have done the battery removal mod (hooked up to the much beefier car battery), charging shouldn't really matter. I was just hoping to use it as a wakeup trigger, which I conveniently replaced it with USB device connected trigger (USB hub/dac/flash drive all get powered up and connected on ACC input).

Alas, the charging circuit "thinks" it is draining when whatever it is doing against the humongous 60AH behemoth is just a drop in a bucket. After a few days of leaving it in airplane mode+screen off, the imaginative battery of the tablet fully drained and the tablet went into the low charge state. I either need to make OTG+charging work, or alternatively find a way to trick the charging circuit into believing it is fully charged. Currently I am feeding 3.9-4.0V to the battery charging circuit header snipped from the original battery. Worked flawlessly with timur's USBrom, but I am upgrading due to the lack of absolute volume disable feature.
[Nexus 7 (2013) Android Development] followmsi:
Pls check EX kernel thread for more details about the OTG+charging topic .. I did use "original" EX code.
[Nexus 7 (2013) Android Development] tsiftsism:
Hallo,

since my Nexus is running the rom from the link i have quoted, and the last few days i have battery drain (my tablet stays awake even if the Wi-Fi is turned off and i don't use it at all), can i flash AospExtended-v6.4 on top of it without wiping any partition and losing the data?

Or should i fully wipe the tablet in order to flash AospExtended-v6.4?

I can't figure out what is causing the battery draining!!

Thanks.
[Nexus 7 (2013) Android Development] Buratei:
Thank you for the response, I think it could be a hardware issue on my side.

I went back to timur's MOB30X just to see how charging works on that, and noticed the tablet is heating up like crazy (74-78C in TWRP just restoring a backup). What's more, it is quite warm to touch even when turned off and just plugged into charge! Maybe it is my improvised battery-less mod, maybe tablet itself. The tablet used to work fine for months until I made some minor changes like tidying up the cable or changing the step-down coverter.

I will be picking up another used flo tonite, hope that settles it!
[Nexus 7 (2013) Android Development] Buratei:
aww crap, help me out guys :(

i got me another flo, freshly bootloader unlocked by me. I went straight to flashing the twrp on followmsi's google drive, and now it boot loops after failed attempt at running some script. screenie below:

trying to get into fastboot to flash another version of twrp, but it wont respond any buttons sequences except holding the power button :(

EDIT: fastboot works... now I need to figure out which version of twrp to go with. I am guessing there is some sort of intermediary version I need to go through before flashing the later versions...

EDIT2: had to reset to factory image (flash-all.bat failed with "cannot wipe userdata" or something along that line, so had to manually remove the -w parameter), the do all this: https://xdaforums.com/showpost.php?p=69012743&postcount=682 except I used firmware.mobi instead of the deprecated CF-autoroot. Worked like a charm! now I need to do the repartitioning and all that haha...
[Nexus 7 (2013) Android Development] lollyjay:
Hey [MENTION=4842109]Buratei[/MENTION] glad to see that you are back on track.
[Nexus 7 (2013) Android Development] jhford:
Possible returning user

I used this Rom on my 2 debs for several months but experienced excessive random reboots and switched to Ripee's LOS Pie Rom. But now I have screen tearing when scrolling and it flashes with each touch. I use the old but great Swype keyboard and this issue makes it difficult to Swype. So, has the rebooting issue been fixed on this Rom? And does anyone have the screen tearing problem?

Thanks
[Nexus 7 (2013) Android Development] IvanHephaestus:
Your eMMC is probably ded, time to buy a new phone
[Nexus 7 (2013) Android Development] Buratei:
Thanks! Spent some time yesterday to set everything up, still wish there is tablet talk equivalent that works on Pie. On another note, I use tasker to display suspend/wakeup animations but haven't found a video player that loads instantly without showing its own UI elements. My goal is to make it look as seamless as the powerevent manager on timur's kernel. The video viewing app on AOSPExtended loads fast, but shows a toast near the top of the screen with the file name.
[Nexus 7 (2013) Android Development] ChrisM243:
Very nice to see that the old Nexus still gets attention. Since I don't have any updates from LineageOS anymore I was looking for something new.

Do we have some options to use the hardwarekeys? Can we see somewhere the status of the security patch level (since not all roms have this)?
[Nexus 7 (2013) Android Development] followmsi:
You can see patch level in settings .. all are based on April 2019 .. May patches are coming soon.

In developer settings you can enable "advanced reboot" menu .. to be able to boot directly into recovery.

Happy testing !
[Nexus 7 (2013) Android Development] ChrisM243:
Hi, thank you for your quick reply. If I remember clearly, the Nexus also has hardwarekeys. Are we able to enable these as well (since the Nexus has really large bezels)?
[Nexus 7 (2013) Android Development] followmsi:
Sensors .. in some cases they do prevent proper deep sleep.

Unlegacy is using different sensors wrapper.

I have cherry picked this change for testing .. looks good.

https://github.com/followmsi/android_device_asus_flo/commit/02f62fb2cc0d13afe0ba4e74ae90282d0b57c238

Sensors seems to be more "sleepy" now.

For testing you can replace the lib your self .. pls manually replace in /system/vendor/lib/hw

sensors.msm8960.so.zip

This change will be part of next AEX build ..

Cheers
[Nexus 7 (2013) Android Development] JT1510365:
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to [MENTION=5480152]followmsi[/MENTION] for providing the fix:)

Download here and flash in recovery:

https://www.androidfilehost.com/?fid=1395089523397959956
[Nexus 7 (2013) Android Development] followmsi:
One more "classic" version ..

flo-Classic_05-2019_AOSP_9.0.0_r37_followmsi.zip

deb-Classic_05-2019_AOSP_9.0.0_r37_followmsi.zip

Changes:

- Switched Sensor wrapper

- Enabled NFC ( seems to work now .. but still battery drain when enabled.)

- Google security updates -> May 2019

- New kernel (sound control .. etc.)

For the System repartitioning / Opengapps: Error 70 topic pls have a look on the first page.

Enjoy :p
[Nexus 7 (2013) Android Development] Ch3vr0n:
Can I dirty flash this over the last 8.1 build you made? Already repartitioned. Is nfc enabled or disabled by default? Debian device.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[Nexus 7 (2013) Android Development] JT1510365:
No clean flash is mandatory

---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------

The nexus 7 2013 does not have hardware keys it only has on screen nav keys don't you own this device?
[Nexus 7 (2013) Android Development] tinyturtles:
Hi all, now that the sensor fix is in, I'm trying to reflash the ROM! However, I install the ROM, install Gapps, then boot up and get stuck on the "Checking for updates... this might take a minute or two" screen (which then changes to telling me to pick another wifi network, but never completed checking for updates). Anyone know about this?
[Nexus 7 (2013) Android Development] followmsi:
dirty upgrade from classic 8.1 to classic 9.0 should work as well .. to be safe, take TWRP backup before.

Not sure about default NFC setting now .. just disable it via settings and kill "NFC Service" app, in case of battery drain.

As it looks like NFC drains less battery on AEX .. maybe some additional fixes are required for "classic" Aosp.
[Nexus 7 (2013) Android Development] followmsi:
Skip this step in setupwizard .. do updates later on.
[Nexus 7 (2013) Android Development] abhifx:
very nice, waiting for AEX to finally switch to fully working N7.
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.5 - May 2019

New month - new builds ..

AospExtended-v6.5-flo-20190508-1130-UNOFFICIAL.zip

AospExtended-v6.5-deb-20190508-1323-UNOFFICIAL.zip

Changes:

- Google security updates -> May 2019

- AEX update to v6.5 -> https://blog.aospextended.com/AospExtended-v6.5-Changelog/

- Enabled NFC - pls see below

- Switched Sensor wrapper (may improve deep sleep)

- minor changes

Tested flo version with Magisk 19.1 !

NFC:

Since Oreo NFC was crashing all the time .. you could not even enable it.

At this point I did "hide" NFC from settings menu completely.

These days I was looking again .. and used a new prebuilt lib to "solve" the problem.

Now NFC starts and I was able to make a quick beam test with another device.

Not even sure if it's "fully" working, needs more testing.

Unfortunately NFC still drains battery like hell !

For this reason I do recommend to switch it off, until it's "fully" fixed.

For the System repartitioning / Opengapps: Error 70 topic pls have a look on the first page.

Enjoy :p
[Nexus 7 (2013) Android Development] JT1510365:
Unfortunately I cannot get this rom to get past the setup wizard on my flo I eventually did get past it by skipping the setup wizard but now I get a constant notification telling me that android setup has a problem with google play services. The notification stays stuck on preparing updates and there is no way to remove the notification completely. Android setup is constantly running in the background and there is no way to stop it. Do you have any idea why this is happening I don't have problems with other ROMs just this one. Any help would be greatly appreciated. Why did google mess up android pie so badly with this android setup bullcrap doesn't make any sense in my opinion this was never an issue with nougat or oreo
[Nexus 7 (2013) Android Development] elpeh:
AospExtended-v6.5-deb-20190508-1323-UNOFFICIAL: should compass work

Hello,

thanks, again, for your work.

Did "dirty flash" from 20190420 on my deb device. What should be the status of compass function? If see the following strange behaviour. Activating the compass function with the compass button in Quick Settings seems to work: varying heading values are shown in real time within the icon, and the values seem to be very reasonable. But: as soon as I dismiss Quick Settings and reopen again, the button is disabled again.

Compass doesn't seem to work in e.g. Osmand.
[Nexus 7 (2013) Android Development] cpsycrow:
Hey. I have faced this a few times now, my solution is to force stop and then disable BOTH android setup wizard system apps (yes there are two)

For good measure i also did the following:

If you have Developer Options already unlocked and USB debugging enabled, then you’ll be able to use an adb method which is a guaranteed fix. If you don’t have USB debugging enabled and can’t access it, then you’ll have to try another method which is not guaranteed to work.

ADB Method
Open a command prompt or terminal window and enter the following:

adb shell
settings put global device_provisioned 1
Then wait for the command to complete. This took about 10 seconds for me.

settings put secure user_setup_complete 1

Cheers
[Nexus 7 (2013) Android Development] prsa01:
Flo, dirty flash 6.4 > 6.5. All as expected in early testing.

As always, thanks
[Nexus 7 (2013) Android Development] sir_bazz:
Had this problem with PE on another device, angler maybe?, and the fix was to set the wifi connection to unmetered.
[Nexus 7 (2013) Android Development] followmsi:
Tested flo version .. here I can switch on/off compass without problems ..several times thru quick settings.

Tested 3rd party compass apps .. all showing correct now.

Before 04/20 release compass (sensor) did not work at all.

Pls post log from deb when compass is failing .. do own flo device only.

Any other Deb users same compass problem ?
[Nexus 7 (2013) Android Development] followmsi:
My last "classic" clean install is some time ago ..

Do not skip (gapps) setupwizard completely.

Do not setup wifi .. except for time zone skip all steps in gapps setupwizard.

Do updates and other config once setupwizard finished.

If this is not working try the steps recommend by other users here in this thread.

Gapps setupwizard and "pure" aosp had always some kind of "issues" ..

Cheers
[Nexus 7 (2013) Android Development] elpeh:
Ok, it seems I misunderstood the AEX compass QS tile. It seems not to toggle the compass function, but to show the heading for some time - so it works as intended?

Compass/magnetic sensor is working now on deb, too. Tested compass apps, google maps.
[Nexus 7 (2013) Android Development] tinyturtles:
This new version of ROM installed without giving me the same issues in Gapps setup. I am facing only one real issue - after the tablet is sleeping, I will turn it on and the entire thing becomes unable to open apps, settings, etc. But I am able to reboot the tablet with no other issues, and then everything works again until a future time that it has been sleeping, is woken up, and becomes unresponsive again.

Otherwise great ROM! Most of the permanently-awake time is gone and now it is awake for a much more reasonable amount of time.
[Nexus 7 (2013) Android Development] curiousde2002:
I just found a "solution" for this by installing edxposed which basically gives you xposed framework on Pie.

With this the old KitKat module is working so Deb has capability to send USSD codes and use a dialer which is a must when using a prepaid simcard.

BUT it (I guess it's the framework) slows down the system, apps need more than twice the time to open and frequent reboots occur.

In other words it's useable but you won't enjoy it.:(

[MENTION=5480152]followmsi[/MENTION]:

Isn't it possible to incorporate these features in the ROM as in my opinion these are basic features for a device with a simcard?

Or maybe someone could make a flashable zip for this?

PS.:

After restoring my nandroid backup and reboot I installed the new 6.5 build and it's working great, battery life seems to be better than on 6.4.
[Nexus 7 (2013) Android Development] bitstra:
This problem with "device becoming unresponsive after deep sleep" on latest AEX update I've solved by

deactivating Digital Well-being.

My flo is running much better, since I deactivated DW...

I found a hint to the problems with Digital Well-being on an article about concerns of PIXEL3 users.
[Nexus 7 (2013) Android Development] Booroner:
Testing,ver y ver y tahnks
[Nexus 7 (2013) Android Development] followmsi:
As I do not own deb device myself it's kind of impossible to implement/change stuff like this.

Need to have logs .. testing .. checking if and when it was working before.. etc.

If you don't own the device yourself it's gonna be hard.

What about other deb users and USSD codes on Pie ?

Cheers
[Nexus 7 (2013) Android Development] Booroner:
Where that option is, this also happens to me, thank you
[Nexus 7 (2013) Android Development] tinyturtles:
Settings -> Digital Wellbeing. Click on the triple dot menu in the top right corner -> Turn off usage access.

Unfortunately, I tried it and this did not solve the freezing for me.
[Nexus 7 (2013) Android Development] adstraylight:
I just disabled the whole app, I didn't have the no response problem, but just wondered if it might give an incremental boost to performance. There doesn't seem to be any noticeable benefit, but neither is there any downside afaict.
[Nexus 7 (2013) Android Development] ReBat:
Thank you so much for making this version which is perfect for me! The soundproblems (crackles, lesser quality) which I encountered with other pi versions are solved with this classic version. I really appreciate your generous work!