yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] bubor:
from log:

this means your app/lib try to use neon instruction, what isnt in tegra2.

Did you try not flash anything? Probably one of the update is wrong.

Google droped tegra2 support long time ago. You have to use older gapps what support non-neon devices.
[Samsung Captivate Glide] dayanest:
What gapps do you currently use? Link
[Samsung Captivate Glide] radbme:
I am starting to think that Google's latest update to services has broken Tegra devices pre-lollipop. The reason I decided to flash this rom was because my ICS build seemed to break last week. Specifically I couldn't get hangouts or gmail to work properly and didn't know why. That makes sense if Google broke services. So I flashed this rom and am having the same issues. The trouble is when I flashed it I didn't know gapps was included so I simultaneously flashed open gapps. I thought THAT was the problem. So after a bunch of troubleshooting this is what I did this morning. I wiped in twrp. I reflashed this rom. I ran remove-gapps.zip to get rid of any remnant of previous gapps packages. I wiped again and then reflashed this rom to get back to the devs intended first boot environment. I then booted into first use and found that login and account restore worked perfectly. I installed logcat first from the play store and then tried to install gmail. It failed but I'm not sure why. In the background the play store auto-updated Google and Text-to-Speech. As soon as that happened I started getting crashing errors like before. So I opened logcat and got this log. I hope it helps. http://pasted.co/c37f39e3
[Samsung Captivate Glide] radbme:
It seems Google did break it. https://productforums.google.com/forum/m/#!topic/play/uX3Xqk2gi_k;context-place=forum/play
[Samsung Captivate Glide] bubor:
yes, as I said google droped non-neon devices finally.

You can try to use older gapps, and thats all.
[Samsung Captivate Glide] radbme:
You can't use older gapps because it forces the google services update in the background. Bummer. I wonder if there is a way to freeze it to keep it from updating.
[Samsung Captivate Glide] dayanest:
So solve.

This is my solution for Transformer TF101 on firmware KatKiss 4.4.4:

Install Lucky Patcher from here: dl1.revdownload.com/dl1/1701/Lucky_Patcher_v6.4.5__5557_Revdl.com.apk

Open Lucky Patcher, select "Search", type "Google"

Uninstall "Google Play", "Google Play Services" (I also uninstalled "Google App" forever cause I needn't it)

Download open gapps on 2017-07-31 from here: github.com/opengapps/arm/releases/download/20160731/open_gapps-arm-4.4-pico-20160731.zip

Disable Wi-fi

Reboot to TWRP recovery

Flash gapps, wipe cache/dalvik.

Now boot and create 2 folders in /data/app - com.google.android.gms-1.apk and com.google.android.gms-2.apk

Now you can turn on your Wi-fi

Here's my solution about installing right version of Youtube for this gapps and prevent Youtube app from updating. There's ZipSigner app which changes a certificate and "detaches" the app from Google Play. For Youtube app this method causes failure on startup with a security exception. Luckily, I've found another solution:

The latest working version is 11.41.56 on October 28, 2016. Download Youtube app from here: apkmirror.com/apk/google-inc/youtube/youtube-11-41-56-release/youtube-11-41-56-21-android-apk-download/download

Disable Wi-fi

Uninstall current Youtube using Lucky Patcher

Now install downloaded version of Youtube

Create a folder com.google.android.youtube-2.apk in /data/app. There should be 1 file com.google.android.youtube-1.apk and 1 folder com.google.android.youtube-2.apk.

This solution should prevent a Youtube app from being updated by Google Play: it begins to update but at the end dialog shown which says there's insufficient storage space.

By the way, you can prevent auto-update for another Google app like Google Drive. Open Lucky Patcher, click on the app and select "App Info" and you'll see a detailed info. All you need to do is to create a folder with name like apk but "-1.apk" has to be replaced with "-2.apk"

Turn on Wi-fi
[Samsung Captivate Glide] bubor:
noted in op

I hope this help others.
[Samsung Captivate Glide] radbme:
This worked for me. It's modified instructions from here: https://xdaforums.com/showpost.php?p=71117440&postcount=14

Download Google Play services APK http://www.apkmirror.com/apk/google...s-10-0-84-836-137749526-android-apk-download/

Download System App Remover http://www.apkmirror.com/apk/jumobi...p-remover-root-3-6-2019-android-apk-download/

Boot twrp

Wipe

Clean flash this rom (if you have messed with gapps prior to this trying to fix the google play services issue you should run remove-gapps.zip from bubor first and then flash the rom http://dualhoki.vim.hu/bubor/dev/remove-gapps.zip)

Reboot into android (or shut down and remove your SIM and then boot into android)

Skip wifi and google account during setup

Plug your Glide into your computer and transfer over Google services and system app remover

Open File Manager and in settings > general enable root access mode

Browse to where you copied over the apps

Install System App remover, open it and grant it root permissions

In System App Remover find Google Play Services and uninstall

Go back to File Manager and install the Google Play Services apk you transferred

Reboot

Open File Manager and browse to /data/app

Create a new FOLDER and name it com.google.android.gms-2.apk (you should see a FILE called com.google.android.gms-1.apk in there...leave it there)

reboot

Enable and connect wifi

Go to settings > accounts and add your google account

Feel free to install any google apps. I installed Hangouts and GMail. All is well currently. I'll update later if things change.

Edit: I've now tested the latest Maps and Youtube. Both crash upon opening or when playing a video. I tried this fix for youtube https://xdaforums.com/showpost.php?p=71086312&postcount=6 but it didn't work. Youtube still works fine in the browser though and Waze is a better map app anyway!
[Samsung Captivate Glide] radbme:
After playing with this rom a bit while trying to find apps that would actually run without crashing (thanks to google's push for dependence upon google services and then breaking it for tegra devices), I decided that it was just too much work and far too unstable. The fix I wrote above DOES work for keeping google services from updating but there's some sort of invisible issue where the latest app updates for Maps, Youtube, and other google apps still won't run. I decided to flash back to stock ICS with Odin. After putting CWM (and then TWRP cause it's better) and rooting, I then installed System App Remover and cleaned house. Most of the stock apps are gone now and all of the bloat. Since ICS predates google play services I actually had to install a couple google apps to find one that forced the google play services install. I chose Maps which to my surprise worked fine (this also updated the Play Store)! (lol) But then I installed GMail and here came the errors. I was then able to do the same fix from above to stop the errors. I had to get a different Play Services apk for ICS com.google.android.gms_10.0.84_(030-137749526)-10084030_minAPI9(armeabi-v7a)(nodpi)_apkmirror.com.apk from apkmirror. WIth that in place and all the bloat gone, this thing is humming right along. I actually prefer the stock messaging app too. The browser is a bit out of date but Opera works really well. Anyway sorry to the mods if this is out of place but just wanted to say how well ICS runs on this in general. Oh and all google apps are working perfectly. Youtube, Maps, Hangouts, Gmail, Google Play Store are all great. I'm happy to share my methods if anyone wants to go back to ICS.
[Samsung Captivate Glide] giannhs_n:
for those who still want cm11 i have found a solution for glide users, find and download com.google.android.gms_10.5.42_(036-149175906)-10542036_minAPI14(armeabi-v7a)(320dpi)_APKdot.com.apk push it on system, remove pre-built gms core apk, after navigate to data/app and make 2 directories named

com.google.android.gms-1.apk

and

com.google.android.gms-2.apk

(this will prevent auto update Google Apps)

and you will have gms that support most of apps

Enjoy!
[Samsung Captivate Glide] bubor:
just download latest beta relase from here:

http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-10-5-48-release/
[Samsung Captivate Glide] giannhs_n:
i will try it... by the way, on latest lineage release xposed do not work it makes endless bootloop... any solution for this? thanks
[Samsung Captivate Glide] bubor:
did you try clean install? ( wipe everything)
[Samsung Captivate Glide] organic2:
Hi Everyone

i tested AAAAAlmost version of GAPPS on our tegra device. Really Last Version of gapps works good without force stop is gapps_20170110 included Google Play Service version 10.0.84

https://github.com/opengapps/arm/releases/tag/20170110

You can download arm 4.4 pico/nano Package and wipe cach and install it from recovery.

https://github.com/opengapps/arm/releases/download/20170110/open_gapps-arm-4.4-pico-20170110.zip

And i found easy way to stop google play Auto update.

First backup of google play service with titanium backup.

You can install autorun manager. And found google play. And Uncheck all of 22 recivers of google play app. And restart device. Done

But!! If not work propley. Restore the google play service (with titanium backup) and TRY THIS NEW WAY!

1.Install Disable Service "app"

2.Goto system tab and foung google play

3.Unckeck/disable '*wifi check and auto update' & "GmscoreUpdateService"

Done. Google play never update himself & google play service

This should be work on 4.8.2 google play and above

Finaly way to Stop Auto update, is: use moded google play app

But its not easy!
[Samsung Captivate Glide] giannhs_n:
i did clean install when i switched to lineage build, boot loop happens when xposed is active if i disable it rom boots normal
[Samsung Captivate Glide] axy_david:
guys, any mirrors? none of the downloads work.

Where can I find the kernel for this if I'd like to use it in other roms(such as crdroid)

I can also say, the latest version does not work with xposed.

Downgrading to the latest cm11 version without even wiping solves the issues, it seems the latest security path might interfere with xposed.
[Samsung Captivate Glide] organic2:
Whats mean about lastest version? Linageos 20170207 ?

I have uploaded ones

Yon.ir/cm11glide

This is 20150825 fastest versions of rom + 20151230 kernel & madouls

You can mix newer kernel ith this. But i dont think any defferent
[Samsung Captivate Glide] Snot Here:
It's 2020 and I may be the only person on the planet who still has a working Glide. I realize no one is working on this phone any more but I still thank [MENTION=5112223]bubor[/MENTION] for this thread because his builds are among the few for this phone that are still available for download.

Confirmed. Xposed loops on boot with 20170207 LineageOS build. I flashed back to 20161102 CM build which works OK with Xposed.
[Samsung Captivate Glide] greeneyez15o:
No battery drain ???
[Samsung Captivate Glide] BrandonE97:
I too have had camera issues with latest rom. Internal storage nowhere near full. As another member posted Netflix doesn't work, never has on any rom other than stock ICS. During the Netflix app loading screen it just crashes. Battery drain issues are going on with Google Play Services on my Cappy too, version 5.0.84 auto updated from Play Store.

On a very happy note with the latest CM build I've had no WiFi issues at all! WiFi is working great and that's with default CM kernel.

I have been running ART instead of Dalvik the whole time for fun and testing to how well it works.
[Samsung Captivate Glide] irekd:
The main reason google released Play Store version 5.0.84 (2 days ago) was to make it handle their G (LG) watches presented during I/O conference. If you don't have such a watch, you don't need the newest Play Store.
[Samsung Captivate Glide] Makshow:
That's true, but it updates on it's own, and I don't know a way to disable it. :)
[Samsung Captivate Glide] Androide3:
Go to app manager and select Google play services and uninstall the update, works for my, my battery life it's better now ...sorry for my english...
[Samsung Captivate Glide] victorsalas:
Netflix problem
[Samsung Captivate Glide] BrandonE97:
Well, WiFi stayed connected constantly until I reverted Google Play Services to stop the battery drain issue. Now the CPU is able to enter sleep and WiFi is going out again. Just like with all other roms it goes out when the device goes to sleep. Turning the screen back on usually causes it to reconnect within a minute or two. Don't know if this info can help in any way but its something I noticed and wanted to report.
[Samsung Captivate Glide] shimbob:
The netflix issue can be fixed as described here.

I use option #2 because Xposed doesnt work under ART.,
[Samsung Captivate Glide] BrandonE97:
Some thoughts on the WiFi issue. I've used the Captivate Glide as a VOIP WiFi only phone for some time. The app I've used is Groove IP that logs in to my Google Voice to send and receive calls. Google will soon cut off service to XMPP, the service these third party apps connect with, and this app will stop working with the service but until then I am still using it. The app has options for a CPU lock and WiFi lock. With the Google Play Services issue keeping the CPU awake the WiFi never cut off. I've since then reverted to the previous version supplied by Bubor's latest CM11 ROM. CPU now goes to sleep proper and battery is back to normal. On a hunch I enabled the WiFi high performance lock in the Groove IP app and now WiFi stays connected without any issues. My question is to Bubor as to if you can enable the WiFi lock by default or add an option to enable it in options to solve the WiFi dropping issue. Maybe add it to the "Keep WiFi on during sleep" option when selecting "Always". This lock on my Nexus 7 tablet causes more battery usage but on the Captivate Glide it doesn't seem to cause any additional battery drain and keeps WiFi on and working proper all the time. This could possibly be a fix maybe for the WiFi issue?
[Samsung Captivate Glide] bubor:
can you try app like this: https://play.google.com/store/apps/details?id=opotech.advancedwifilockfree&hl=hu ?
[Samsung Captivate Glide] willriddle1:
I installed it!

Sorry I actually isntalled the ROM from the other thread... can't figure out how to delete this post.
[Samsung Captivate Glide] Makshow:
Hey, an 2014-07-25 update! That's great! I've already flashed, running fine.

Thanks for your continuous work.
[Samsung Captivate Glide] ReznikAkime:
Agreed, thanks for keeping things rolling with the updates. Is it just a CM update?
[Samsung Captivate Glide] bubor:
yes.
[Samsung Captivate Glide] mara-:
Anyone got automatic Skype fix working? For me, automatic switching works 1 of 10 times, meaning 9 times GSM calls won't work. Tasker shows it executed commands, and it shows good output, but GSM calls still won't work. Any suggestion?
[Samsung Captivate Glide] irekd:
wi-fi issue #2

Hi, I'm on 20140725 and all is running fine except wifi. To be honest wifi doesn't work properly for me since I started I927 adventure.

How it behaves ... it just doesn't want to turn on at once I'm being tapped on wifi icon. I must tap on the icon a few times (sometimes 3 times is enough, sometimes even 10 times don't do the trick). In case when lots of taps don't work I enter airplane mode and at once exit it or change 2G to 3G and back to 2G, than tap on wifi icon and in most cases it helps. But the whole thing is very annoying. I red about wifi problems on this and [MENTION=5519567]stormdude124[/MENTION] thread, but it seems my problem is different.

Here's the logcat part related to my tries of enabling wifi:

D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/MPLSensor( 416): cb_onMotion:2
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver
D/MPLSensor( 416): cb_onMotion:1
D/WifiService( 416): setWifiEnabled: true pid=542, uid=10015
E/WifiStateMachine( 416): Failed to load driver

As you can see I've tried 8 times (calling setWifiEnabled method) and all have failed.

And the reason is wifi driver.

Does anyone encountered such a behavior?
[Samsung Captivate Glide] stormdude124:
I had the same problem but it worked half the time (but I used automateit)

Also [MENTION=4626389]irekd[/MENTION] Did you dirty flash or factory reset and install

Also have you tried graKernel?

I've never had WiFi problems on any ROM that's strange... What's your baseband?
[Samsung Captivate Glide] irekd:
Usually I dirty-flash my roms. In most cases it works fine. Yes, I know one should always factory reset and start everything from scratch, but the time... if only it wouldn't take so much time. Anyway I'll try to eliminate potential reasons.

I didn't try graKernel. My baseband is I927UCLJ3.
[Samsung Captivate Glide] stormdude124:
Usually when I update I'll backup /data (which is all your apps and app data ect.) Factory reset and restore /data

That way /system gets updated properly

Try graKernel and report back
[Samsung Captivate Glide] Adam77Root:
[MENTION=4626389]irekd[/MENTION]: Check dmesg too.
[Samsung Captivate Glide] mara-:
It seems that this solution is not reliable then. Any idea why it happens? Maybe switching to GSM library is not fast enough?
[Samsung Captivate Glide] Makshow:
Have the same issue from CM 10.1.3, previous versions worked fine. Tried different ROMs and grakernel - it's a known issue, nothing happens. My solution was simple - I just never turn Wi-fi off. Battery life impact is negligible - phone never searches for wi-fi when sleeping, once in 3 mins when awake. But I agree, it's a bit annoying. Once in a time I have to disable wi-fi, after that I usually reboot - glad this happens only once per few weeks maybe.
[Samsung Captivate Glide] irekd:
I went your way and fortunately it worked. I don't have wifi issue anymore. Thanks for advice. I used backup/restore feature may times before, but never this way. I mean to install a new rom version after making factory reset and than restore only /data "partition". It works like a charm and is way faster than conventional clean install and installing all apps or restoring them using software like eg. titanium backup. [MENTION=5304692]Makshow[/MENTION] try to go this way.
[Samsung Captivate Glide] stormdude124:
Glad to hear it worked :D

---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------

That seems about right
[Samsung Captivate Glide] mara-:
Shame. I really thought we have a solution for this, but we can hope someone will come up with something else.

BTW, anyone experiencing random reboots?
[Samsung Captivate Glide] mara-:
[MENTION=5112223]bubor[/MENTION]

Can you do anything about wlan? When I disable it, I can't enable it again, I have to reboot the phone to get wlan working. I think this problem didn't exist before.
[Samsung Captivate Glide] Sztunt1:
I find solution: many time press the wifi button in status bar:) For me works always.
[Samsung Captivate Glide] irekd:
As it was adviced a few posts earlier by [MENTION=5519567]stormdude124[/MENTION] and confirmed by me, just make a clean install and the problem with turning on wi-fi should disappear. At least at my place it has. There is also described over there how to restore apps with their settings (all installed and configured apps).

BTW [MENTION=5519567]stormdude124[/MENTION], I made some research and proposed by you and now used alsp by me method of restoring data partition, although work properly in most cases, hower there are apps, which are being installed on data partition, their settigngs are stored there as well, but they have influence on system partition, because for instance during installation they read some kernel state. Then when we install a new rom and restore old data partition, we can have problem with such apps. Thus proper work of this method is not 100% obvious and one should take it under consideration.
[Samsung Captivate Glide] stormdude124:
For example say your coming from omni ROM and you restore its /data to cm it won't work. This method is ROM dependent
[Samsung Captivate Glide] irekd:
My post wasn't about going from one rom to another. I was talking about CM within one version (just changing nightlies).

Many system (Android) settings are stored in the data partition. That's why, when you restore it, some settings restore.

Imagine what will happen when you clean install a new CM nightly, which has some significant changes/improvements in system, and than you restore data partition containing some system settings, which aren't up to date or are completely different than system apps are expecting. It can cause strange Android behaviors. Of course most apps will not be affected, but who knows which ones will be, so we must be watchful :)
[Samsung Captivate Glide] stormdude124:
Agreed. I understand now :D
[Samsung Captivate Glide] SillyB:
Thanks Bubor!

I've been running one of your old JB roms forever. Things around here seemed to slow down and my build was pretty stable so I didn't keep tabs on anything for months. My phone began to bog down and I wanted to do a wipe and fresh install to pep it up, so I checked in here and found you're still updating your amazing work. I've been running this KK rom now since saturday and its great! Just wanted to say thanks along with my donation - go grab lunch on me!
[Samsung Captivate Glide] irekd:
[MENTION=5112223]bubor[/MENTION] you've built a new version (20140822). Thanks. Any important changes, or just a monthly update?
[Samsung Captivate Glide] bubor:
nothing in device tree.
[Samsung Captivate Glide] vampiro:
Random reboot...

I've installed 4.2.2 and 4.4.4 and there was so many random reboots.

Just spent 3 hours doing backups and fresh installed CM11 - 20140822 (4.4.4) and this stills continues. I've flashed stock 4.0.3 many times and this is not happening in stock. Did this to eradicate the idea it was a hardware issues, but it's not.

I like CM versions for my folks, as these help to have a cleaner rom and longer battery, but can't seem to find the issue or solution.

Someone else did mention "random reboots" earlier but there was no answer on his question.

Has anyone else had this problem after install?

Is there a solution to this?

How did you fix it to keep it from rebooting?

Please answer and/or look into....

BTW, great rom so far, and hate to switch back to stock as my mom can't keep her phone on and missing calls.