yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] ezzie:
Any idea why the randomizer and splash screens will only show up in the left hand corner of the screen? I have the sprint diamond with the original rom. I've tried the earlier releases and the current 1.3 and they all show the same. It does randomize the splash screens and i have been able to add new screens and they are included in the rotation. If anyone has any ideas it would be greatly appreciated.

ezzie
[Windows Mobile Software Development] werD:
The problem is that Splash Screen Randomizer currently doesn't support Importing files for VGA devices. ie. it always scales to a max of 320x240(lame I know, but it was quick :) ). I have planned to release the next version with full vga support around Christmas. I'm currently studying for an MS exam scheduled for next week.. so it may be closer to the first of the year.

Until I do release the next version... to get around the small scaled image issue, you'll need to make the images yourself for your phone. The screen size for the diamond is 640x480 pixels. You can open any of the files that are in your splashes folder('my documents\Splashes') and resize them with paint.net or your favorite image editor. You can also drop any other .bmp or .png file into your splashes directory to add the image manually.

Hope this helps and be sure to check back soon for updates
[Windows Mobile Software Development] ezzie:
thanks! I loved your app on my mogul. Good luck with your exam!!

ezzie
[Windows Mobile Software Development] werD:
Updated to version 1.4

Ok guys, I have my new fuze and so i can get some practical testing going on. Ive updated SSR to scale dynamically so it works with VGA devices. It should scale well and work without a hitch on WVGA and the square phones out there too.

Updated to 1.4.0 on 01-26-09

Notable Changes

Major form factor support added(QVGA,VGA,WVGA[testers needed]). Screen layout and image importing is now dynamic

IO Mode switches on automaticaly on first run if your phone is windows mobile 6.0 or below (i.e < 5.2.19000)

OpenFile 2.0 included (my extended Mobile Practices codebase)

File attributes on default splash are adjusted to work better with IO Mode

Better error handling added

Lots of backend improvements and UI Tweaks

Richer UI coming soon

Im currently working with my host to get ftp up and going again so I can update the apptodate settings on the server. Until I do, ApptToDate will still show 1.3.0 as the newest version.

As Always, I really appreciate any feedback you guys can give me.

Enjoy
[Windows Mobile Software Development] ezzie:
It looks great! I have the HTC Diamond (Sprint). So far it works wonderfully and i have been messing around with it.:D:D
[Windows Mobile Software Development] werD:
Great! Glad to hear its working well for you. :D

Ive taken care of my ftp issues, so AppToDate users should now be able to download the most recent version as well next time they run apptodate.

Thanks
[Windows Mobile Software Development] chagass36:
Thanks :cool:
[Windows Mobile Software Development] chrisnz1947:
I have used this on my Kaiser and am just about to update to a HTC HD2, given the different screen resolutions do you think this will still work
[Windows Mobile Software Development] werD:
The hd2 uses a standard resolution with 192dpi. You should have no issues(let me know if you do). Enjoy your new phone:D
[Windows Mobile Software Development] nastradacha:
thanks , works great
[Windows Mobile Software Development] [★]:
Hi, I have this installed on my HD2 and it doesnt seem to be working. I know my splashscreens are the correct format because I downloaded them from someone off xda and they even recomended using your program. However whenever I soft/hard reset the phone, I just get the normal screens

Why is this? what am I doing wrong :(

[Also which splash screen does it change, the HTC one of the Winmo one?]
[Windows Mobile Software Development] werD:
Splash Screen Randomizer adjusts the Windows Mobile Splash Screen.

Be sure to run the program called Splash Screen Randomizer Settings (SplScrnRndStg.exe) Click the randomize button then reboot. You should have a new WM Splash Screen(if "use specific screen" is unchecked you will get a random one each startup).

Make sure your images are in the splashes folder. If they arent, try importing them from the "import/multi" screen.

Lastly if neither of those work(not likely), choose an image, then choose "replace default". Reboot, if that works, you need to select "IO/Mode" from the "Import/Multi" screen
[Windows Mobile Software Development] [★]:
Hi, its all working now, I noticed I had some really old version of the program lol. Thanks for the great work, lovin my new splash :p
[Windows Mobile Software Development] F!r3f0x:
I have tried to use this app on my HTC Leo.

Even I starded this app and chose a picture from \My Documents\Splashes\ the app crashed with a error.

Further my splashscreen at the start of the device is damaged. I only see a white blank picture nothing more :(.

Somebody can help to solve that?!
[Windows Mobile Software Development] werD:
What was the error?.. Please make sure you are using the most current version if you're unsure, click the "About" link inside of the app and tell me what version of Splash Screen Randomizer you are using.
[Windows Mobile Software Development] F!r3f0x:
Iam using the v1.4.0.20180 of this app.

My ROM is on v1.48.407.1 (71294) GER.

The error only says that in SplScrnRndStg.exe is an error.

The app is working now very fine but for example if I want to save the settings the app is crashing.

What Iam wondering in is that the splashscreen works pretty well although the app is crashing :).
[Windows Mobile Software Development] werD:
When the error happens do you see a details button(that should give you more informatin about the error)? / Does this happen after a reinstall? It sounds like a specific setting has an unexpected value or there is some sort of permissions issue. Without the error message it is very difficult to debug though.

There are 2 applications, one does the randomizing and sets the registry values(SplScrnRnd.exe), the other changes the settings around and resizes/imports files(SplScrnRndStg.exe).

If you keep getting the error after a reinstall and you get no error message, please go to the application folder and copy the .xml settings file there and paste it on here for me to review.

Im glad your screens are working, ill be even more glad when we find out why the app is crashing for you :)
[Windows Mobile Software Development] F!r3f0x:
I had reinstalled the application but the error appears further :(

Nevertheless the app works pretty well if I dont care that the app is crashing :D

the following error report I get if I click on "details"

bei System.IO.__Error.WinIOError()
bei System.IO.Filestream..ctor()
bei System.IO.Filestream..ctor()
bei System.IO.StreamWriter.CreateFile()
bei System.IO.StreamWriter..ctor()
bei System.IO.StreamWriter..ctor()
bei System.IO.File.CreateText()
bei SplScrnRndSg.SplScrnRndStg.CreateShortcutInStartUp()
bei SplScrnRndSg.SplScrnRndStg.SaveSettings()
bei SplScrnRndSg.SplScrnRndStg.mnuSave_Click()
bei System.Windows.Forms.MenuItem.OnClick()
bei System.Windows.Forms.Menu.ProcessMnuProc()
bei System.Windows.Forms.Form.WnProc()
bei System.Windows.Forms.Control._InternalWnProc()
bei Microsoft.AGL.Forms.EVL.EnterMainLoop()
bei System.Windows.Forms.Application.Run()
bei SplScrnRndStg.SplScrnRndStg.Main()
[Windows Mobile Software Development] werD:
Thanks, thats exactly what I needed! I'll correct the error in the next release.

It is crashing when either trying to save or remove a shortcut to the file "\Program Files\SplashScreenRandomizer\SplScrnRnd.exe".. It is trying to add/remove the shortcut to here.. "\Windows\Startup\SplScrnRnd.exe.lnk" If you are currently getting a random splash screen when you boot then it is having trouble removing or replacing the fie. If your splash screen only changes when you do it manually, it is having trouble adding the file to the startup folder. You can add it manually(its in "\Program Files\SplashScreenRandomizer\SplScrnRnd.exe") Just copy it, and paste a shortcut in Startup

Thanks again for the error details, Ill make sure the permissions on the startup folder are handled properly in next release.
[Windows Mobile Software Development] ady_uaic:
I'm in as a tester for WVGA.
[Windows Mobile Software Development] peacekeeper03:
Nice App!

Thx for your work
[Windows Mobile Software Development] abumaha:
how work on android for hd2
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Natsu2000:
Hello

Since I've installed the CarbonRom on my phone I can't use the camera anymore.

On the backside I have only blackscreen and with the front camera I can see me but when I try to take a picture the application freezes.

Does anyone know how to fix this issue?

Thanks in advance
[General Questions and Answers] Horatio.:
Hello, Can somebody upload a firmware for Qphone 7,1 It was bought in Italy and now its just in boot loop....

CPU: MT6735

SW: 8A00(0000)

VER: CA00

Flash Type: EMMC

Flash ID: EMMC

Flash Size: 0x3A3E00000->14910,0M

Flash Name: EMMCFlash
[Galaxy S 5 Q&A, Help & Troubleshooting] drewcu:
So I have posted before without any replies and am still seeking help...

I know there are others out there in the same situation as me:

On an Unlocked VZW bootloader

On Verizon Wireless 4G LTE in the US

Trying to run a Custom ROM on their phone

But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.

What I have tried:

AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)

Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs

Changing APN settings to match the stock VZW settings exactly

Flashed new VZW APN files from an ltefix.zip file I found on XDA

Changing CDMA to be Home and not just Automatic

Changing from Global to CDMA/LTE+EVDO

Went to the Verizon store and got a new SIM card

Booted up without SIM and powered off; then inserted SIM and booted up again

Tried different Modem/Non-HLOS versions like QC2 and QL1

Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings

Added some lines from the stock VZW Build Prop to Custom ROM Build Prop

Removing HD Voice/VoLTE from my Verizon account

Avoided installing any apps after flashing a Custom ROM to see if the problem remained

Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.

This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.

But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!

Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?

Thank you very much!

Drew
[Galaxy S 5 Q&A, Help & Troubleshooting] james_rokr:
Worry not, I have the same problem on an international unlocked G900F.

The problem is inexistent on latest stock firmware, but it is present on the Oreo custom roms i've tried so far, such as lineageOS, CrDroid, Resurrection Remix.

The Only Workaround i've found so far is to enter the info menu on lineage os, dialing *#*#4636#*#* and turning off radio and On, on the Device Information menu, also updating SMSC proved to work on a few ocasions.

Needless to say, I've tried EVERYTHING this forum suggest, such as full wipe from stock recovery and running latest stock for a few days, or even flashing the latest baseband alone, but it doesn't work. I've read some interesting post about this issue on a Xiaomi Oreo device, and i'ts supposed to be an issue of Oreo roms and the way it measures the signal bars, but no fix so far.

Anyway if anyone finds a way to fix this annoying issue on the next Lineage16 I'd be grateful
[Galaxy S 5 Q&A, Help & Troubleshooting] deli5:
Having similar issues with G900V on verizon. I've tried many ROMs old and new, latest LOS16 / RR. also I've tried other network fixes as in original post, and different hardware. I have a few of these, all EMMC15 unlocked bootloaders

Are there any developments here?

Weird thing is, SMS/MMS/calling 'works' two blocks away but I always have the 'roaming indicator off' no matter where I am, and there is a delay in sms IF it work at all. Also, this just started last month. (?) I've been using LOS 16 without network issues for a few months prior. It's is possible Verizon has changed something in the service in my area? I went to verizon to verify compatibility and try a new sim, they were mostly useless but otherwise confirmed that the g900v was on the 2020 list of compatible phones. been trying older builds (including starting fresh on the one that was working last month) but nothing but using stock QL1 magisk rooted ROM works - and that one works very well, reliable, and fast. everywhere. grrr, I'm not ready to retire my fleet of s900v, and I would rather retire them than go back to MM if this can't be fixed.
[Google Pixel 2 XL Questions & Answers] jordan.harris01:
Just a quick question, but will I get security updates on my Pixel 2xl the day they're released (ie. today) while being on Koodo? Or will they block it and I'll need to flash it myself?
[Google Pixel 2 XL Questions & Answers] v12xke:
I don't know anything about the Koodo MVNO, but Security updates are always on a phased roll out schedule by IMEI over the course of 2-3 weeks. You could get it today... or 3 weeks from now, or never. Maybe this will help you decide. The full factory image for September is waiting for you HERE right now. Or you can just read about it HERE.
[Google Pixel 2 XL Questions & Answers] Deleted member 5445131:
Do you know if AT&T Prepaid plans delay updates?
[Google Pixel 2 XL Questions & Answers] equlizer:
.......sorry posted on wrong topic.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
He's saying that it's not carrier controlled for the updates. So the answer would be no. If you can't wait a day or few, learn to sideload the OTA. It's literally to commands and it's installed in a few minutes. That what I just did this morning.
[Google Pixel 2 XL Questions & Answers] acheney1990:
I'm on Koodo but bought directly from Google. Got update OTA same afternoon it was released.
[Essential Phone Guides, News, & Discussion] johnny8910:
https://www.essential.com/developer/current-builds

Also, just received it on my phone this very moment.
[Essential Phone Guides, News, & Discussion] dirtsky:
Downloading now! Came to post this exact thing.
[Essential Phone Guides, News, & Discussion] johnny8910:
UPDATE

Screen shot for those interested
[Essential Phone Guides, News, & Discussion] mookiexl:
changelog?
[Essential Phone Guides, News, & Discussion] Caltinpla:
Check the screenshot one post right before your!
[Essential Phone Guides, News, & Discussion] ziddey:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md

edit: hey it works
[Essential Phone Guides, News, & Discussion] sruel3216:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
[Essential Phone Guides, News, & Discussion] oracleoftruth:
If I try to unroot by restoring images it says "Stock backup does not exist!"
[Essential Phone Guides, News, & Discussion] ziddey:
I believe you'd fail the OTA if you have an altered boot, but you can try.

I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing

You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.

Drop a shell.

Determine current boot slot: getprop |grep boot.slot

Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)

Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.

Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.
[Essential Phone Guides, News, & Discussion] p51d007:
Nice...4 days in, and patched with the security update already.
[Essential Phone Guides, News, & Discussion] sruel3216:
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.
[Essential Phone Guides, News, & Discussion] robertbarber:
For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.
[Essential Phone Guides, News, & Discussion] gorm:
Anyone try to Fastboot install the Sept update?

Tried 3 times and the screen was unresponsive every time after booting to setup

Finally went back to last months original P release and everything was as normal and updated from there...........
[Essential Phone Guides, News, & Discussion] naeledge:
Just installed patch. Scrolling feels so much better, especially when scrolling slow.
[Essential Phone Guides, News, & Discussion] beard805:
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!

I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to

get my screen back.

Really weird stuff.

EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/

I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.

Thanks!
[Essential Phone Guides, News, & Discussion] jon_ybanez:
my PH-1 is no longer recognizing my T-Mobile SIM.

i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.

the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.

i'm currently reinstalling August 2018 Release via fastboot & see if that helps.

EDIT:

August 2018 Release resulted in no touch response & unable to progress through setup.

giving June 2018 Release (Oreo 8.1 ) a try via fastboot.

i just want a working phone back
[Essential Phone Guides, News, & Discussion] beard805:
Hey Jon,

Go ahead and take a look at my post I just made above yours. It might be able to help :)

Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.

Thanks!
[Essential Phone Guides, News, & Discussion] jon_ybanez:
thanks for the info.

touchscreen works again but i still get an Invalid SIM message

i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community

thanks in advance
[Essential Phone Guides, News, & Discussion] beard805:
Sadly, I don't know much about the SIM side of the issue :(

Hope someone with more knowledge can chime in!
[Essential Phone Guides, News, & Discussion] ziddey:
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing

You can try to dd them:

dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2

Would be a good idea to backup your current images

from https://xdaforums.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135
[Essential Phone Guides, News, & Discussion] jon_ybanez:
thank you for the files.

if you could point me towards a guide that instructs me on what to do, i'd appreciate it
[Essential Phone Guides, News, & Discussion] oceansoul:
TWRP did not freeze, it was the loss of touch screen support on the lastest release, just use a ota mouse
[Essential Phone Guides, News, & Discussion] ceelos218:
Looks like Essential locked down Sim cards? my verizon doesnt work anymore.. sprint sim seems fine.
[Essential Phone Guides, News, & Discussion] innoth:
Updated. But still not have notch setting [emoji26]
[Essential Phone Guides, News, & Discussion] Dashwood Foxe:
Letting you guys know if you plan on rooting from a full wipe, twrp's touch control are completely bork and non responsive!
[Essential Phone Guides, News, & Discussion] stryver:
I'm having this issue. Still rooted with fastboot but I hate not having the option to use twrp.
[Essential Phone Guides, News, & Discussion] jon_ybanez:
well, downgrading wasn't able to restore the ability to use my T-Mo SIM.

I reinstalled today's update via fastboot followed by the patched_boot.img that beard805 mentioned.

Magisk was able to be installed & root was obtained.

After learning how DD works, I pushed the 2 modemst files provided by ziddey.

A quick reboot of the phone and....I still get Invalid SIM.

i'll be pulling my SIM out & letting the phone sit on WiFi overnight.

I'll reaccess this tomorrow and hope that maybe it'll magically fix itself & allow me to use my phone as a phone again.

thanks to everyone that dropped a piece of their knowledge on this issue
[Essential Phone Guides, News, & Discussion] ziddey:
Hmm maybe the partition doesn't actually write properly with dd. You can downgrade to an old bootloader (nougat, maybe even an early one) and flash the modemst using fastboot.
[Essential Phone Guides, News, & Discussion] bmg1001:
I wrote up a quick Reddit post regarding the touch issues with TWRP. https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
[Essential Phone Guides, News, & Discussion] PITTAR:
how to install this september update on rooted essential ?
[Essential Phone Guides, News, & Discussion] stefan.pilsu:
Hi there,

I have active slot b.

boot_b.img from you placed in PH-1 Internal shared storage....

...wich is the corect comand to flash in adb shell ?
[Essential Phone Guides, News, & Discussion] kenbrownstone:
Any one get a fix income on the invalid sim? Unlocked not rooted
[Essential Phone Guides, News, & Discussion] jon_ybanez:
well, i'm out of ideas to get my SIM to work again.

- I flashed down to Nougat (build NMJ32F)

- successfully flashed the modemst images

- updated to PPR1.180905.036 via OTA but I still get an Invalid SIM message