Related
I've bought my prime for slightly more than a month now and I've noticed that sometimes there may be random restarts after the screen hangs, for example while playing Asphalt 6 and browsing through flash heavy websites today at separate times, the screen turned irressponsive (Not even the home buttons worked ) and my prime restarts, has anyone experienced this before ? I'm troubled as whether or not my prime is faulty, if so would I need to prove that it is for a warranted exchange?
yes, happens to me too. 2-3 times a week
MXR2 said:
yes, happens to me too. 2-3 times a week
Click to expand...
Click to collapse
I wonder whether this is normal and will be fixed by an update or may our units may just be faulty )):
Been getting this lately as well. 2 to 3x a week for me too. Since .21
Sent from my Transformer Prime TF201 using Tapatalk 2
this can happen on pretty much any arm slate or phone.
I experienced this myself on all my devices (though very rare on the iconia).
On my desire, the stock rom suffered it very frequently when playing intensive games, once I had modded everything and ran an aosp rom with a completely stable and custom kernel (courtesy of thalamus <3) my mobile never ever did it since.
It simply occurs because the kernel is not completely bug free and also no processor is ever made equal, you could find eco may cause restarts more randomly if your processor cant handle lots of utilization on the companion core and undervolting, it may also happen on the higher settings on processors simply due to the kernel.
It's no reason to give up on your device or worry that its defective, if you try hard enough im sure you could get just about any stock arm device to soft reset through multitasking a bunch of intensive things at once and dicking with its governers at the same time.
some of the custom kernels are already looking epic promising like shakes, these paired with aosp roms will introduce a far better level of stability to our tabs, its just a matter of time.
Hello I own the Samsung Vibrant for two years now and even though I was a bit reluctant to overclock the phone at first as new phones were coming out in the market and its (Vibrant's) performance deficit was becoming all the more significant (in comparison to newer phones) I "succumbed to the temptation". At first by a little margin (no more than 20% overclock) but eventually -as I was seeing my phone to be capable for it- for even greater ones. There was a time that I was using my phone at 50% over-the-stock clocks.... those were the days
Eventually -it seemed- as if it somehow starting becoming less and less capable holding the clocks so I started lowering my clock thresholds eventually killing the overclock altogether. Mind you the grand total of the time(s) that I had my phone overclocked (up until then) was not that great...
But then ICS came out with all its fancy tools and the "temptation" overcame me again and as if from a miracle I was able to maintain 50% overclocks like the good ole days (1512Mhz to be exact). To be sure -that time around- that that is a stable clock I devised a slew of different test from extensive software decoding, to 3D and CPU rendering. My phone was rock solid. To address the battery issue I bought an extended battery and all was well in "Vibrant-Ville"...
To my dismay though even though my phone seemed rock solid I seemingly starting losing my overclocking capacity (once again) as I migrated into Jelly Bean, so I said to myself "oh no, no, I'm not going through this again, I'd choose a moderate overclock and I'll leave at that". So I disabled Live-OC, custom voltages, hell even deleted NSTools and used the standard 1.2GHz setting, my battery was better, my phone was rock solid once again and thanks to jelly bean my phone was still fast enough...
Two days ago -though- the ghosts of the past reared their ugly head once again, out of the blue my phone lost its stability. Anytime I was trying to do anything remotely complex and it would reboot (BTW I'm using Helly-Bean right now, using the "Smooth" setting, Smartass governor @ 1.2ghz, pretty standard stuff).
I love this phone but I feel it's nearing its death-bed, what's your opinion guys?
I'll prolly remove the oc altogether but I fear it won't be enough, I fear that instability would start encroaching the 1ghz setting as well one of the days and then it would be game over. I want to avoid this fate at all costs, so anything you could recommend I would try, even changing my rom.
Also to those who used overclocks in the long term what was your own experience?
Thanks for your attention
No response(s)?
Sorry for the bump but I take it none of you guys ever have/had any of the problems I'm describing. Hmm, that means that I was unlucky with my piece of hardware it seems... pity :/
More than likely an aging chip is the case. Personally my phone runs smooth at 1GHz, so I don't see the need to unnecessarily overwork the CPU. After reading your original post, one line stuck out to me in particular. You mentioned that you ran the CPU at 150% for a time, and to me that sets off a red flag. Setting the CPU at 1.5GHz is risky and can cause some major wear on the CPU. Not to say I've never overclocked that high, but I usually only set it that high when playing a high graphics game. Even then, 1.5GHz is not recommended if you wish to use your device long-term. Even 1.4GHz is considerably pushing it. Although our devices can handle it, eventually, they're going to tire out. Now some phones may be able to last longer than others, it depends on the amount of iron in the sand used to make the silicon processors or other minuscule things could play a role. Essentially, it's random. No two chips will be exactly identical nor run exactly the same. So in your case, that may be the case. Perhaps your device really is nearing the its end. Considering that your phone was made to last only a few years at stock speeds, you should still be pleased with how long it's lasted. However, it is understandable if you're upset with this. The only thing I can suggest is to not overclock anymore and to try and keep its temperature low. Perhaps try undervolting? But if you want your phone to last, don't overclock (if your phone's processor is already starting to fail at 1.2GHz, when it used to run rock solid at 1.4 or 1.5GHz, then you definitely need to stop overclocking entirely). More than likely you won't hear other Vibrant users discuss similar problems because they've already moved on to new devices, before the long-term effects of high overclocking began to take its toll. But if you do a little research, you'll find other users on other devices having similar problems to what you are having.
Wish you the best in your efforts, and hopefully you'll get a year or two more out of the device... Hopefully someone will come forward with a better recommendation/solution to your problem. Since I pretty much stated what you probably already knew.
I'm not for overclocking, nor have i overclocked my vibrant.
With that being said, i have never had any performance issues, and I'm having difficulty recalling any issues with stability either..
I hope you treat your new phone with more respect..
I'm sure it will live you much longer for it.
Sent from my amazingly stable SGH-T959 using SlimICS
I have Samsung drivers
atlas 2.2
odin 1.3
gbbootloaders
cmw4 fixed for cm7
CI500_VZW_EH03_GB_CM
and mutliple releases of CM10.1
I followed instructions exactly how [GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock say to do.
I always end up with a bootloop after flashing. The instructions are flawed. Or, one or more files are corrupted.
fewert said:
I have Samsung drivers
atlas 2.2
odin 1.3
gbbootloaders
cmw4 fixed for cm7
CI500_VZW_EH03_GB_CM
and mutliple releases of CM10.1
I followed instructions exactly how [GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock say to do.
I always end up with a bootloop after flashing. The instructions are flawed. Or, one or more files are corrupted.
Click to expand...
Click to collapse
Did you look at my post which further explains the process.
http://forum.xda-developers.com/showthread.php?p=53235945
Have you installed cm10.1 multiple times?
Some times it doesn't always set thing up in one flash
hhp_211 said:
Did you look at my post which further explains the process.
http://forum.xda-developers.com/showthread.php?p=53235945
Have you installed cm10.1 multiple times?
Some times it doesn't always set thing up in one flash
Click to expand...
Click to collapse
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
fewert said:
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
Click to expand...
Click to collapse
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
skepticmisfit said:
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
Click to expand...
Click to collapse
Lol my phone e400 is super multitasker
Sent from my LG-E400 using XDA Free mobile app
fewert said:
Yeah I read a post saying to do what you just described with success.
However, this phone is really poor. I have tried GB, ICS, JB and all of them I get similar performance just different features.
The phone can't handle two apps at once regardless of the rom.
I was traveling to a different city to get something on Craigs. It constantly would shutdown my Maps and Navigation when I wanted to read a Kik message.
If I have Kik open and want to read a txt msg, it takes like 10 seconds after clicking the txt msg icon to show the txt.
Is there an app or method that everyone uses on this phone that I don't know about to get this phone to run speedy? Or, is it just so outdated it can't run modern versions of apps?
I just want navigation, txt, kik, and a light browser like dolphin.
Can a Fascinate handle all that and be snappy and quick??
In the mean time, I am switching over to my S3, though I don't like how it's so big I can't reach all the screen with one hand.
Click to expand...
Click to collapse
skepticmisfit said:
i think you should understand that this phone has a single-core CPU. running at 1GHz. this phone is almost 4 years old. it's amazing this thing can even run things like Kitkat at all, let alone with the relative finesse the most recent unjust build provides.
it took me a while to realize that apps these days are not optimized for single-core CPUs, it took upgrading to a gs4 to realize that. the fascinate is an admittedly, well, slow phone. or its not meant for multitasking, definitely.
the s3 runs circles around this phone. almost anything does. i've never really found anything that allows for the multitasking and insane speed that i get out of my s4, the closest i've ever gotten was cm7, but that even in its stable release had tons of SOD problems (sleep of death, phone locks and never comes back on).
part of the issue is that the fascinate has 512MB of RAM. back in 2010, it was adequate. not even good, just.. alright. these days the norm is 2GB. a phone with 1GB of RAM is considered outdated. despite google's efforts to optimize kitkat for 512MB devices, this phone's GPU shares RAM with the system, and depending on the configuration, usually 100+ MB is reserved for the GPU, leaving typically about 360-384MB of RAM. You can get more (the kitkat ROM i've mentioned allows 416MB of RAM to the system) but things will start breaking, particularly HD video recording and torch, among other things
Click to expand...
Click to collapse
I have not used the kik so I can't really say about it's performance,,, I have seen on the 4.4 kitkat rom from Unjust when I have used google maps navigation it was a huge battery sucker, no matter if I only put it on device [gps] only. I could barely even use it and on a charge it was still draining it faster than it could take it.
i did not have this on jellybean roms
I have not had the the problems you describe '10 seconds to open an app'.
Hangouts used to be slow opening initially but their latest update has made it much faster
I don't think it's multitasking is bad for what it is as a phone given it's specs,,, but everyone use a phone differently,,,
so I mostly agree with the overall jest of what skept is saying,,, it is ultimately limited by the 512MB ram available to use.
for GB and JB roms you can also look at the V6 Supercharger thread, it does help with multi-tasking, it can be a bit hard to understand how to implement it but once you figure that out it goes decent, boot up and time till initial use are much longer than normal, but you just have to plan your reboots for when plenty of time allows
i think jellybean roms are very good performers and given the face that you can use a different kernel that allows for overclocking up 1400 Mhz if desired,,, it's a give and take though,,,, over 1200Mhz and battery life goes south very quickly. [luckily the battery doesn't take long to charge, usually 1 hour,,, and even 5 minutes here or 10 minutes there will really help it last through the day]
Most of the earlier jellybean [4.1.x] versions seemed to give better battery life from what I remember than the newer [4.2.x] ones
and there are a lot of different ones to choose from to suite your style or needs from basic cm to full customization.
most of them were stable enough to be daily drivers,,, the big thing is you will just have to read up on a particular one or just break down and try some to see if they fit what you want.
With all that said though the fascinate will never perform like an S3, S4, Nexus, Nexus 4, Moto G, Moto X
I would consider checking out the Motorola Moto G, it's physical dimensions are nearly she same as the fassy but a hugely better phone, screen size, etc and depending on your phone carrier needs it can be had for as little as $65 bucks...
Well lg optimus l3 is very powerful and performant in fact of multitasking if you're a dev or not a complete noob.My phone can go until 1.2 ghz without probs and its factory clock speed was 800 mhz.Most apps aren't optimized for multi-cores and l3 is single core.384 mb of ram are enough on stock and 301 mb aren't enough on cm.But my kernels got swap.
Battery is very good:10days in stand by,2 days in normal use.
Antutu sucks but i don't believe in it.
So its up to the devs,we're good devs and there are more than 100000 l3s in the world.Now we're getting dualboot.Its all about devs,its all about devs.
Sent from my LG-E400 using XDA Free mobile app
Is it just me, or does the phone use a lot of RAM? Mine seems to be using 2.7GB minimum at all times. Seems high.
Higher would be more ideal. The Windows mindset of "I'm running out of RAM!" doesn't get you anywhere here; in Android, empty RAM is wasted RAM. My Droid Turbo averages ~1.8gb used of 3gb. Seems Nougat tries to average 60%-70% usage.
When you switch out of an app, it's moved to the background and (usually) suspended, but kept in memory so you can switch back to it quickly. It's things like this that take up memory you think should be "free".
In the event that you need to load up a big app, stuff running in the background is quickly and gracefully unloaded.
Unless you're getting constant foreground app crashes - which might indicate that something is forcefully keeping itself loaded and starving everything else of needed memory - you shouldn't worry about it. Android is fairly good at handling memory these days.
Septfox said:
Higher would be more ideal. The Windows mindset of "I'm running out of RAM!" doesn't get you anywhere here; in Android, empty RAM is wasted RAM. My Droid Turbo averages ~1.8gb used of 3gb. Seems Nougat tries to average 60%-70% usage.
When you switch out of an app, it's moved to the background and (usually) suspended, but kept in memory so you can switch back to it quickly. It's things like this that take up memory you think should be "free".
In the event that you need to load up a big app, stuff running in the background is quickly and gracefully unloaded.
Unless you're getting constant foreground app crashes - which might indicate that something is forcefully keeping itself loaded and starving everything else of needed memory - you shouldn't worry about it. Android is fairly good at handling memory these days.
Click to expand...
Click to collapse
I notice this issue more on custom ROMs than stock firmware. On mine and my wife's Quarks (3GB RAM, as you well know), running Marshmallow and Lollipop versions of the same ROM, something causes the phones to just freeze up for about a minute, crashes, then RAM is released to use. It was happening at least once a day on my phone, then my wife said it was happening to her phone. (Our old phones, not the new LG V30 phones.) I've messed with the LMK settings, trying different combinations, to no avail. And I did report it in the Nougat ROM thread for that phone. (Marshmallow ROM thread no longer has support.)
So, while I totally agree with your answer, it is the technically correct answer, I do understand the OP's concern. I've gotten to the point where I like to see more free RAM, so I know my phone isn't about to freeze up. At least on my old phone.
I love custom ROMs, but the past couple of weeks it's been nice to run stock on my new LG V30 and have a very fluid experience. I've not disabled anything. I saw some others disable stuff and then got lagging. I've not touched a thing and my phone is very smooth.
Could a "theme" downloaded from play store take up a lot of RAM and/or slow things down, too?
This is my first experience with a theme.
coldbeverage said:
Could a "theme" downloaded from play store take up a lot of RAM and/or slow things down, too?
This is my first experience with a theme.
Click to expand...
Click to collapse
Possibly, but probably not. From what I've seen, LG themes seem to skin far less than say, substratum does, and even substratum is pretty lightweight unless you get into transparent themes.
Keep in mind the default theme is itself...well, a theme. You're not really saving anything by staying on it. If you see a skin you like, use it, if you're really worried use one of the LG-provided ones that come with the phone.
ChazzMatt said:
I notice this issue more on custom ROMs than stock firmware. On mine and my wife's Quarks (3GB RAM, as you well know), running Marshmallow and Lollipop versions of the same ROM, something causes the phones to just freeze up for about a minute, crashes, then RAM is released to use. It was happening at least once a day on my phone, then my wife said it was happening to her phone. (Our old phones, not the new LG V30 phones.) I've messed with the LMK settings, trying different combinations, to no avail. And I did report it in the Nougat ROM thread for that phone. (Marshmallow ROM thread no longer has support.)
So, while I totally agree with your answer, it is the technically correct answer, I do understand the OP's concern. I've gotten to the point where I like to see more free RAM, so I know my phone isn't about to freeze up. At least on my old phone.
I love custom ROMs, but the past couple of weeks it's been nice to run stock on my new LG V30 and have a very fluid experience. I've not disabled anything. I saw some others disable stuff and then got lagging. I've not touched a thing and my phone is very smooth.
Click to expand...
Click to collapse
Interesting. It does seem like stock ROMs tend to be more conservative with RAM usage, whereas custom ROMs will have less aggressive minfree settings in order to keep more stuff loaded up. "Unused RAM is wasted RAM", but only up to a certain point; in my experience (Maserati with its ancient kernel as well as Quark) approaching ~100mb of free memory in LP/MM/N can bring things to a crawl, and pushing it can cause a kernel panic :good:
The only issue I've seen in Quark RR has been with the Pixiv app, though, and it does exactly what you said. But...I'm fairly certain the app itself leaks memory, as it only happens after browsing a while and is perfectly fine for another stretch after it OOMs and restarts.
My experience with stock ROMs in the past - Quark included - has been "smooth but lacking in features/customization" --- I've never really understood the complaints that stock is slow and claims that custom is blazing fast in comparison. The OEM has a decided advantage in that they have all the tools they need to compile the ROM properly, with then-current driver and kernel sources and a deep understanding of the hardware...I'd be really surprised to find a stock ROM from the last few years to be slower than custom.
But to be honest, my sample size is pretty small. *shrugs* I stick by what I've said, though, if anything the V30 doesn't use its memory enough; some people have complained about apps popping out of memory sooner than expected. LG is still putting out updates too, if a memory-management problem is found, hopefully they'll get right on fixing it.
I recently went from a oneplus 5 to the nord 200 when I switched to t-mobile because of the free promotion. Before I got it I did a little bit of research on the processor and storage speed and didn't expect much of a difference in performance because the snapdragon 480 seems to be fairly powerful and the nord has the same UFS 2.1 storage as my old phone.
I was pretty disappointed to find in my use the phone about 1/2 the time the phone was pretty sluggish in the general user experience and app launch times were significantly longer. May be placebo, but I disabled digital wellbeing, and all the tmobile bloatware and it may have helped a little. I remember reading oneplus heavily throttled some of their phones in recent history. I may switch back to my old phone.
I know the device is relatively new, do you guys think it will get better with software updates or is this just how it is?
I found turning on "Mobile data always active" in the developer options massively improved performance in my apps (at least where online load times and download speeds in-game were concerned)
Did you just get your phone recently? After setting up this phone for the first time, I also noticed the device was extremely slow, with all the app and software updates happening in the background. After all the updates were installed, I turned the phone off for about a day, and performance went to normal. It's not as fast as a flagship and there are minor hiccups here and there, but that's about what I expected from a 400 series SoC.
My original report was the day after I set everything up, I disabled the permissions for the launcher which did improve the responsiveness of the launcher, but application performance and launch times are still slow compared to my old device and not what I would expect from a phone of this spec.
I'm pretty confident this phone is a victim of oneplus' recently reported throttling for battery life. I was curious and compared geekbench scores (which aren't throttled under oneplus' list) and both the nord and my oneplus 5 got fairly similar scores for both cpu and compute. I tried out a browser benchmark motionmark which benches graphics performance. The nord got a 25 and the oneplus 5 got a 189... I ran the test again to make sure but got similar results.
That graphics should be coming from gpu and not cpu though....
I tested cpu and compute on geekbench, compute is a measure of gpu performance. The nord scored a little higher than the 5 in that.
I would assume oneplus' throttling would effect cpu and gpu but even if not, my oneplus 5 scoring almost 8x as high does not seem anywhere near normal
T1Coreon said:
I recently went from a oneplus 5 to the nord 200 when I switched to t-mobile because of the free promotion. Before I got it I did a little bit of research on the processor and storage speed and didn't expect much of a difference in performance because the snapdragon 480 seems to be fairly powerful and the nord has the same UFS 2.1 storage as my old phone.
I was pretty disappointed to find in my use the phone about 1/2 the time the phone was pretty sluggish in the general user experience and app launch times were significantly longer. May be placebo, but I disabled digital wellbeing, and all the tmobile bloatware and it may have helped a little. I remember reading oneplus heavily throttled some of their phones in recent history. I may switch back to my old phone.
I know the device is relatively new, do you guys think it will get better with software updates or is this just how it is?
Click to expand...
Click to collapse
Same experience here, i picked up this phone expecting at least a decent experience but still get bad slow not usable for everyday tasks sometimes.
Im not expecting a flagship performance of course but this is far from decent in my experience.
I hope android 12 will solve many performance issues. Or custom fw
I'm about to throw away this phone into trash. Did not expect so weak dev community activity. The laggy interface is almost unusable if you constantly swap between apps and find them unloaded from RAM. All my text or uploaded content just disappear. It is very frustrating experience. I never had this behaviour with my 2/32 gb xiaomi.
zaooza said:
I'm about to throw away this phone into trash. The laggy interface is almost unusable if you constantly swap between apps and find them unloaded from RAM. All my text or uploaded content just disappear. It is very frustrating experience. I never had this behaviour with my 2/32 gb xiaomi.
Click to expand...
Click to collapse
If you're really at your wit's end, have you considered installing a GSI? I've tried Phh's AOSP w/ gapps, and once you register your device with Google, it works flawlessly (except safetynet/drm) and is a million times faster than stock. Or I'd be more than happy to take your device off your hands.
zaooza said:
Did not expect so weak dev community activity.
Click to expand...
Click to collapse
You know, custom ROMs don't just appear out of thin air. Someone has to take the time to bring up a device and make it stable, and it's not an easy task. I would say to be patient and just accept the fact that there's no guarantee that this device will get custom ROMs.
lzgmc said:
If you're really at your wit's end, have you considered installing a GSI? I've tried Phh's AOSP w/ gapps, and once you register your device with Google, it works flawlessly (except safetynet/drm) and is a million times faster than stock. Or I'd be more than happy to take your device off your hands.
You know, custom ROMs don't just appear out of thin air. Someone has to take the time to bring up a device and make it stable, and it's not an easy task. I would say to be patient and just accept the fact that there's no guarantee that this device will get custom ROMs.
Click to expand...
Click to collapse
Any disadvantages with gsi besides safety net drm? Want to try gsi but this is new to me
Metconnect2000 said:
Any disadvantages with gsi besides safety net drm? Want to try gsi but this is new to me
Click to expand...
Click to collapse
Other than pictures from the camera being degraded compared to stock and having to install apps from the Play Store/changing a few settings in the Settings app, everything seems to work fine