yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] FemBlack:
Hey Guys ..

I am looking for testers for the new features ,which will be available for the next update..

New Features:

Select icon from any iconpack.

Select image from sdcard.

People who are interested pls contact me in this mail riazmohamedd@gmail.com
[Android Apps and Games] M1LL3R:
[MENTION=5219664]FemBlack[/MENTION], why I´am only able to joint 4 icon packs with the pro version?
[Android Apps and Games] FemBlack:
this feature will be available from the next version...
[Android Apps and Games] FemBlack:
Hey All.. Pushed the new update to the play-store.(02/10/2015)

★ Select icon from any iconpack.

★ Select icon from gallery/internal storage.

★ Added Italian, Portuguese, Polish, Russian translations
[Android Apps and Games] benjamminh:
I've paid for the pro and made a donation for the premium features but can only use the basic ones. What do I need to do?
[Android Apps and Games] aerifal:
Some icon pack are not selectable, e.g in advanced mode, when I trying to blend icon and choose "SELECT ICON FROM ICONPACK" it brings me to icon pack welcome screen.
[Android Apps and Games] FemBlack:
i think sterday i sent the mail pls check...
[Android Apps and Games] FemBlack:
some iconpacks are not created correctly for this icon picking funtion...
[Android Apps and Games] kettir:
Nice app! I've picked up on the pro version. I'd like to see a step by step (not a video please) of how to create both the advanced and the basic icon packs, including where the installed icon pack is stored and how to apply it.

Also, how to remove Icondy icon sets, I mean the ones that you create and maybe don't want to do anything more with them, and the ones you create and "install".

so far, to create a basic set I get this far:

Click the plus sign

select Basic Iconpack

provide a name

Select the iconpacks (up to 4, hopefully more in the future)

Click OK

select the default icon pack

(note: at this point after the icon pack is selected, the app doesn't do anything until you select your phone's back button. This is confusing.)

Select filter if you want to use one

Select default icon - I get a blank screen here. Not sure what this is for.

Blend icon packs - this screen is confusing because you get a list of all your icon packs. Experimentation showed me this is where you select an item and then determine its default icon, but there's nothing to tell the user that.

Now click the check sign and get "creating iconpack"

when it's done, click "install"

The installing screen appears

You can click Done, or Open

If you click open you select which launcher to use to apply the pack

You are asked if you want to apply the icon theme

Click OK

You are dropped back to a list of the icon packs on your device and nothing else happens

If you drop back to your main screen you can see the icon pack has been applied
[Android Apps and Games] CitizenX:
Really like this app, do you already know when we can use more than 4 icon packs?
[Android Apps and Games] fluffyrush:
Amazing

Amazing tool! :)
[Android Apps and Games] kettir:
Does anyone know where the newly created icon packs are saved? How do I delete one of the packs I have created with Icondy?
[Android Apps and Games] dej1i:
Icon preview

It would be nice if we could see a preview of the icons we are picking when combining more than 4 icon packs. Is this something you could do ?
[Android Apps and Games] glennsamuel32:
I just love this app !!!

Is there any way we could get a "Glow" filter too ?
[Android Apps and Games] i killed tupac:
I think this app is abandoned...I bought it and yeah, it doesn't work very well. It's like 3/4 assed at best. I like the idea, and it probably worked at some point, but warning to new buyers...don't
[Android Apps and Games] Jacob_R:
nice :good:
[Android Apps and Games] thecentury:
thanks for sharing :)
[Android Apps and Games] Thewest123:
Doesn't work on Xperia. Other icon packs work. Can you please add support/fix this?

Thanks ^^ I really like this idea.
[Android Apps and Games] hshah:
Bringing this back from the dead... is there anything similar out there?
[Android Apps and Games] yufanyufan:
try “Icon Pack Mixer”. The UI is much better.
[Android Apps and Games] hshah:
Just gave it a go... interesting functionality but not quite what I was after. I want to merge everything in all the packs I have, into one big one. That way when I go looking for a new icon for something, I only need to go to one place.

:)
[Android Apps and Games] nec947:
A promo code would be appreciated

I can translate your app to Persian/Farsi language instead.
[Android Apps and Games] x13igpoppa:
Is there anyway I could get the pro version of this app ?
[Android Apps and Games] MasterGamer1:
Google play link not working

No download possible
[Nexus 7 Original Development] Ziyan:
The Unlegacy Android Project​

Introduction

Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.

On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Nexus 7 (2012) include:

- Linux kernel 3.4.y (currently 3.4.113)

- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority

- F2FS support from kernel 4.9 (for /data only! no point of f2fs on /cache)

- SELinux in Enforcing mode

Installation

It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.

If you're planning to install GApps, be sure to read the second post!

Aside from these, installation and upgrading is no different than on other ROMs.

Problems

- We received some RIL bug reports on 3G variants - other than that, there are no known issues.

If you notice anything, be sure to report it in this thread. Stability is our main concern. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if we don't reply directly to them.

Downloads

See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds :)

We will have a built-in OTA updater (just like stock) soon (it's a work in progress) :)

Features?

There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.

As usual, feedback is appreciated :)

XDA:DevDB Information

Unlegacy Android Project, ROM for the Nexus 7

Contributors

Ziyan, sheffzor

Source Code: https://github.com/Unlegacy-Android

ROM OS Version: 7.x Nougat

Version Information

Status: Stable

Created 2015-06-07

Last Updated 2017-12-23
[Nexus 7 Original Development] Ziyan:
Reserved

GApps

If you want to install GApps, we recommend Open GApps Pico.

An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.

In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.

SafetyNet

The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!

Rooting

You can flash the latest Magisk to get rooted.
[Nexus 7 Original Development] anzi2001:
Yesss is it snappy? :eek:
[Nexus 7 Original Development] Ziyan:
I was able to workaround the panel errors in the kernel - PWM control isn't working for some reason, so I had to use an alternative method to enable backlight, meaning it's using a fixed brightness. This isn't important right now (I want the core functionality to work before making stuff bug-free). I also forward-ported the touchscreen driver, so it's mostly working now - it still needs some fixups for 3.4. My next goal: audio and video decoding.

View attachment 3350098

Kernel/common android-3.4 branch could be merged into the kernel after it's fixed up, which will surely make it more efficient.
[Nexus 7 Original Development] NeoPreacher:
great, i wish you very much success :fingers-crossed:
[Nexus 7 Original Development] Ziyan:
While I try to do my best to keep myself from working on this 24/7, I couldn't resist... and fixed camera, video encoding and decoding, and audio (party, just the rear speaker works yet) also works now :silly: what this means? Blobs won't stop us, as they work fine on 3.4 as well.
[Nexus 7 Original Development] anzi2001:
Man you really are doing the job man :D any way i can help? :eek: i want to help :D
[Nexus 7 Original Development] USBhost:
I'm so subscribing to this

I never thought we will get to

3.4
[Nexus 7 Original Development] SkOrPn:
Subbed for sure. Very good news here.
[Nexus 7 Original Development] Traediras:
Will definitely be keeping my eye on this one. :D
[Nexus 7 Original Development] Ziyan:
Today, I fixed sensors and panel PWM control (meaning brightness can be changed, auto-brightness works fine as well), and Bluetooth. Doing this alone requires a huge amount of time and work, as there's still a zillion thing to do, like merging in android-3.4, fixing up touchscreen (there are ghost touches and packet spams slowing down the kernel), fixing up suspend (need to press power button multiple times to wake up), audio, otg, etc...
[Nexus 7 Original Development] HTCDreamOn:
No one else has tried building this then?? I thought this thread would boom after all the excitement for 3.4 on the 3.1 bringup thread. Anyway, Ziyanns just helped me fix this booting for both pcbs now so it should boot for everyone.
[Nexus 7 Original Development] Ophidian_DarkCore:
do you happen to have an img for testing?
[Nexus 7 Original Development] HTCDreamOn:
No, you need to hardcode your pcbid and projectid into board-grouper-misc.c atm which you can get from last kmsg (just grep for those things when catting a kmsg in adb shell).
[Nexus 7 Original Development] anzi2001:
Can i help somehow? :eek: i want to help lol :D
[Nexus 7 Original Development] fra9090:
I want to help too ! :)
[Nexus 7 Original Development] 19dragon98:
I tried to build (img) but without success...As you said on a recent post you cannot build .img but you need to to hardcode your pcbid and projectid into board-grouper-misc.c but i dont know how to do it :S
[Nexus 7 Original Development] espaciosalter20:
i will subscribe to this thread, just to see how it goes...
[Nexus 7 Original Development] Indha Lezzio:
It was a long time since i was not so excited in xda
[Nexus 7 Original Development] nruri:
Looking forward to this!
[Nexus 7 Original Development] aquavalanche:
well, I'll be happy to test it after you release it [emoji14]. Keep up the good work mate! [emoji3]
[Nexus 7 Original Development] dex2grigg:
Im Confused, why the hype for this kernel!?
[Nexus 7 Original Development] NeoPreacher:
Because it's a big upgrade, it's 3.4

Gesendet von meinem Moto G mit Tapatalk
[Nexus 7 Original Development] notsotelia:
Hope the finals went well, if you are already over it.

I really wish this project the best, you know samsung is not the only device which needs some love :p .

Don't get me wrong, i'm not demanding anything, i'm just really excited to test out your work, since it looks very promising.
[Nexus 7 Original Development] Ziyan:
I have decided to open-source the kernel trees again, hoping some developers will respect our work this time (and maybe actually help us). As a bonus, I have also uploaded an AOSP 6.0.1 ROM with this kernel and the necessary userspace changes included. Speaking about userspace, check out the repos at the Grouper-AOSP project - a lot have changed, including the removal of several ugly workarounds previously needed for M. As an extra gift, everything needed to build M with 3.4 is included in that org - simply init the repo with the aosp-6.0 branch (using the platform_manifest repo url), and you're good to go to build exactly the same ROM I uploaded :) but please, if someone decides to release a kang or something, please give us some credits by at least including our nicks and this thread in the op (hopefully, after looking at the commit history of the kernel, everybody will notice the vast amount of time spent with this). I'd rather not see 3.4 included in ROMs yet - extra flashable zips are OK (until this is proven to be stable enough for general usage). If someone claims this as his own work or something, I won't hesitate to make the sources private again - I hope everyone will understand this situation after spending a couple hundred hours working on this stuff.

Alright, the current kernel bugs are listed here (this is the "main" kernel repo, the Groper-AOSP project includes a recent mirror of this), plus in the uploaded ROM:

- tricky audio playback (I believe other M roms had this issue in the past, but I'm really not sure if it's the same issue with no sound after boot, also the left and right channels are swapped - I'll investigate it in the future)

- DRM not working (should be easy to fix later)

- possibly other minor issues, report them here in the thread

A couple notes: this is a pure AOSP rom, as of now, there are no plans to include extra features. It's also not optimized to be "snappy" - there is no zRAM and other stuff in here, which should greatly improve memory management with 3.4, but for now, our plan is to make this thing fully working and stable. A couple drivers were replaced or rewritten, so there might be some minor issues remaining. And to be honest, I don't know anything about the performance compared to 3.1, so reports about it are welcome - there's still room for improvements, like disabling some extra debugging that might be present in 3.4.

I would be happy if all the discussion about this were kept here - I only want to hear about bug reports when using my unmodified uploads, not about bug reports with even more unstable kangs :)
[Nexus 7 Original Development] Bert98:
Maybe a dumb question, but where can I download the ROM?:D

Inviato utilizzando XDA One
[Nexus 7 Original Development] Ziyan:
Check the downloads section on the top of the page :)
[Nexus 7 Original Development] Bert98:
Oh alright I was on mobile haha thanks :good:

Inviato utilizzando XDA One
[Nexus 7 Original Development] tomskra:
Sorry for maybe silly question, but: I flash the ROM in TWRP, then I flash Gapps. And when tablet boot, I haven't got any google app. I want to flash Gapps again, but I lost TWRP, now I have stock recovery. How can I flash Gapps? Thanks for reply.

PS: But the speed of tablet is amyzing. Thank you very much for this kernel and ROM
[Nexus 7 Original Development] joaopaulo_:
After Flash rom reboot in recovery mode (back to main menu of twrp then reboot>recovery) then flash gapps.

Only notifications sounds is working for me. And google play services are forcing close after first boot (after set all permission on its working)
[Nexus 7 Original Development] KawaiiAurora:
Will there be a flashable 3.4 kernel zip for cyanogenmod 13? Thanks! ^^
[Nexus 7 Original Development] tomskra:
Has someone working USB-OTG in new ROM with this kernel 3.4 ?? And another question: How can I disable AutoRotate?? Sometimes I want use tablet only in Portrait mode (f.e. in bed).
[Nexus 7 Original Development] iwjosi:
Rotation lock not working, I hope you can fix it
[Nexus 7 Original Development] Bert98:
Audio is not workin, either.. But damn it's smooth :D

Inviato utilizzando XDA One
[Nexus 7 Original Development] dareino:
anyone noticing super slow charging on a/c?....hopefully it drains super slow too!

d
[Nexus 7 Original Development] Ziyan:
I think OTG just needs userspace changes, as the kernel correctly recognizes OTG devices when attached. About the rotation lock, it's one odd issue - I don't think it has anything to do with the kernel, but what the hell broke it then? I'll need to review the userspace changes...

Sounds like an SMB347 driver issue, as we switched to the upstream driver instead of using the hacked together driver from 3.1. I think it sets the wrong charging current limits.

Unfortunately, I won't really have time until next weekend to look at these :(
[Nexus 7 Original Development] mn.code:
My observations so far:

- Audio is working for notifications, but not for media (for example if you receive an email you will hear the notification, but if you go to youtube and play a video, you won't)

- OTG - not powering an external device, as I don't have an Y cable at the moment, can't test this further

- Charging is ok for me, I am using genuine Samsung 2A charger

- Network location doesn't seem to be working, haven't had the time to test GPS only though

- Overall performance is much better than 3.1
[Nexus 7 Original Development] chall32:
Would this fix the audio prob: https://github.com/danielhk/android_device_asus_grouper/commit/3e7e50467f2534c48d633af5cf91b18c99cf3b40 ?

As spotted on the CM13 thread: http://xdaforums.com/showpost.php?p=65250363&postcount=211 :)
[Nexus 7 Original Development] sheffzor:
Tanks for the tip, I'll test it and if it works I will release the updated build for grouper and the missing one for tilapia!

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] sheffzor:
That change doesn't solve the audio problem, I will have to look deeply into the code to check what is happening.

btw, I attached the tilapia build to the downloads section, so tilapia users can have a taste of aosp 6.0 with 3.4 :D:cool:
[Nexus 7 Original Development] sheffzor:
I already got the problem on audio, until we release a new build, you guys can workaround doing the following:

Go to Settings->Sound & notification->OtherSounds->Dock speaker plays->SET TO "ALL AUDIO":good::good:
[Nexus 7 Original Development] Bert98:
Oh my god it works, you're AWESOME :D

Inviato utilizzando XDA One
[Nexus 7 Original Development] tomskra:
Has anyone tip how to get root on this ROM? I tried to flash "BETA-SuperSU-v2.52.zip" through TWRP 3.0, but then tablet doesn't boot anymore. I had to flash ROM again.

Odesláno z mého Nexus 7 pomocí Tapatalk
[Nexus 7 Original Development] dareino:
I flashed 2.67....all good

d
[Nexus 7 Original Development] aquavalanche:
okay, so here's what I experienced while using this ROM & kernel in a short time.

1. smoother experience than 3.1. I feel many operation complete with less delay than 3.1 (I used twisted 5.1 + M-kernel before)

2. rotation lock not working, system doesn't respect rotation setting. I think it should be system related, not kernel.

3. I haven't encountered (or I should say noticed) any bug in my casual usage (reading news, browsing, media playing), aside from point 2.

And this is a bit of OOT

4. I think I installed the gapps in a wrong way, as I needed to set the permission manually and as the result, I didn't have the setup wizard.

5. installed clock app forced close on me. I have to switch to Google clock app.

Overall experience : I am quite happy with current version [emoji4]. I think I will use this one as my daily driver. cheers for all devs working on this kernel (and ROM)!! [emoji106] [emoji106]
[Nexus 7 Original Development] tomskra:
Thanks. "BETA-SuperSU-v2.67-20160121175247.zip" works correctly :)

Odesláno z mého Nexus 7 pomocí Tapatalk
[Nexus 7 Original Development] everesee:
Am I the only one who gets "Google Play Services Stopped" error again and again? I flashed open gapps 6.0 micro for testing.

Any recommendations for working gapps if the ROM supports it?
[Nexus 7 Original Development] sheffzor:
You should flash gapps before the first boot, then you will get a few FC because of permissions on setupwizard. Since we are using the pure aosp, it doesnt have the permissions for gapps in the framework, we will add them later.

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] everesee:
My steps was;

-Enter Recovery

-Full Wipe

-Flash ROM

-Flash Gapps

-Reboot

So I flashed gapps before the boot. I don't know what's wrong with my device :/
[Nexus 7 Original Development] sheffzor:
Did you complete the setup wizard?

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] everesee:
Yes.

At the setup wizard, my device gave some "play services stopped working" errors randomly. After the setup wizard, google play store failed to download any app and Google Now Launcher couldn't work due to errors.

My Gapps File: open_gapps-arm-6.0-pico-20160215
[Nexus 7 Original Development] sheffzor:
Check if you have all the permissions enabled for the Google Play Services app.

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] everesee:
Permissions fixed the problem! Thank you

Finally I can test the kernel :)

If anyone needs help with that problem; http://www.ibtimes.co.uk/android-6-...oogle-play-services-force-close-error-1524431
[Nexus 7 Original Development] biondi53:
I'm getting a black screen after google logo..... I tried with TWRP 2.8.7/3.0.0, with different gapps, without gapps, with system mount/unmount, MD5 OK... and no way : /
[Nexus 7 Original Development] KawaiiAurora:
Just in case, make sure you're using all ext4 partitons. You might need to update your bootloader to the latest version since I had this problem even in the Android 4.3 days
[Nexus 7 Original Development] biondi53:
the latest version is 4.23? I have that
[Nexus 7 Original Development] namerke:
[MENTION=4619263]sheffzor[/MENTION] [MENTION=2633638]Ziyan[/MENTION]

Great news on releasing test builds to the public, I'm facing some issues with the usb/charging module on the hardware side (the typical nexus hardware bug), but i'll help with the testing once I receive my order of spare parts.

Have you guys considered Opengapps for gapps usage ? It seems like a decent package, but needs some modification/commits on rom side on android 6.0 + (link for details)

Anyway, thank for your hard work, you guys are awesome. :good:
[Nexus 7 Original Development] KawaiiAurora:
Yep.. Do other MM roms boot? If yes, maybe your N7 mobo isn't supported for some reason by the kernel..
[Nexus 7 Original Development] sheffzor:
We know that we have to do changes on framework permissions to support opengapps, we just haven't made them because our focus is on the kernel and userspace, so we give the chance to other devs and ROMs put their hands on this work base and fine tune it.

Sent from my OPO

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

Can you get us a lastkmsg from twrp?

Sent from my OPO
[Nexus 7 Original Development] biondi53:
Yes, but never with kernel 3.4.... : / testing a version of vocoderism MM rom with 3.4 I had a soft brick....
[Nexus 7 Original Development] NeoPreacher:
You need to save log. Not screenshot
[Nexus 7 Original Development] sheffzor:
Do the following after flash the ROM:

- Power off the device;

- Power on (and let it go to the brick place);

- Press power off until it resets;

- Just after it resets, push VOL DOWN to go to bootloader;

- Boot to recovery;

- Go to the terminal and write this command: "cat /proc/last_kmsg > /sdcard/last_kmsg.log";

- Use the USB MTP connection to get the file from the tablet and post it here;

I must be in this order: BOOT ROM->BRICK STATE->RECOVERY->GET LAST_KMSG;
[Nexus 7 Original Development] biondi53:
Like this?