yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] DssTrainer:
Alternative to using the carrier file:

1. Start->Settings->Connections->Connections

2. Under "My ISP" Choose "Add a new modem connection"

3. Enter "Sprint PCS" as the name

4. Enter #777 as the number

5. Leave the User/Pass/Doman empty

6. Click "Finish"

7. After the first time the phone tries to connect, it will ask again for a login. Leave it blank and check "Save Password". It should connect now and won't ask for the password anymore.
[Touch CDMA Windows Mobile ROM Development] SeeBeatty:
^^Yes, but there are other aspects of having a carrier cab installed that you may want. It's not just the data,... can you dial 911?
[Touch CDMA Windows Mobile ROM Development] rmarshll:
Vetvito, Would you mind sharing how you edit and customize your Start Menu Button in some of your ROMS, This is Something I have always wanted to learn but I cannot find the information anywhere.. It would be really handy to make differnt themed ROMS.
[Touch CDMA Windows Mobile ROM Development] asenduk:
keyboard skins

hey Vet

on your future kitchen release, can you include your black or gray keyboard skins similar to your black pill and schwartz? none of the keyboard skin cabs i have works... or better yet, a kitchen with the black pill and schwartz theme... gotta love them themes!! :D
[Touch CDMA Windows Mobile ROM Development] quserpa:
V1.3

Vet: V1.3 is flying- Great ROM once again- Thanks!
[Touch CDMA Windows Mobile ROM Development] dealpapa1:
The best rom I have ever used.
[Touch CDMA Windows Mobile ROM Development] asenduk:
1.3

just saw that you uploaded 1.3... wooohooooooooo!!!!!! :D

thanks Vet!!!!!!!!
[Touch CDMA Windows Mobile ROM Development] boggsie:
I'll be honest and admit that I'm still trying to get a handle on what some (most ?) of this new raphael stuff actually does.

The stuff that I normally use is working great, but it is difficult for me to gauge whether or not ShareDLL, DShow & ConCurrenceMGR are working as expected, when I'm not really sure what, if anything they do for the Vogue plaform.

However, I do appreciate the opportunity to evaluate and the work by VetVito is top-notch. Thanks for the effort.

Best regards,

-boggsie
[Touch CDMA Windows Mobile ROM Development] vetvito:
Those items that you listed are actually OEM items in the Vogue, these are just updated.
[Touch CDMA Windows Mobile ROM Development] asenduk:
your name?

hey Vet

i followed your instructions on the 'read first' file. i opened the file located in 'your rom' with notepad but i don't see 'your name' :confused: can you help me out?
[Touch CDMA Windows Mobile ROM Development] rmarshll:
Vet, if you dont have time to answer the above question.. could you at least lead me in the right direction as to where I can learn to change the Start menu look like in some of your Roms?
[Touch CDMA Windows Mobile ROM Development] vetvito:
Dozens of threads on that, but here you go
[Touch CDMA Windows Mobile ROM Development] rmarshll:
I have tried searching. I dont really know what Im even looking for.. I dont want to used Wisebar do you have a good thread that will explain this.. I have only seen your roms and JDs roms over at PPCGeeks that have this cool little touch and I would like to learn how to do it.

Think I found something.. Thank you..
[Touch CDMA Windows Mobile ROM Development] SprintGuy765:
help

I'm getting an error

rom folder does not exist

ROM\XIP\

what does that mean

and could anybody share their selection txt (1.3)

thanks alot
[Touch CDMA Windows Mobile ROM Development] stylz3:
Hey Vet. I ran your latest kitchen release and manager to get it to load, but when I first ran it I add some other OEMs that I hava saved on my PC to customize it to the way I like, but got some errors during build OS like "couldn't create device .hv and user .hv. I still finished creating the ROM, but bricked my phone after flashing it. Luckily was able to unbrick it following a tutorial at geeks and got it to back to normal. I ran build OS again but didn't include any of the OEM packs I have and everything is fine now. No errors no bricks.

Was there anything else I was supposed to do besides just dropping the OEM in the OEM folder that would of prevented the error?
[Touch CDMA Windows Mobile ROM Development] boggsie:
HELP

EXPLICIT INSTRUCTIONS

I haven't tried it ...

Best regards,

-boggsie
[Touch CDMA Windows Mobile ROM Development] vetvito:
Whenever it does this, go to Temp, and read the very bottom of the text file. It should say something along the lines of "Error, Failure to parse Line #..." and then it gives the .rgu. Find the .rgu, and open in a text editor and go to that line, and you should see your problem.

Or upload them and I will take a look.

You need the .Net packages, check a few pages back for the links.

That is all you need, I included the signing tool in the kitchen.

Problem solved.
[Touch CDMA Windows Mobile ROM Development] computerjunkie:
Vet

I loaded 1.3 very early this morning. This after noon, when i looked at my phone, I had 1 unread text message. when i clicked on it, i saw no text messages in my inbox.

Then I sent myself 2 text messages from the sprint website, and now I have 3 (1 + the two i just sent) unread text messages but still no text messages in the inbox.

Also there was no notifications sound. I checked the sound and it is enabled and works when I press the "play" button to test the sound.

Anyone else experiencing this? I'm trying to do a backup right now and then will do a hard reset and retest this problem and edit this post as needed. Please help!

EDIT:

I just backed up everything using pim backup and opened the Messaging file: No text messages in that file only email. Maybe the text messages are being placed in the wrong spot in the database? I will erase my email, and redo the backup and see if there is anything in the messaging file of the backup then.

EDIT 2:

A hard reset seems to have fixed this problem. I wonder what caused it in the first place...Anywho...problem seems fixed by hard reset.
[Touch CDMA Windows Mobile ROM Development] computerjunkie:
I did discover a new problem though. I have seen this problem with other ROMs so it's not Vet exclusive. But since Vet is a genius, I thought maybe he could help us all out.

Is anyone seeing text messages disappearing when you do a soft reset (with the stylus)?

At first I thought I was going crazy but I just tried it directly after a hard reset to make sure I was sane.

Steps:

1. I sent myself a text message from the sprint website. Text message arrived fine.

2. I read the text message then did a soft reset with the stylus

3. After reset, the message seems to have disappeared from the text message inbox.

I've reproduced the above several times in the last 5 minutes. Vet, any ideas?
[Touch CDMA Windows Mobile ROM Development] SprintGuy765:
Please

Hi, Vet I love your rom.

I was wondering if you could make a rom like Schwartz Cleaned except with the latest build (raphael)

thanks alot
[Touch CDMA Windows Mobile ROM Development] vetvito:
Did you use a pim from a different build? Pim back up, SPB Back up?

If so, pim's from different builds dont always work. Its best to sync your contacts, tasks, notes, etc.. with a server. I use Funambol, its free.

I chalked it up as a 6.1 bug. Browse the forums and you will see what I'm saying. It hasnt happened to me lately.

It will be updated when I come across a untouched 20XXX build.
[Touch CDMA Windows Mobile ROM Development] computerjunkie:
Well I used a backup from v1.0. What's funny is that I used this same backup to restore my contacts, etc after the hard reset and it's been working fine since. Maybe I messed up a setting, i'm not sure. But to clarify, it's been working fine ever since I did a hard reset.
[Touch CDMA Windows Mobile ROM Development] LycanNyc:
So to not be confused whats the latest ROM so far? JULY 5 ?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] hrdlw:
Just the topic name. Is it possible? Can any develloper actually do this? Im just curious, and it can be really sick.
[Xposed General] VincentJoshuaET:
Pixel Experience had this feature to actively listen to the music currently playing in the surroundings, exactly like the Google Pixel feature. For some reason, it is removed in an update. Is this possible with Xposed?

P.S. I'M not asking for the ambient music ticker that exists on many other custom ROMs.
[Xposed General] mattgyver:
Thread closed. As per the [Read before posting] Module-specific questions/requests do NOT belong here! sticky, your question should be asked in the following thread: https://xdaforums.com/xposed/modules/index-xposed-modules-collection-post-t2327541
[Asus ZenFone Max Pro M1  Questions & Answers] su-do:
I think my audio IC is broken, the right channel (through 3.5mm jack) only outputing (white/pink) noise..

The speaker(buzzer) seems ok,, bluetooth also sounds clean.

But only R channel audio from 3.5mm jack is problematic.

It happen after I accidentaly connect the rca input to the power amp output...

Do you guys know the number? Its a NXP chip right?

I can't find it online.

Or, is there any compatible IC series available?

Should I try change the daughterboard first?

Thx in advance.
[Android Q&A, Help & Troubleshooting] 174gjc:
As everyone probably knows, the standard way for rooting a phone with an unlockable bootloader is to put it into what is known as the unlocked or "red state" (in AOSP parlance), which disables the cryptographic chain of trust to allow for unapproved ROMs or modifications to the standard ROM to be made, and then flashing a new recovery or directly flashing a ROM with Magisk included. I have a couple of questions in regards to this process that I can't seem to find proper answers to elsewhere on the internet, and I was wondering if anyone here might know the answers to them.

1. To what degree are rooted phones susceptible to evil maid style attacks, where the recovery partition or the bootloader itself is altered to allow an attacker to gain access to the phone next time it starts up? I assume that Android precludes the idea of directly unlocking phones which you gain physical access to when locked through filesystem or disk encryption, but probably doesn't prevent the substitution of the regular boot.img with a malicious alternate boot.img.

2. What is the process for putting phone into the "yellow state", in which the bootloader is locked but a custom signing key is used to prevent alterations to phone?

3. What implications would locking the bootloader whilst rooted have on applying OTA updates via the standard method (reflashing with Magisk) or through an alternative like Chainfire? What would be the easiest way to stay up to date with security patches?

4. To what degree is Magisk secure against unauthorized privilege escalation attempts? Is there a way for a malicious application, or exploited application to achieve root without the user explicitly authorizing it via a prompt?

I'm primarily asking these questions because I think that users that want root shouldn't have to compromise on security, and I think that the technical means for achieving this exist, but aren't properly documented. I would also assume that there are others that have a similar interest in this topic, so that's why I'm posing these questions to you.
[Android Q&A, Help & Troubleshooting] 174gjc:
Bump.

Bumping this thread as it never got any replies, and has been up for nearly a month now. My apologies to any threads that got pushed down because of it.
[Samsung Galaxy M30s Questions & Answers] Dv1101:
Wanted custom roms to be developed..............:cowboy:
[Samsung Galaxy M30s Questions & Answers] ravisrma:
yes
[Samsung Galaxy M30s Questions & Answers] pabgar:
YES YES YES and for triple time YES. We should pray to God OF Developers for custom roms.
[Off-topic] jabberman:
I own a sony ux (http://www.sonystyle.com/webapp/wcs...&productId=11040489&SR=sony_search_seo&SQS=ux)

And I also have a sim card in it so I have Internet where ever I go. I was wondering if anyone knows if its possible to make outgoing calls using the AT&T Network and my sim card? Not voip, but like a cell phone.

I see that someone is working on using a skype dialer and an iphone skin to create a phone, but not sure if this is what I am looking for.

http://www.micropctalk.com/forums/showthread.php?t=2288&highlight=uphone

Let me know if I am way out of bounds here....

Thanks

Jim
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Introduction

LineageOS 17.1 is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

What works

Calls, SMS, Mobile Data

Camera

NFC

WiFi

Bluetooth

Torch

Sensors

GPS

SELinux Enforcing

HWC​

What doesn't work

IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.

WiFi tether (hotspot) not functional (fixed in 21/01/2020 release)

HD headsets in call not working (fixed in 21/01/2020 release)

NFC HCE (GooglePay etc) fixed in 07/03/2020 release

You tell me!
​

There are still quite a few features that are not yet completed for LineageOS 17.1, these are not bugs this is a beta release.

Any hardware related issues will be ignored if you do not provide:

a) Logcat

b) proc/last_kmsg

c) data/tombstones

d) dmesg

Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications

Installation

Install the latest TWRP (Available Here)

Make a full backup (just in case something goes wrong)

Do a full wipe (Cache, Data, System)

If this is your first time on a LineageOS ROM format data

Download the latest LOS build and transfer it to your phone

Install LOS

If you are installing GApps do it at the same time (preferably in the same install queue)

And finally boot, the first boot can take several minutes as it optimises all the apps

Do NOT install the TWRP app when prompted, this will cause a bootloop
​

Downloads

Latest official releases HERE

Latest unofficial releases HERE

OpenGapps HERE

Flashable recoveries: HERE

TWRP is availableHERE

Magisk is available HERE
​

Thanks

@Stricted

@l-0-w

@sekil

@alexax66

@macs18max (BT call audio fix)

@Borduni

All the testers on the Discord group (https://discord.gg/8fp9cr7)

And all others who have contributed to the Exynos projects past and present
​

A special thanks to my donors

Markus Anders

@D4ND310

@epicwilmo

@tyson

@thebinf

@Herti

@pixelou

@xavier66

And any that I missed :D
​

XDA:DevDB Information

Lineage OS 17.1 for A3 2016, ROM for the Samsung Galaxy A Series

Contributors

danwood76, stricted

Source Code: https://github.com/LineageOS

ROM OS Version: Android 10

Based On: LineageOS

Version Information

Status: Beta

Created 2020-01-17

Last Updated 2020-05-29​
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Unofficial change log below:

Changes in the LineageOS 16/05/2020 release:
[INDENT]-Fixed mediaserver shim to solve boot crash introduced by last update
- Synced to latest LOS[/INDENT]
Changes in the LineageOS 13/05/2020 release:
[INDENT]- Fixed ringtone routing when headset is plugged in (thanks @stricted)
- Synced to latest LOS (including May security patch)
[/INDENT]Changes in the LineageOS Recovery 13/05/2020 release:
[INDENT]- Synced to latest source
- Added my signing keys to the zip verification function
[/INDENT]Changes in the twrp-a3xelte-3.3.1-0-danwood76 release:
[INDENT]- Synced to latest TWRP 8.1 source
- Added selinux labelling to system_root to fix broken backup restore
[/INDENT]

Older changes listed below:

Changes in the 12/04/2020 release:
[INDENT]- Disable rounded corner animations (thanks @dariotr)
- Cleanup overlays (thanks @dariotr)
- Switched to new BSP to solve licensing issues (thanks @stricted)
- Synced to latest LOS (including April security patch)
- Uploaded LineageOS recovery
[/INDENT]

Changes in the 12/03/2020 release:
[INDENT]-Added mounting of ext4 formatted SD cards
-Synced to latest LOS (including March security patch)
[/INDENT]

Changes in the 07/03/2020 release:
[INDENT]-Fixed NFC HCE (Google Pay should now work)
-Synced to latest LOS
[/INDENT]

Changes in the 29/02/2020 release:
[INDENT]-Disabled WiFi MAC randomisation
-Synced to latest LOS
[/INDENT]

Changes in the 16/02/2020 release:
[INDENT]-Switched to new HIDL power HAL
-Synced to latest LOS (including February security patch)
[/INDENT]

Changes in the 10/02/2020 release:
[INDENT]-Fixed Bluetooth audio config
[/INDENT]

Changes in the 08/02/2020 release:
[INDENT]-Re-enabled SELinux (had it disabled during testing)
-Fixed some of the bitrates in the audio config (fixes the robot voice in whatsapp messages)
[/INDENT]

Changes in the 07/02/2020 release:
[INDENT]-Fixed GPSD location in RIL blobs (thanks @alexax66)
-Synced to latest LOS
[/INDENT]

Changes in the 21/01/2020 release:
[INDENT]- WBS BT calling is fixed
- WiFi hotspot fixed
LOS Updates including:
- Ambient display settings now visible
- System profiles
- Dark mode fixes
[/INDENT]

Changes in the 17/01/2020 release:
[INDENT]
[*]Initial release
[/INDENT]
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Reserved
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Well done! I'll probably try it out too.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Toemmel:
Hi danwood76,

thank you for LOS17!

I´ve just installed installed it but it doesn´t start. i can only the see the boot animation and nothing more happens.

I´m waiting now about 1 hour ....

What can I do now?

Thank you for your work so far!!!!

Regards

Toemmel
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] gamefreak61:
Hello Dan,

Just installed this rom with Opengapps 10 BETA pico and Magisk 20.3. Got it up and running within 5 minutes, clean flash.

Haven't found any error on installation, running very nice.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Hi!

Just tested it. Everything I tested worked fine so far. Switched back to my backup of LOS 16, as I am still waiting for the official release which should arrive soon I hope. Don't want to setup my phone from scratch several times.

Thanks for all your efforts!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
Congratulations Dany just installed and everything works for me is perfect, the problem I found was only in the gapps, he does not install the error. but LOS17 is perfect. my model is a310m
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
How did you install?

You won't be able to update from official builds (without a resigning script and some luck)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I tested the latest Pico and nano opengapps beta from the link in the OP and both work fine.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
The mistake was mine, I was installing the gapps along with LOS17 I did the separate installation and everything worked out. thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Ok, The order is important.

1st ROM

2nd Gapps

3rd Magisk

Good that it is now working!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Johnpson:
Thanks thanks man I thought my a3 was abondond in 2020
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Toemmel:
I was in your official LOS16. So I can't update to unofficial LOS17?

Or did I misunderstood something?

Thank you for yozr work that you did so far!!!!!

Regards

Toemmel
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
When lineageos 17.1 is finally released you can go official 16.0 to official 17.1 but this is an unofficial release.

In the install instructions I said to make a backup, erase, and install. That is what you need to do to run this build.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Dima464473:
Hi, I noticed that 1 beta does not work hotspot, + Russian is not fully translated. thanks.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Thanks [MENTION=5925090]alexax66[/MENTION] I will look into it tomorrow, I obviously can't do anything about Russian translation but I would urge you to submit correct translations via gerrit.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
Hi,

I tried to install the ROM with OpenGapps Pico (version January 16th, 2020) but after a couple of minutes into the initial booting process it returned to the recovery. The problem seems to be Gapps-related since the system booted just fine without Gapps installed. I wiped cache, data and system prior to the installation and am on the latest TWRP 3.3.0. I first installed the ROM and then OpenGapps in the same install queue (no Magisk). My models is a A310F.

Am I missing something essential?

Best regards,

thebinf
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Odd, that is the same version OpenGapps I tested with and it worked fine. Try re-downloading it, maybe the download is corrupted?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The A3 has a quad core processor (Exynos 7578). Yes there is a second cluster in the silicon but they are disabled for a reason. Most likely the A3 CPUs are from the lowest quality bin and have issues on the second cluster (people have reported instability running 8 cores in the past). You will not gain much in terms of performance enabling the second cluster outside of benchmarks (most games etc are still only single threaded) but will increase your power drain.

I will never enable the second cluster in my builds so do not ask.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
My TWRP builds are identical to stock from a UI perspective?

Maybe you are running Lineage recovery?

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Oh, I'm really sorry I confused between los recovery and your signed version of twrp. I can make backups now, hopefully restore will work too!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] yeye.phone:
Hello,

sorry if i'm bad, but if i want to update lineage-17.1-20200412-UNOFFICIAL-signed-a3xelte with the last release, i need to use Danwood 's twrp or los recovery ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

You should be able to update with either recovery.

I recommend los recovery though as it has proven to be stable during updates.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Big thanks to [MENTION=6707196]danwood76[/MENTION] and [MENTION=8184192]Stricted[/MENTION] !

We will soon have official 17.1 A3 (2016) builds! It's merged to Hudson, so the next official build will be 17.1!

https://review.lineageos.org/c/LineageOS/hudson/+/276245
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pluescho:
Thx so much!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
To update to the new official builds I have updated my migration zip with the new keys for official 17.1.

It is available here (obviously use the 17.1 version):

https://mega.nz/folder/rUxWBKQT#0j0324DVoZi62fT7mpwHlw

I would advise you to use the lineage recovery if you do not use the extra features of TWRP as it is more up to date.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
[MENTION=6707196]danwood76[/MENTION]: Congratulations and a big thanks for your work!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] AndyYan:
Quick question, this should work from any Nougat stock (including the latest with U5/S5 bootloader) right?

EDIT: Disregard, seller sent me an A310N0 (which only ever had U1 bootloader) instead of A310F.