yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] smartyP:
yes, mine is set to wap.cingular.. i switched everything to use the MEdia Net connection (not the My ISP one) - which was already set to wap.cingular.. thanks for the suggestion though, i left it out of my list - if anything this can be a consolidated spot for common causes.

FYI, it actually started working on its own since my initial post (after not having worked all day).. the only things i have done tonight are the following:

1) did a send/receive via a WIFI connection on the gmail account

2) setup outlook 2007 on my PC and synched my contacts/notes/email

3) upgraded my radio from default .11 to .17 (perhaps .11 radio restricts proxy settings?) (*soft reset - may have played a role?)

i wish i had tested it between each of these steps, but i wasn't really doing these things to try and fix the gmail issue.. hopefully it will stay working :)
[Tilt, TyTN II, MDA Vario III General] snooginsguy:
Here's a silly question - had you tried simply soft-resetting the phone? I had the same problem for a bit, was absolutely driving me nuts, and all it took was a soft reset to get it to connect and work fine ever since. Maybe for future reference...
[Tilt, TyTN II, MDA Vario III General] smartyP:
not a silly question.. i had tried resetting somewhere amongst my attempts during the day with no avail, but obviously i reset during flashing the radio rom, so who knows, maybe that did play a factor.

all i know is it is still working today from work, so that is a big plus.
[Tilt, TyTN II, MDA Vario III General] smartyP:
try everything in the list, and try a soft reset as well.. if that doesn't do it you may want to try and update your radio rom to .17 since you are on .11 as i was..
[Tilt, TyTN II, MDA Vario III General] bpage08:
I had the same problem and had to enable SSL for incoming and outgoing mail under the advanced settings in the Outgoing mail server setup page. Once I did that everything has worked perfect since then.

Hope it solves your problem aswell.
[Tilt, TyTN II, MDA Vario III General] laakness:
I've never had an issue with Gmail and wap.cingular...except HTML messages still not working.

The SSL thing is most likely it. If you read google's instructions for setting up the account it clearly states that ssl with authentication has to be enabled.
[Tilt, TyTN II, MDA Vario III General] ercave1:
Gmail

For those having issues with Gmail, has anyone looked into Mobipush? This service allows you to use your device's Direct Push Technology to get your Gmail sent to your device in real-time. I had previously mentioned this in another thread. All you have to do is turn on POP or IMAP access in your Gmail settings and setup your device as per the instructions on Mobipush's site. I've been using the service and it seems to work great...and did I mention its free?

here's the link...

http://www.mobipush.com
[Tilt, TyTN II, MDA Vario III General] vwauditech:
I use Java for my Gmail account its very nice and fast with 3G. I have never tried setting it up on an account inthe built in Messaging App. I use Pocket MSN for my primary Hotmail account. Just download the Gmail IMAP software from Google and try it out and see what you think.

Kevin
[Tilt, TyTN II, MDA Vario III General] pizzaguy:
i had the same problem with bellsouth as my email provider when using outlook email but i got it to work on xpressmail - i still dont know what was wrong...
[Tilt, TyTN II, MDA Vario III General] lordshwa:
Same problem, I think

Gmail app loads and maybe 1kb comes down but then after a short time it errors saying that it needs a data connection and to look at the FAQ. This only started happening after upgrading to ATT ROM AKU 0.4.4. Worked on my stock ATT TILT no problems.
[Tilt, TyTN II, MDA Vario III General] jinks:
mobiPush looks good. I use Seven's extended beta. http://community.seven.com/forum/main.php They now support Gmail IMAP. It works great, and I like how it fixes Gmail's imap problems. I'll have to check out mobiPush to compare the two.
[Tilt, TyTN II, MDA Vario III General] TitsMagee:
Funny, I was able to get G-mail to work fine on my first Tilt and I got the new one (red light of death issue) and now my G-mail won't work...:(:(
[Tilt, TyTN II, MDA Vario III General] AllTheWay:
Gmail IMAP software? Do you happen to have a link for that!
[Tilt, TyTN II, MDA Vario III General] mdemirha:
http://www.google.com/mobile/mail/index.html
[Tilt, TyTN II, MDA Vario III General] wiggy9906:
I had same problem "Error Synchronizing" - "Cannot connect with current connection settings"." - Problem is activesync getting in a twist. Go into connection manager and turn off activesync, or connect to PC and then disconnect.

Wiggy
[Tilt, TyTN II, MDA Vario III General] vwauditech:
Tried setting up gmail in Messaging App

I tried to set up my gmail account too, just to see. I set up gmail pop3 at gmail settings. I went through messaging App and set up incoming with

pop.gmail.com:995 and outgoing smtp.gmail.com:465 Nothing seemed to work, says unable to connect with current settings. A few have already said that it worked fine under their messaging app. What settings are you using if you have it working? Please post your incoming and outgoing settings please.

Thanks, Kevin
[Tilt, TyTN II, MDA Vario III General] JangoSolo:
I had this when I upgraded to Dutty's new rom, and I was panicking like mad. I tried everything - but nothing worked apart from wifi sync - so I went to bed. When I got up I tried to sync and worked right away...

So I dunno if you've been hard at work at this non stop - best thing to do is seemingly to let it settle, same thing happened for me when I upgraded again to V3 Dutty's (which is awesome by the way) - gmail started working after a little while (this time I did nothing)
[Huawei P9 Lite Questions & Answers] loginroman:
Guys, doing a rollback with nougats .. everything is fixed in place according to the instructions ... it was loaded on the stock approx. After blocked the bootloader itself through the HUAWEI Multi-Tool by the Team MT loader ... Well, here it got the inscription: Exclamation mark - your device has failed verification well, and 3 options for the standard action .. Everything is written in red. Below White: Your device is booting now ... this way the download is endless. I could not turn it off - restart with double vibration. It does not respond to any variants of the holding of the buttons. Trying to download something that is not, apparently.

Silence is complete, no fastboots not include nothing to do ... O.O The version that something happened with eRecovery and with the usual .. The P9lite VNS-L21C432 ...Sorry my Eng

View attachment 4086705
[Nexus 7 (2013) Original Android 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 flo/deb include:

- Linux kernel 3.4.y merged in (currently 3.4.108 - mostly security patches and minor bug fixes)

- 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!)

- SELinux in Enforcing mode

Installation

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

- No known issues for flo/deb yet.

If you notice anything, be sure to report it in this thread. Stability is our main concern. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I 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) :)

Information about our experimental builds and progress you may find here.

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 to add extra features.

As usual, feedback is appreciated :)

XDA:DevDB Information

Unlegacy Android Project, ROM for the Nexus 7 (2013)

Contributors

Ziyan, Clamor

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

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.4.x

Version Information

Status: Stable

Current Stable Version: 8.1

Stable Release Date: 2017-03-24

Created 2017-03-24

Last Updated 2019-04-05
[Nexus 7 (2013) Original Android Development] Ziyan:
Reserved

GApps

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

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.

Stock-like setup

Disable the following built-in (AOSP) apps:

- Android keyboard (once you installed Gboard)

- Browser

- Calculator

- Camera

- Clock

- Email

- Gallery

Install the following apps from the Play store:

- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)

- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)

- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)

- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)

- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)

- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)

- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)

- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)

- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)

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 (2013) Original Android Development] boom1982:
Hello)

Please add a night mode, with the icon in the blind
[Nexus 7 (2013) Original Android Development] Ziyan:
I simply use Darker for night time playing in the bed :) personally, I reduce brightness to 65% and apply a slight yellow tint. When most websites are white, theming the framework wouldn't matter that much anyways... and we kinda want to feel like a factory image (no dark mode in them either) :)
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=2633638]Ziyan[/MENTION]

It's a pity)

The rom itself works fine. Good job)
[Nexus 7 (2013) Original Android Development] webdroidmt:
[MENTION=2633638]Ziyan[/MENTION] Thanks for your efforts on these older devices. I've used your work on both Gtab 2 and Grouper before I sold them. I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match. I haven't tried flashing any of the roms yet but figured I'd let you know.

Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. [MENTION=6622051]Startrek852[/MENTION] was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.

Anyway, just wondering if "in your travels" you've heard of this Netflix issue and might possibly know of a proper fix. Thanks again.

Mike T
[Nexus 7 (2013) Original Android Development] Ziyan:
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly :confused:

Play Movies works perfectly, so I'm not sure how to debug that :( either ways - can look into that zip later on.
[Nexus 7 (2013) Original Android Development] webdroidmt:
Thanks for your reply. Here's the D/L for the drmblobs zip if you decide to take a look. https://www.androidfilehost.com/?fid=529152257862690585

Very weird on the MD5 thing, as mentioned I downloaded it twice and on a desktop PC so it shouldn't be a mobile issue??? I'm gonna' flash it later, will report if there's a problem.

Mike T
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=2633638]Ziyan[/MENTION]

Updates come out every day ...?)

And why the cache is not f2fs?

I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out :)

p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
[Nexus 7 (2013) Original Android Development] irfanhutomo:
have volume wake option?

edit: stuck at "patch image "Patching system image unconditionally..."
[Nexus 7 (2013) Original Android Development] Ziyan:
Our little build server likes overdoing its job and building even if the changes don't affect flo - until this is fixed, it's enough to update every 3-4 weeks or so to get the security updates, unless I make an announcement here about a change :)

About /cache f2fs: there's simply no point, as that partition isn't actively used by the system (other than maybe OTA updates). I usually don't support it, as it can lead to more complications than what it worth...
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=2633638]Ziyan[/MENTION]

Thank you for your reply)

I really like the way the rom works.

Only have to use a lot of additional tools to at least somehow expand the settings)))
[Nexus 7 (2013) Original Android Development] esemyuron:
Good work... but video recording with green lines in Google Camera 3.2, stock kernel, Nexus 5
[Nexus 7 (2013) Original Android Development] Mayrbek86:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
[Nexus 7 (2013) Original Android Development] Ziyan:
Mind giving me a bit more details regarding this? I can connect to a Wi-Fi Hotspot created with my Nexus 4 (also running Unlegacy Android 7.1) just fine, and can browse the internet with the Nexus 7 through it (mobile data activated on the Nexus 4) :)
[Nexus 7 (2013) Original Android Development] maksimus0021:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine. :)

Regards.
[Nexus 7 (2013) Original Android Development] Ziyan:
Alright. We'll be soon opening a Nexus 5 thread as well. :)
[Nexus 7 (2013) Original Android Development] maksimus0021:
Good news! Thanks for your work! :)

Regards.
[Nexus 7 (2013) Original Android Development] Mayrbek86:
Where did you find this fix wi fi, give me a link?
[Nexus 7 (2013) Original Android Development] maksimus0021:
Install via TWRP.
[Nexus 7 (2013) Original Android Development] adstraylight:
Are there outstanding issues with 8.1/Flo also?
[Nexus 7 (2013) Original Android Development] abhifx:
apart from gps... not much. but there are more expected changes lined up. oreo is stable enough.
[Nexus 7 (2013) Original Android Development] b4ckfir3:
My Nexus 7 is running really hot for some reason, any ideas?
[Nexus 7 (2013) Original Android Development] Clamor:
New 8.1 builds are available, GPS should be fixed.
[Nexus 7 (2013) Original Android Development] deyanimay:
Skype front camera

Does the front camera work in the Skype app for this ROM? I'm currently using aicp and unfortunately half the image is messed up for the front camera in Skype. Back camera works fine and the front camera works fine in the default camera app just not in Skype. Hoping to switch to this if its not an issue.
[Nexus 7 (2013) Original Android Development] abhifx:
Can confirm that GPS is working. Functionality wise, this is the best ROM. However I did face a sleep of death which is strange. Will test more and report.

Wish dt2w was included in this ROM so that for my car install I can easily wake the tab.

Edit: on my second instance of locking GPS while driving, i could see lots of satellite but lock could not achieved.
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=3692487]abhifx[/MENTION] without dmesg/logcat we can't actually help
[Nexus 7 (2013) Original Android Development] adstraylight:
I had a couple of Sleeps Of Death with the previous version, I have a hunch it's got something to do with using the clear all button in recents before turning the screen off, this was a habit from my grouper years.

I did try to retrieve a last kmsg, but there didn't seem to be one...

Anyway, it hasn't happened since I stopped using clear all.
[Nexus 7 (2013) Original Android Development] abhifx:
I doubt clear all button is the culprit. but if it happened on grouper's unlegacy, might as well try and replicate here also.
[Nexus 7 (2013) Original Android Development] adstraylight:
No it didn't happen on grouper, I was just saying why I got into the habit of doing it, ie the lack of RAM on the grouper.
[Nexus 7 (2013) Original Android Development] MikiGry:
Why is GPU constantly running at 320Mhz ?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=5468078]MikiGry[/MENTION] no its not. 128-320-400 MHz, mostly 320MHz, with 400MHz while interacting
[Nexus 7 (2013) Original Android Development] MikiGry:
[MENTION=5424240]Clamor[/MENTION]

Idle frequency seems to be 320Mhz . It jumps sometimes to 400Mhz, sometimes to 200MHz but is always gets back to 320Mhz
[Nexus 7 (2013) Original Android Development] adstraylight:
Re: GPS on 8.1/Flo, I think that first fix time is greatly improved by calibrating the compass first, got it down to 8s.

---------- Post added at 10:58 AM ---------- Previous post was at 10:39 AM ----------

If you look in the GPU section of kernel auditor, you will find several different options of GPU governor, perhaps one of the others will suit your needs better?
[Nexus 7 (2013) Original Android Development] MikiGry:
I'm just curious why tablet always gets back to 320Mhz. Seems little wird to me. Nothing more than that
[Nexus 7 (2013) Original Android Development] cnsultnt:
First post says 2018.03.15 is the latest, but there are newer versions in the repository. Are they stable (except the one marked experimental)? I'm not offered system updates.
[Nexus 7 (2013) Original Android Development] Clamor:
2018.03.15 is last update of first post. All builds not marked as experimental are stable for daily use
[Nexus 7 (2013) Original Android Development] buffal0b1ll:
Yes. For my use, they're both stable including experimental 0613
[Nexus 7 (2013) Original Android Development] cnsultnt:
Thanks. Where would I find chance looks, if any? Runs great for me as-is, but behind on security updates.

Does the system update not work? It reports me as up to date. Dirty flash should be no problem, right?
[Nexus 7 (2013) Original Android Development] Clamor:
[MENTION=5047191]cnsultnt[/MENTION] there aren't any changelogs, there are only list what works/doesn't work. OTA are still WIP. I recomend use even EXP build. If it is published, than you can be sure it is stable enough.

[MENTION=4831195]buffal0b1ll[/MENTION] you r right, if EXP build is published, it is stable as well.
[Nexus 7 (2013) Original Android Development] Clamor:
Yesterday were uploaded new 8.1 builds (flo/deb) with July security patch (marked experimental but they are stable).

Future builds will be published approx. in first 10 days of each month (when new security patches are released). About builds with fixes of critical stuff we will write additionally.

P.S. 7.1 builds are available as well.
[Nexus 7 (2013) Original Android Development] abhifx:
Just to confirm that in oreo builds, GPS is locking quite fast.
[Nexus 7 (2013) Original Android Development] Bingoig11:
Deb or Flo?
[Nexus 7 (2013) Original Android Development] Clamor:
Both. They share same hardware (except deb has modem).
[Nexus 7 (2013) Original Android Development] daitalos:
Last build (20180703 8.1 experimental Flo) works very well,almost stable... The problem I mentioned in the post#166 has been solved ...

also,I think default cpu governor/ondemand doesn't works satisfactorily...Interactive it works much better & fast for me

thanks & sry for english
[Nexus 7 (2013) Original Android Development] nicky-xda:
Dirty update from LOS 14.1?

I have now installed: lineage-14.1-20171226-nightly-flo-signed.zip

Is there a way to dirty update to this "unegasy" without wiping "DATA"?

When i try that, it gets stuck at booting and the user interface never appears.
[Nexus 7 (2013) Original Android Development] braveheartleo:
As you can see for yourself, you cannot do a dirty flash from one ROM to another. There's the answer to your question.

I will suggest that you can at least do backups using Titanium Backup. You'll have to look it up yourself on how to do that, plenty of guides lying around. Though, I will suggest that you take caution that you don't include system apps and substratum overlays during backup and restore.
[Nexus 7 (2013) Original Android Development] nicky-xda:
This is not right. I've dirty flashed since some years on several different devices, even between them and between android versions 6, 7 and 8: sometimes it works and sometimes not ;)

In this case here unfortunately not (yet).

---

I've tried titanium several times as well and never hat real success because the settings of the apps normally do not get saved/restored.
[Nexus 7 (2013) Original Android Development] braveheartleo:
This will be my final take on the subject. ? Just because you got *lucky* on your dirty flashing experiences between ROMs from the past doesn't make it right.

Unless you hook some serial console to your phone and watch it while it boots to see and debug how *successful* your dirty flash has gone (like how a diligent person would do it), then you're just playing Russian roulette to see what works and what doesn't, like what your posts suggest and have no idea what you're doing (going about it blindly with luck).

Simply put: Dirty flashing between different ROMs is ill-advised (and even between same ROMs to some degree). Recommendation is always to clean flash. When you do dirty flash, unless you're willing to debug and fix what's broke for the benefit of others in the same boat as you, then you're on your own. ?
[Nexus 7 (2013) Original Android Development] Ziyan:
Actually, while not recommended, I dirty flashed from UA 7.1 to 8.1 without any issue; but yeah, dirty flashing from LOS to any other ROM doesn't work. :)
[Nexus 7 (2013) Original Android Development] nicky-xda:
compass / orientation not working?

On my device the compass / orientation sensor does not seem to work. The app "GPS STATUS" shows them as malfunctioning. What about you others?
[Nexus 7 (2013) Original Android Development] Ziyan:
Is this on the last Oreo build? Is auto-rotation working? Did you try rebooting?