Database Users

[Q] long time watcher and rom user. first time poster.

Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel

Tell us what your problems are here.

1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium

Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple

Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.

shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel

New Nexus 6P User, problems out of the gate

So like the title says, I'm a new Nexus 6P user, and I had problems out of the gate.
I bought the device 2nd hand from a guy off craigslist, after my S6 edge started over heating after I had the screen replaced (don't buy Samsung "edge" phones, I know your careful, but on the off chance you drop it, your in a world of trouble).
I tested the phone, before I bought it, it appeared pretty much brand new, everything worked. When I got home, and hard reset it again for good measure all hell broke lose.
After a hard reset the phone wanted to update to build 19 something. After the update and a reboot, the phone app kept crashing before I could finish the setup process. The only thing I could do is factory reset it again. This appeared to clear up that problem. I did the near by device thing, and restored it from what Google could find out about my S6 edge. I wish it was more of a restore like what you can do in the iOS world, but it's better then what we had before so it's cool. I noticed that Chrome would crash everytime you tried to use it only in less I uninstalled the update. After I got the phone to the point where I wanted it, I thought I was free in the clear. When I started trying to use music apps, they all crash. Apple Music, Spotify, Soundcloud. Then I noticed YouTube also crashed the same way. When I tried to make a phone call, the phone app would crash too... So the phone was useless. I downloaded the SDK and the most current build which I think was 20 something. I followed a guide on here and formatted the phone reinstalling everything around build 20. The only thing this fixed was the phone issue.
I could now make phone calls without it crashing, but I was in the same boat with some applications working, and the same ones that didn't work not working. I flashed this phone 5, or 6 times, with the last time me formatting the userdata. I read that it wasn't a good idea because it could lock me to only 32GB ( I had a 64GB version), but after I did the flashing along with the usedata format, I still had 64GB of useable space, however I still had the same issue with the same types of applications crashing. I tried older builds, same issue (also the older builds all had the problem with the phone app crashing to the point that the phone wasn't usable).
I ended up sending the phone to the manufacturer, which appears to be in the same metroplex I live in. Hopefully they can find a hardware problem under warenty and fix it. I'm making this post to see if anyone else ran into similar issues, and if anyone knows if this is a hardware build issue, that was hopefully resolved.
I'm sorry to be so long winded...

Is the phone rooted and running a custom ROM?

Pappy35 said:
Is the phone rooted and running a custom ROM?
Click to expand...
Click to collapse
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)

vmiyoshi said:
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)
Click to expand...
Click to collapse
How much did you pay for it?
Sent from my LG-H830 using Tapatalk

RidinNerdy said:
How much did you pay for it?
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
I paid 4 for it...

Internal Clock Issue

I have a Moto G4 Play, I believe it is XT1607, purchased straight from Motorola. I'm running Squid's CM with the stock kernel. Overall it works great, but I have a minor annoyance: when I first turn the phone on from being completely off, the time and date is always completely wrong. I mean off by MANY hours and minutes (like I don't even know where it gets this time from), as well as like 20-30 days. Obviously this isn't much of a problem since time syncs with my cellular network after the boot is complete, but this still bothers me slightly. Every other phone I've had kept the time accurate even when it was off. Is this a ROM issue or a G4 Play issue? Anyone else experiencing this?
*Note that I don't remove the battery when the phone gets turned off.

It's nothing tho. Connect to WiFi or use the latest ROM

I have the same problem in my Moto g4 play. Any suggestion?

It's tied to your Recovery. TWRP goes off whatever the hardware time is. My phone was initially in Mountain or Central time, but even with it set to Pacific Time it's off by several hours and minutes. The only way to fix it would be to modify whatever the heck smartphones use as BIOS/CMOS.

mkollersms said:
It's tied to your Recovery. TWRP goes off whatever the hardware time is. My phone was initially in Mountain or Central time, but even with it set to Pacific Time it's off by several hours and minutes. The only way to fix it would be to modify whatever the heck smartphones use as BIOS/CMOS.
Click to expand...
Click to collapse
Maybe this is something Moto removes as a result of unlocking bootloader. There's no possible way this glitch exists on stock firmware.

jasonmerc said:
Maybe this is something Moto removes as a result of unlocking bootloader. There's no possible way this glitch exists on stock firmware.
Click to expand...
Click to collapse
Well, I would gather that the clock applications (CM has two) would be storing that information either in the memory space directly or not at all. That's the only way I could see that file being recreated on boot. As far as I can tell, phones don't have button cell batteries in them, so don't ask me how the Recovery manages to keep time.

jasonmerc said:
I have a Moto G4 Play, I believe it is XT1607, purchased straight from Motorola. I'm running Squid's CM with the stock kernel. Overall it works great, but I have a minor annoyance: when I first turn the phone on from being completely off, the time and date is always completely wrong. I mean off by MANY hours and minutes (like I don't even know where it gets this time from), as well as like 20-30 days. Obviously this isn't much of a problem since time syncs with my cellular network after the boot is complete, but this still bothers me slightly. Every other phone I've had kept the time accurate even when it was off. Is this a ROM issue or a G4 Play issue? Anyone else experiencing this?
*Note that I don't remove the battery when the phone gets turned off.
Click to expand...
Click to collapse
Hey bro! I have this phone too!

triggerlord said:
Hey bro! I have this phone too!
Click to expand...
Click to collapse
Good to hear from you again. Is your internal clock being stupid as well (assuming you flashed TWRP/ROMs and such to it)? If so what exact model do you have?

jasonmerc said:
Good to hear from you again. Is your internal clock being stupid as well (assuming you flashed TWRP/ROMs and such to it)? If so what exact model do you have?
Click to expand...
Click to collapse
I have the XT1607. I bought it off Amazon. I flashed AOKP + Gapps and the clock seems to work fine on mine.

Essential ph1 twice random reboot

Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.

I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?

It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.

Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk

If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.

Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.

Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.

If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?

I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.

Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?

Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...

Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41

Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.

Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds

Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.

That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.

Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.

Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.

Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.

Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.

OOS 10.3.x - Constant random crash to black screen then spinning dot

I am at wits end. Here's how my situation has unfolded:
- Was running OOS 10.3.2 international, bootloader locked stock on a T-Mobile 6T (been running solid since 9.0.11 MSM hack early last year, updated progressively as the "System Updates" have appeared)
- No customization or tweaks
- Starting late last week, phone has been (seemingly) randomly crashing to black screen, then to spinning dots, like its booting
- I have to Vol up + power to turn off, then reboot
- I captured a logcat of the crash, which may be useful to someone, I just see the system handling a notification, then a system level ANR happens, taking out the core system processes?
I have tried:
- Google/OP backup -> factory reset -> restore account, apps, calls, sms and settings -->> still crashing
- OP backup -> factory reset -> add as fresh account, restore OP bu apps, calls, sms and settings -->> still crashing
- OP backup -> MSM downgrade to 9.0.11 -> unlock bootloader -> install TWRP, Magisk, TWRP install 10.3.2 international -> fresh account, restore SMS messages, etc
After the last attempt, ran all morning without crashing (yay!), proceeded to utter the words to my son ,"hey, fixed my phone, no crashes!", phone crashes 5 minutes later
Then I thought, "well I just signed in to Firefox sync, maybe that's it??", uninstall Firefox. Hour later, crashes during a phone call.
Okay, then thought maybe its something goofy with stock kernel? Install Omega kernel. Crashes 2 hours later on another phone call.
It also seems to crash fairly consistently in my pocket, and I have noticed "Pocket Mode" does not work (overlay doesn't appear when covering proximity sense; sensor works, tested with an app)
Am I experiencing a flaking mobo or some other hardware issue? Please tell me no, I am at 16 months with this phone, so factory warranty is out (and 6 months to go on my payment plan/offer).
Before I try LOS 17.1 (and probably still get crashes :silly, thought I'd try asking for insight here. I have tried googling for similar issues and searching forum threads, but no dice. Thanks!

Well, I have an update here. I turned off "Pocket Mode" last night for giggles, and lo and behold, I have 20 hours up time with no crashes. Proximity sensor works, took several calls today and screen turns off when covering it. Also put phone in pocket regularly to test, no crashing.
Hopefully this helps anyone else with this strange issue. Kind of sucks that I am going to potentially butt call people, but, less pocket time these days while we're all stuck at home (COVID-19 "stay at home", for those reading this post years from now wondering what the heck I'm talking about).

Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.

hondoslack said:
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
Click to expand...
Click to collapse
LOS 17.1, random reboots persist . Thinking my phone is toast...

hondoslack said:
LOS 17.1, random reboots persist . Thinking my phone is toast...
Click to expand...
Click to collapse
Try this port rom from op7..
Working great ..easy to install and super stable
https://forum.xda-developers.com/oneplus-6t/development/rom-oneplus7-beta-2-t3971383

have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...

sderaps said:
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
Click to expand...
Click to collapse
Unfortunately I've pretty much confirmed mine was a bad motherboard. I bought a used one off eBay, and installed it yesterday. Phone is running so much better, no more crashes, and proximity sensor is working properly again.
If you want to give LOS 17.1 a shot, here's a good place to start: https://forum.xda-developers.com/oneplus-6t/how-to/guide-installing-lineage-t4075955
I found it mostly a frustrating ROM, as fingerprint and face unlock don't work. Call me lame, but I absolutely love picking my phone up, looking at it, and having access immediately. Then there's all the apps that hook into the fingerprint for quickly unlocking that you can no longer leverage (the unlock part, not the app). Anyway, up to you.

Since I upgraded my op to 10.3.2, my proximity sensor IS not working.