yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] curiousde2002:
Sending USSD codes on unmodified Deb has never been possible because Google in its never ending wisdom had decided not to enable this.

The module does exactly this as the dev describes it here [Xposed][MOD][Android 4.4+] SMS, USSD, tethering and native SIP for Nexus devices by makuser :

" I've created an Xposed module to give you a very simple and secure way to enable SMS, USSD and the native SIP dialing function on your Nexus 4, 5, 6, 7 2012 and 2013, 9, and 10. "

I don't know if and how I can provide logs for this.

I need to install edxposed again to get the module working but as it worked last time how do I get logs?

There was no malfunction only a very poor system performance.

Maybe you can have a look into the module to see how it works.

I have a Deb and would be happy testing it. :)

Thanks!
[Nexus 7 (2013) Android Development] followmsi:
For better understanding .. I will not work "remotely" on this problem.

Sorry, but your Deb device will not help in this case.

To prevent frustration for you and all the other Deb users .. I have extracted this apk and checked the code quickly.

For the next AEX build, most probably in June, I have added the "missing" values to Deb device tree now ..

https://github.com/followmsi/android_device_asus_deb/commit/f19b4bab4d4556e3f993c92f7f885a5658126433

Not sure if this will improve .. we will see next month.

Are you the only DEB user with this problem ? .. still waiting for some more replys on this topic. :)

Cheers
[Nexus 7 (2013) Android Development] curiousde2002:
Maybe I'm the only one who's really missing this feature.:)

Tethering and SMS had always worked for me also without this module, I think this is something provider specific especially in the US.

Thank you very much any way !
[Nexus 7 (2013) Android Development] sir_bazz:
Haven't had to use USSD in years, so can't test or confirm the issue or not.

SMS works fine though, as does calling via Google Voice.

Probably not helpful but thought I'd share incase it helps anyone else.
[Nexus 7 (2013) Android Development] tinyturtles:
How's battery life doing for other folks? My tablet isn't awake 24/7 anymore, but reports Google Play Services and Nova launcher using sensors (not sure how to isolate which ones specifically) the whole time. Not sure how to fix it... Already tried resetting the data of both, but it comes back later anyway.
[Nexus 7 (2013) Android Development] Booroner:
All stock, the battery is now fine for me, previous compilations spent a lot of battery.
[Nexus 7 (2013) Android Development] Ruggerxpunk:
I'm sorry this post isn't technically on topic, but this thread seems to be the most active, and where I'm likely to get the best answer.

I unlocked and rooted my personal Nexus 7 (2013) back in 2013.

Now I need to do the same to my father's Nexus 7 (2013), but the link to the Toolbox no longer works:

http://www.wugfresh.com/nrt/

Is anyone able to point me in the right direction for what I can do to:

Unlock bootloader

Flash TWRP

Thanks, I kind of promised him I'd fix his Stock N7 (2013), but now the tools I would normally use no longer seem to be available.

Thanks again!
[Nexus 7 (2013) Android Development] ripee:
Link still works: NRT_v2.1.9.sfx.exe

Or if you prefer doing it via the command line: Unlocking the Nexus 7 (2013) Bootloader
[Nexus 7 (2013) Android Development] yourrealking:
Switched from Lineage. This ROM is good, but I have two questions.

(1) Where is "volume button reorientation"? I mean, I want the volume up/down button to switch in landscape mode . Lineage OS has this feature. Is it not available in this ROM?

(2) The "rotation confirmation" button on the Navigation Bar is displayed at a wrong position, between the Home and the Recent button. Is there any way to fix this?
[Nexus 7 (2013) Android Development] sdv1973:
There are disapiring all panels. Help
[Nexus 7 (2013) Android Development] drewski_1:
More info? Not sure what panels you're referring to.
[Nexus 7 (2013) Android Development] dealpapa1:
twrp-3.3.1-0-flo.img	8.8M	2019-05-19 16:27:52 EDT

https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img.html
[Nexus 7 (2013) Android Development] Booroner:
Sorry, he finished twrp for DEB ??? Thanks.
[Nexus 7 (2013) Android Development] ripee:
Replace flo with deb in that link to get twrp for deb.
[Nexus 7 (2013) Android Development] Booroner:
If I have understood it, I only have to download that file and then modify the name, removing FLO and putting DEB ?????

Sorry and thanks.
[Nexus 7 (2013) Android Development] n3kf:
No, this....

twrp-3.3.1-0-deb.img

Download using that as a link

Change the flo to deb in the link above and you will get that file above.

https://dl.twrp.me/deb/twrp-3.3.1-0-deb.img.html
[Nexus 7 (2013) Android Development] ripee:
No. remove FLO and put DEB in the link, not the file!
[Nexus 7 (2013) Android Development] followmsi:
Yes, If you use the Update.zip versions .. as we have "fixed" ramdisk from "old" 7.1.1

This was the reason I would like to go for the kernel flasher versions. ;)

They should still work.

Have a look here ..

https://github.com/followmsi/mkbootimg_tools

Using this tool you can extract new ramdisk and combine it with the kernel binary you like. Just extract the boot.img and repack ..

Untill now they are no kernel updates available ... If they are online, I will compile new versions.

But for now we will keep EX inside the ROM.

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

Have a look here ...

https://xdaforums.com/showpost.php?p=71740178&postcount=267

You can also mount system (RW) and type:

echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop

in TWRP terminal. This will allow you to bypass the SetupWizard altogether on a clean flash.

As it looks like the gapps team is working on an replacement SetupWizard for 7.1.2 ..

Cheers
[Nexus 7 (2013) Android Development] TechnicsKuzya:
OK, thx for the info. The kernel flasher versions - normal boot, but the "config mix" bug still here.
[Nexus 7 (2013) Android Development] followmsi:
Not much more information .. :)

If we would know at least the names of the files we maybe able to determine the origin.

But what is your actual problem ? .. waste of 60 MB on your storage ?

Drop the files .. dalvik / cache will not break your system - it may increase your booting time.

As well I don't use Titanium backup .. can't help you better on this topic.

You may ask inside TB forum for more information.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Did you install official kernel installers as well ?

Here are all the settings / values like expected ?

We have no rush to get other kernels running on stock AOSP ramdisk .. we need to clarify the issues first.
[Nexus 7 (2013) Android Development] ZakSeven:
This process is pretty much obsolete since Android 5. Even more now that 7 use a new method to pre-compile and optimize our apps. Because of these changes titanium backup will always find stuff in Dalvik it thinks is unused as the optimization may be dormant until a proper time to resume.

There's no harm in cleaning it, but you would expect the OS to restart or resume what it was doing at some point or on your next reboot. Which may even be slower since you wiped items in process. https://en.wikipedia.org/wiki/Android_Runtime

Also Titanium backup last update to this process is from version v3.5.7 according to their change log, so basically when it was relevant. Current version is 8. Still an excellent program for backup but trying to play around with Dalvik these days are really not needed.

Zak
[Nexus 7 (2013) Android Development] drewski_1:
Most kernel threads I've followed have recommendations to reflash Stock boot.img before changing custom kernels to avoid issues with remnants left in the ramdisk.
[Nexus 7 (2013) Android Development] followmsi:
Yes, if you use official installer which is modifying the ramdisk.

But again .. here we not modify the ramdisk.
[Nexus 7 (2013) Android Development] TechnicsKuzya:
May be we can clean (delete some config folders/files) ramdisk with script before flash custom?

At the last ROM I flash extracted boot.img then custom kernel (anykernel2) - now it work, but need test more....

---------- Post added at 09:06 AM ---------- Previous post was at 09:00 AM ----------

Still in test... I want to find what config files need to be delete or restore from stock at the ramdrive before flash "anykernel2" zip.
[Nexus 7 (2013) Android Development] followmsi:
This depends on the custom kernel ..

You need to look into the custom kernel installer.. check the scripts. Etc.

Maybe one custom kernel uses config file called A the other custom kernel is may using a file called B ;)

For me the system is "OK" If I can boot it with AOSP ramdisk. :)

This is possible with all kernels except glitch kernel.

Glitch knows it and we may find a solution at some point.

Without using the custom scripts or tools like EX manager I guess we will always have some different "values/settings".

Still hope to find an "acceptable" way for using custom kernels in this ROM ;)
[Nexus 7 (2013) Android Development] TechnicsKuzya:
May be this help: How to extract kernel configuration from android kernel or boot.img and build related kernel for the device

.
[Nexus 7 (2013) Android Development] followmsi:
We know how to build a kernel .. :)

We have all the configs available on GitHub.

No need to extract them ..

As well we have built the kernel binary already.

You can not change a built kernel binary again you just "feed" the kernel values by scripts.

But we don't know where the "mixed" values are coming.

Here is a just part of the elementalx script .. is cleaning glitch stuff too ;)

Adding files to system .. etc.

Code:

ui_print("Cleaning up");

delete("/system/etc/init.d/99elementalx");

delete("/system/etc/init.d/99elementalx~");

delete("/system/etc/init.d/99glitch");

delete("/system/etc/init.d/99glitch~");

delete("/system/etc/elementalx.conf");

delete("/system/etc/init.d/99zram.sh");

delete("/system/lib/modules/cpufreq_limit.ko");

delete("/system/bin/thermald");

set_perm(0, 0, 0777, "/tmp/systemcheck.sh");

run_program("/tmp/systemcheck.sh");

ui_print("Installing system files");

package_extract_dir("system", "/system");

set_perm_recursive(0, 2000, 0755, 0755, "/system/bin/mpdecision");

set_perm_recursive(0, 2000, 0755, 0755, "/system/bin/thermald.bak");

set_progress(0.4);

ui_print("Creating config...");

set_perm(0, 0, 0777, "/tmp/buildconfig.sh");

run_program("/tmp/buildconfig.sh");

set_progress(0.5);

package_extract_dir("boot", "/tmp");

set_perm(0, 0, 0777, "/tmp/max_oc.sh");

set_perm(0, 0, 0777, "/tmp/edit_ramdisk.sh");

set_perm(0, 0, 0777, "/tmp/abootimg");

run_program("/tmp/busybox", "dd", "if=/dev/block/mmcblk0p14", "of=/tmp/boot.img");

run_program("/tmp/abootimg", "-x", "/tmp/boot.img", "/tmp/bootimg.cfg", "/tmp/zImage", "/tmp/initrd.img");

run_program("/tmp/max_oc.sh");

run_program("/tmp/edit_ramdisk.sh");

run_program("/tmp/abootimg", "-u", "/tmp/boot.img", "-f", "/tmp/cmdline.cfg", "-k", "/tmp/elex.zImage", "-r", "/tmp/initrd.img");

set_progress(0.8);

ui_print("@Installing Kernel");

run_program("/tmp/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p14");

As said before, have talked to glitch and he does not know why his kernel is looping on stock AOSP.

You can always use the current boot.img from the ROM and apply it via TWRP first, and then flash an official custom kernel afterwards.

(Don't forget supersu this way)

Cheers
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Yes, this is my way now - it gives a stable result.
[Nexus 7 (2013) Android Development] drewski_1:
The ramdisk is not modified during the install, but it's probably something that happens during use after-install that is causing the carry-over effects.

---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------

+1 but still need followmsi versions to handle F2FS?
[Nexus 7 (2013) Android Development] followmsi:
The kernels I have compiled all support F2FS .. still use it myself for cache and data.

Not sure about the current config in the official packages.

Most configs I have seen does support F2FS by default.

Cheers
[Nexus 7 (2013) Android Development] drewski_1:
:good: so glad you picked up the N7 dev for this! :victory:
[Nexus 7 (2013) Android Development] followmsi:
Today we have a "technical" release :)

AOSP_7.1.2_r2_N2G47E_flo-ota-eng.followmsi-v2.zip

AOSP_7.1.2_r2_N2G47E_deb-ota-eng.followmsi-v2.zip

The previous ROMs were still based on a "handmade" default.xml from nbehary.

We always used a fixed list of approx. 480 packages from google/github for this ROM .. also for 7.1.2.

If the AOSP releases will include more or less packages we will not recognize this way.

Only by doing ongoing manual checks - which I don't like. ;)

For this build today we go now for the "full" AOSP package list - given by google.

Now we have 533 packages synced from google/github.

The ROM size has been increased as well.

All the required stuff for flo/deb has been moved into a new local_manifest -> "roomservice.xml"

https://github.com/followmsi/manifests/blob/flo-deb-aosp-nougat/local_manifests/roomservice.xml

This way we have much more control over future builds .. at least for me :)

As well I have added "stlport" even it's seems not to be required for this ROM anyway.

Pls install and test v2 !

Cheers
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks MSI....?
[Nexus 7 (2013) Android Development] rajsris:
Dirty flashed new rom version plus SuperSU, then wiped cache and dalvik. Rebooted and everything came back fine!
[Nexus 7 (2013) Android Development] Coronado is dead:
Tried searching, but has anyone had issues with the home and recent apps buttons not working?

Clean install of rom, gapps micro, and SuoerSU.

Thanks!
[Nexus 7 (2013) Android Development] Booroner:
Perfect, thank you very much!!!!
[Nexus 7 (2013) Android Development] JT1510365:
No just search twrp deb on google and you will find it easily

Edit: never mind I didn't see until now that other people have already answered your question
[Nexus 7 (2013) Android Development] mickey36736:
Installed on my deb with gapps nano after I replaced the screen and it's work great. Better idle drain than stock rom.

Installed elementalX-7.02 kernel for tweaking cpu voltage and enable zram.

Many thanks for the rom. :)
[Nexus 7 (2013) Android Development] dealpapa1:
June 2019 Android Security Update Goes Live for Pixel Devices
[Nexus 7 (2013) Android Development] followmsi:
New AEX builds will come in the next days .. depends on AEX team.

There will be no "classic" version this month.

Due to holiday season the July AEX builds will be delayed.

Enjoy the summer :p
[Nexus 7 (2013) Android Development] dealpapa1:
god does not need vacation :laugh:
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.5 - June 2019

The DEB users should test tethering and sending USSD codes ..

AEX gets bigger and we have less free space in system.img !

Especially DEB device has reached the limit. The build stopped due to missing space left in system.img.

Unlike to PixelExpierence we still use "stock" partition size (840MB System/560MB Cache) for building AEX ROM.

We may switch to "big" system partition layout (1280MB System/120MB Cache) for the next builds.

Should we integrate minimal gapps package too ?

AospExtended-v6.5-flo-20190609-0844-UNOFFICIAL.zip

AospExtended-v6.5-deb-20190609-1144-UNOFFICIAL.zip

Changes:

- Google security updates -> June 2019

- Changes for tethering -> needs testing ! (DEB only)

Tested flo version with Magisk 19.3 !

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

Due to holiday season the July builds will be delayed !

Enjoy the summer :p
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.5 - June 2019 - GAPPS edition

As I want to test GAPPS integration on AEX myself I made one more ROM ..

Not sure about regular GAPPS builds .. the builds are for testing if gapps integration works fine on AEX.

Pls check for correct time-stamp and bigger size to determine the GAPPS verison in gdrive folder ..

AospExtended-v6.5-flo-20190609-1614-UNOFFICIAL.zip

AospExtended-v6.5-deb-20190609-1741-UNOFFICIAL.zip

Changes:

- GAPPS packages from AEX GitLab (minimal version)

Due to holiday season the July builds will be delayed !

Enjoy the summer :p
[Nexus 7 (2013) Android Development] ipdev:
I'm not a big fan of GApps integration.

It's one of the reasons I do not normally use roms like Pixel Experience.

Personally I like light roms. AEX is a nice blend between AOSP and Lineage.

AEX integrated gapps into the official build on Pocophone awhile back.

The maintainer ended up releasing an unofficial build without gapps with every update.

Now there are two official builds for Poco are with or without gapps.

General.

Apps baked into the rom may cause a problem when updated.

Take AdAway for example, it used to be part of cm, aex and others.

GApps.

Google updates at least one a month, day, hour.

Depending on your account, sometimes you do not get the newest version, so Google Updates actually downgrades you.

Yeah I've had it happen. My testing account(s) and personal account do differ.

My main testing account is signed up for Google Beta(s) so regardless what Gapps I install into system, most are updated right after I sign into Google.

I try to use the most minimal system install of GApps.

Sorry the long post. :o
[Nexus 7 (2013) Android Development] followmsi:
Yes, it's not automatically an advantage to integrate gapps into rom.

Not clear yet if there will be more gapps integrated AEX builds at all.

For now It's a test build .. as I had to extend partition size anyway.
[Nexus 7 (2013) Android Development] underflash:
GAPPS integration into ROM would "save" from a separate GAPPS download and a single sideload comand? More complex stuff, potentially more problems.
[Nexus 7 (2013) Android Development] curiousde2002:
:rolleyes:

Sending USSD codes does not work, I also tried with Google phone installed.

But if it worked you would not need to install a dialer anyway.

You could send the USSD code right out of a fake contact with the USSD code as it's phone number.

I've not tested tethering yet but this has always worked on my Deb.

But thanks for your great work!
[Nexus 7 (2013) Android Development] Booroner:
As for the drummer's note more than the previous compilation, I made a clean installation.

Very tahnks [MENTION=5480152]followmsi[/MENTION]
[Nexus 7 (2013) Android Development] followmsi:
Pls make logcat .. boot up and start to send USSD code via contacts app .. repeat a few times for the logs.

Try with Google dialer too .. a few times and log it too.

Thx.
[Nexus 7 (2013) Android Development] followmsi:
Yes .. saves additional gapps download and installation.

Just have a try yourself .. wipe system and install gapps version from above.

Do not wipe data .. just wipe cache/davilk as last installation step.

But as said above .. not sure about more gapps "integrated" AEX builds in the future.

Cheers
[Nexus 7 (2013) Android Development] curiousde2002:
There is never any visible reaction when sending the USSD codes so I hope the logs can tell you more.

Thanks!
[Nexus 7 (2013) Android Development] spocoeric:
I've run into a frustrating problem on the latest non-GAPPS build on my deb. No matter what settings I change, the temperature units on the at a glance home screen and lock screen are stuck on Celsius. Am I missing something obvious or is this a bug?
[Nexus 7 (2013) Android Development] Alfordr:
Hello !

I'm having some problem with the sysrepart_1280_120.zip scrip, show missing tool! status 11 and abort, does anyone knows why this is happening and what I can do to solve it?
[Nexus 7 (2013) Android Development] theistus:
Question: if we've already repartitioned using the old 1140/260 script, can we use the 1280/120 script with no problem, or would we need to undo the first repartitioning first?
[Nexus 7 (2013) Android Development] prsa01:
Yes, I did exactly this back when they each were first posted. No problems

No problem going from the smaller to the larger for me
[Nexus 7 (2013) Android Development] theistus:
Went ahead and have it a try, no problems, in case anyone else has the same question
[Nexus 7 (2013) Android Development] L.F.B.:
Hi, I want to move on from RR pie... I think the dev is not updating anymore...

And because of Master folownsi is this rom developer?

This AEX rom come with the exkernel from this thread?
[Nexus 7 (2013) Android Development] Hazzuma:
Pie

I am using now 8.1.0,since months,works fine,,Is to safe now to upgrade to pie 9,wz ur file,,,for my nexus 7، 2013 , noticed some telling about unworking WiFi at pie 9 !!!
[Nexus 7 (2013) Android Development] yourrealking:
The in-built launcher's icons look blurry. I have tried other sizes like +20 but all looked blurry compared to Nova launcher.
[Nexus 7 (2013) Android Development] v12xke:
It's not baked in, but there is an ex kernel for pie in the rom download folder. I've used it on the past few aex builds. you can also search this thread for more kernel discussion.
[Nexus 7 (2013) Android Development] L.F.B.:
Ive just flashed this rom and Its the best for this device!

Just a little laggish but with the exkernel gpu overclock this rom gets so smooth! Amazing!

Great job of our Master dev [MENTION=5480152]followmsi[/MENTION]???
[Nexus 7 (2013) Android Development] followmsi:
Checked your log files .. but I did not find the culprit.

As said before .. will be tough if you don't own the device yourself.

Maybe at some point we find a fix for sending USSD codes on deb device !

Sorry, no better news on this topc ..

Cheers
[Nexus 7 (2013) Android Development] followmsi:
AospExtended-v6.6 - July 2019

AospExtended-v6.6-flo-20190723-0811-UNOFFICIAL.zip

AospExtended-v6.6-deb-20190723-1014-UNOFFICIAL.zip

Changes:

- Google security updates -> July 2019

- Update to AEX 6.6 -> https://blog.aospextended.com/AospExtended-v6.6-Changelog/

Tested flo version with Magisk 19.2 !

Magisk 19.3 seems to have some Magisk Hide issues on certain devices.

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

Enjoy :p
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] thank you once again for your time and efforts.

I would like to have a link to a kernel that allows overclock of cpu/gpu.
[Nexus 7 (2013) Android Development] prsa01:
Flo dirty update, no issues

Thanks once again for maintaining this rom!

No problem with Flo dirty flash, gapps pico, pixel essentials magisk module.

Previously repartitioned using one of your scripts
[Nexus 7 (2013) Android Development] followmsi:
Pls use EX kernel manager to adjust CPU/GPU values ..

I just made one EX based kernel for Pie .. which has no special overclocking.

https://drive.google.com/drive/mobi...k92ZUdnTTg?usp=drive_open&sort=13&direction=a

Most of the stuff is part of "my" kernel too .. which is included in ROM.

Maybe there are some "custom" modules or tweaks for overclocking available .. I can't help you here.

Cheers
[Nexus 7 (2013) Android Development] Nomad1600:
Just switched from Unlegacy Android to AEX and so far so good. II'm letting the battery go through a few cycles before giving it too thorough a test (may also play with kernel speed) but seems very smooth and I like having a few more tweeking options than what UA offers . Thanks for bringing AEX back for the Nexus 7 2013!
[Nexus 7 (2013) Android Development] Nomad1600:
Question... is there something I can do to better center any of the AEX logo wallpapers when the tablet is in the landscape position? Its a minor thing, but when I set them using the Wallpaper control the logos are at the very bottom or even below the bottom of the screen. I'm guessing there is an easy fix I am missing. Thanks!!
[Nexus 7 (2013) Android Development] PIERCALD1:
I have problems of continuous disconnection of wifi and bluetooth. Are there possible fixes?