yashsingh1/xdaforums huggingface dataset:
[Android General] Falence:
(Dear moderators: I apologize upfront if this is in the wrong section, please refer the correct section or permissions if required before deleting.)

As per the title we are looking for developers who can contribute to a new operating system for mobile devices. Currently we have a leading well know GLOBAL mobile phone manufacturing company invested in this project.

What we are wanting to create:

- A mobile operating system that is simple and intuitive to use,

- that gives its users all the control over privacy, content, and device.

- That is free from all marketing and online campaigns,

- that gives each individual user the right to choose their setting prior to install,

- SAFE!!

What we are looking for:

- Developers who have the skill sets to achieve the target set for us,

- Skills in creating mobile operating systems and or Hacking and manipulating mobile OS systems,

- Skills to write software for hardware communication (drivers),

- Free to travel and work on the OS (Although not essential),

- Long term Commitment.

What we offer:

- sizable remuneration,

- equity shares,

- All the hardware you need for testing,

- the chance to be part of something GREAT!

If you feel you can contribute in any way, regardless of how big or how small you think your contribution is, please write here and make sure you have a contactable messaging link so we can start a private chat to find out more, or message me directly..
[Samsung Galaxy Note 20 Ultra Questions & Answers] d_ganggreen:
There are many "leaks", if all are true what color is everyone thinking of getting?

I am torn between a few of the leaks I have seen. The white looks really good to me, probably my first choice. After that it is a toss up for Bronze, Blue, Green.

What is everyone else thinking?
[Samsung Galaxy Note 20 Ultra Questions & Answers] krabman:
Copper.
[Samsung Galaxy Note 20 Ultra Questions & Answers] tourbound129:
Copper is definitely first choice.
[Samsung Galaxy Note 20 Ultra Questions & Answers] swaze:
Ive had a version of blue for every note going back to the beginning. For some reason I think Copper is calling my name. Its different.
[Samsung Galaxy Note 20 Ultra Questions & Answers] kangi26:
Maybe I'll go with the black one. I put a Pitaka case on, so the color itself doesn't really matter at all to me. Maybe I'll do the copper so I can have a nicer colored S-Pen?
[Samsung Galaxy Note 20 Ultra Questions & Answers] alastairgreen_Nexus:
Copper, since its the same as my Note 9
[Samsung Galaxy Note 20 Ultra Questions & Answers] cpufrost:
Once you go black, you never go back! ;)
[Samsung Galaxy Note 20 Ultra Questions & Answers] shook187:
I was thinking copper but I'm afraid it looks more like pink.

Black or white for me!!!
[Samsung Galaxy Note 20 Ultra Questions & Answers] 94b20gsr:
I'm with Shook, "copper" looks like rose gold to me so I won't be having that. Blue or black here.
[Samsung Galaxy Note 20 Ultra Questions & Answers] @home:
Samsung chose some of the most boring colours for the note 20 Ultra.

The copper is horrid & black is boring.

I'll probably go for white, I had the Pixel 4XL in white & it was ok.

What happened to the Canary Yellow of S10e...Now that would have been a fab colour to have on the Note 20 Ultra.
[Samsung Galaxy Note 20 Ultra Questions & Answers] fatboypup:
Black, because 512GB
[Touch Diamond, MDA Compact IV General] amirfsl:
im using htc touch diamond..

looking for a freeware that can lock the screen when there is an incoming call,NOT during a call..

sometimes i accidentally hit the answer or deny key on the screen while my phone is in my pocket...

i dont want accidentally answering or denying calls..

just looking for a simple software..

i've tried s2u2 but it seems that 'slide to answer' is not compatible with touch diamond....i'm not gonna use that again

any suggestions?
[Touch Diamond, MDA Compact IV General] bonquiz:
same problem...

an tried s2u2 too, but it sometimes work an sometimes doesnt, its so strange with it, when i get a call it flashes up, getting brighter and darker again the touchflows shows up and dissappears an i dont push anything the call is rejected so s2u2 wont work for me...

please help, this problem with accepting or rejecting incoming calls just by having it in my pocket is very anoying.

thanks
[Touch Diamond, MDA Compact IV General] jirka20:
you can try this http://xdaforums.com/showthread.php?t=422871
[Touch Diamond, MDA Compact IV General] bonquiz:
OMG

i cant tell you how much i thank you

awesome tool.

thanks for the quick help...

btw is there any in build function in the diamond itself, like dont wakeup screen by incomming calls or something?
[Touch Diamond, MDA Compact IV General] buciuman:
OMG!

Did u guys notice there is a sticky thread regarding this!!!!!

OMG!

http://xdaforums.com/showthread.php?t=414731
[Samsung Galaxy J7 (2017) Questions & Answers] c_/\/\_k:
Urgent Help Unlock J7 Max (sm g615f/ds) Without Data Loss

hello freinds, i have 2 year old j7max... few months back i stopped using it.. but now i need some data which is inside that phone.. unfrotunately i forgot the pattern pin.. but i do have google account. But i dont want to wipe or format it.. Is there any way to unlock this phone without wiping the data..?

In ODIN mode.. secure dl mode in On.. and FRP lock is On.. so unable to flash recovery or any other file.... or is there any way to recover with google account..?
[Miscellaneous Android Development] tvroman:
How different is the Atom XL?
[Miscellaneous Android Development] a-dead-trousers:
Going XL

Hi.

Great work. :good:

I want to built a ROM for the Atom XL myself. And because I'm no expert on this (for now) I'm in search of guides and hints on how to achieve my goal.

As far as I know the biggest problem with Unihertz is that they use a Mediatek chipset with which they are not allowed to provide the sourcecode of the kernel. Or at least you have to pay for it from Mediatek.

But there are some variants of the chipset (Helio P60; mt6771) used in other mobile phones (e.g. Nokia X5) for which I was able to find kernelsources on Github. Using these and the latest Android kernel from google I tried to compile a kernel as a starting point. I was able to extract the build.config directly from the phone which helped tremendously. This should at least get me to the point where I'm able to assemble a TWRP build. But I believe that I'm still missing some (vital?) drivers which are specific to the actual device. This includes I think the missing touchscreen driver that you mentioned is preventing the recovery to be useful.

So now I'm a little bit stuck, because most of the guides to arrange a LineageOS (or any other custom ROM) build tree I found require the sourcecode from the manufacturer which we don't have. All other guides to build from scratch were too generic for my current level of expertise.

Can you please share your approach to create this build?

If you don't want to do this in the open you could also PM me.

With kind regards

ADT
[Miscellaneous Android Development] PeterCxy:
You don't need the kernel source code to build a working ROM -- just look at my device tree for Atom L. I think you can build a working ROM for the XL by just replacing the prebuilt kernel in my device tree with the one from Atom XL and also re-extracting the vendor blobs from XL using the script in my devcie tree, then rename everything to Atom XL instead of L. I don't know if the integrated amateur radio would still work though.
[Miscellaneous Android Development] a-dead-trousers:
I'm already on to that.

But I seem to have trouble extracting the prebuilt kernel. None of the tools I found gave me the exact files you have got (dtb.img, dtbo.img, Image.gz). What did you use?

The best I could get were "dtb", "kernel" and "dtborecovery" (without extensions) which roughly had the same size as yours.

Also, as far as I understand it, with your initial commit (without the modifications for Lineage itself) I should be able to at least compile a recovery image but I got an error regarding a missing dtb.img file in the "out" directory.

Something seems to be missing because, my dtb file is in the "device" directory and not being transfered into "out" during building.

I'm not sure that is because I have got a different naming scheme (renamig it didn't help) or I did something wrong with the extraction.

---------- Post added at 07:30 ---------- Previous post was at 07:14 ----------

Another question I have:

Are the vbmeta-files you used to flash the recovery the ones from the original firmeware zip from unihertz or did you get them from the lineage built?

And reguarding the rather smallish system partition:

I have an idea to bypass that by using the SPFlash Tool from Mediatek. As far as I understand the settings in the scatter-file this tool does a repartitioning of the internal storage. So we only need to "decrease" the userdata, "move" some partitions inbetween and "increase" the system. Only problem is, I couldn't find a partition designated as "system" in the scatter-file, only one big "super" and a "vbmeta-system" (which for my understaning is for verified boot) partition.

What do you think?
[Miscellaneous Android Development] PeterCxy:
> None of the tools I found gave me the exact files you have got (dtb.img, dtbo.img, Image.gz). What did you use?

There is a tool called `unpack_bootimg` in the Android source code. Just run `make unpack_bootimg` in the root directory of the Android source tree and you will get one in the output directory. (btw I have renamed those extracted files so the names won't exactly match, but you need this tool to extract the correct images. All other tools won't work properly).

> my dtb file is in the "device" directory and not being transfered into "out" during building.

Because most tools other than `unpack_bootimg` extracts dtb incorrectly.

> Are the vbmeta-files you used to flash the recovery the ones from the original firmeware zip from unihertz or did you get them from the lineage built?

Those don't matter. Either will work as long as you flash it with the correct parameters as given in my post.

> And reguarding the rather smallish system partition

No don't do that. Android 10 does not use a separate system partition anymore, instead both system, vendor and product are sub-partitions in a huge super partition. When flashing a new ROM, the partitions are automatically resized to match the new image exactly, instead of leaving free space unused like before Android 10. That's why I need to reserve space in BoardConfig.mk for gapps to be installed correctly.
[Miscellaneous Android Development] a-dead-trousers:
Still not able to build.

I'm still getting an error:

FAILED: ninja: 'out/target/product/Atom_XL/dtb.img', needed by 'out/target/product/Atom_XL/boot.img', missing and no known rule to make it

Comparing your BoardConfig.mk with mine shows a slight difference in the offset and size values which could be associated with the different kernels of the phones.

But using "unpack_bootimg" I didn't get a value for "BOARD_KERNEL_OFFSET" like you have it in your config. Could this be the problem?

Your BoardConfig.mk

My BoardConfig.mk

Do you see anything else out of the ordinary?

(Because I'm doing everything what you did step-by-step the links point to the best matching commits)

Despite not being able to compile right now I tried to press on with integrating your changes in the hopes that it will be fixed somehow later on ;)

So I'm currently stuck on this commit of yours:

Atom_L: import overlay from official vendor

Where did you get the "config.xml" and "power_profile.xml" from? The best thing I could find was a "power_profile.xml" inside "/vendor/overlay/FrameworkResOverlay/FrameworkResOverlay.apk" which seems to be a "compiled" version of the aforementioned xml-file.
[Miscellaneous Android Development] PeterCxy:
> Comparing your BoardConfig.mk with mine shows a slight difference in the offset and size values which could be associated with the different kernels of the phones.

TARGET_KERNEL_OFFSET should normally always be 0x00008000. Also, your other offset values seem to be wrong too -- those values from `unpack_bootimg` cannot be filled in directly to BoardConfig.mk. Instead, you need to subtract BOARD_KERNEL_BASE from them (e.g. BOARD_RAMDISK_OFFSET should be 0x55000000 - 0x40078000, which is 0x14f88000, the same as mine). In fact, I think those parameters should be exactly the same for XL and L. Other than that, I don't think I can see much of a problem about your makefiles.

However, note that not all of my historical commits represent a compilable state of the device tree. I'd suggest you start directly from the latest state and just replace whatever is relevant instead of starting over. And there should not be much that needs changing at all except device names, fingerprints and the proprietary vendor files.

> Where did you get the "config.xml" and "power_profile.xml" from

Exactly from those apks. Just decompile them using apktool.
[Miscellaneous Android Development] a-dead-trousers:
Still giving me errors.

So I tried a

very

unconventional approach: I just copied the file myself into the mentioned "out/target/product/Atom_XL" folder. :p

For now it's still compiling. Fingers crossed.

I just reached your biggest commit yet.

Can you tell me how you got the list of needed files? I hope it's not through trial-and-error.

Except for the values in "setup-makefiles.sh" only the "proprietary-files.txt" seems to be device specific. Is there anything else I need to be aware of in this commit?

P.S.: I know it is tedious to go through your commits one by one but I want to learn something of it not just simply copying what you did. To get a feeling where the biggest pitfalls are and what you did to circumvent them.
[Miscellaneous Android Development] PeterCxy:
> Still giving me errors.

Looks like that dtb.img error was totally my fault -- it was due to my jerry-rigged solution of using prebuilt dtb image that conflicted with one of Lineage's update in August and I haven't built the ROM for a month. Now I have fixed it in the latest commit.

> Can you tell me how you got the list of needed files?

All of those files are for VoLTE support and I started with the list from a commit in Redmi Note 7 Pro's device tree that imported those VoLTE blobs, and then added what was missing one by one (when something is missing the Phone process will crash and you can see what got missing in the logs). I don't think the list will be any different on Atom XL so you can just use the one in my device tree.
[Miscellaneous Android Development] a-dead-trousers:
Hi.

Thanks to you everything is running smoothly here. But what bugs me is that TWRP is not working on our devices.

Although for the Atom there is a possibility: https://xdaforums.com/android/development/twrp-modded-to-unihertz-atom-t3885793

Before I want to go public with my build I wanted to solve this last "mystery".

So I tried to include it in my current source tree according to the (official?) guide but some errors prevented me from a successful build.

Naturally I asked for some guidance at the most reasonable places I know of but got nothing so far:

https://xdaforums.com/showpost.php?p=83443611&postcount=4622

https://xdaforums.com/showpost.php?p=83455271&postcount=4623

https://github.com/TeamWin/android_bootable_recovery/issues/70

I even tried different repositories (omnirom/android_bootable_recovery) and revisions (android-9.0) but these resulted in missing library "type" (static vs. shared) errors so I assume these are too old for LineageOS 17.1

What I want to know is how you managed to get TWRP to built for your device even though the touchscreen wasn't working?

Did you use your LineageOS source tree or one of the many "minimal" manifests? If so, which one would be the "best" to use?

wkr ADT
[Miscellaneous Android Development] dirtylimerick:
[MENTION=5351691]PeterCxy[/MENTION] and [MENTION=7624432]a-dead-trousers[/MENTION]

Thanks for all the work on this so far. I've got an Atom L and have gotten the ROM's PeterCxy posted running on them as in the OP. Do either of you have a quick step-by-step workflow of how you got all the Lineage sources set up and built into the various ROMs? I'd like to be able to build the ROMs from scratch and understand the process.

If I can get caught up to where you two are at with the builds, I can help debug, test and work through issues.
[Miscellaneous Android Development] a-dead-trousers:
I documented my steps to setup up the build environment in the readme of my repo:

https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL

But leave out the TWRP part. It isn't working yet mostly because TeamWin/android_bootable_recovery and LineageOS/android_bootable_recovery are too similar.

To figure out all the bits and pieces needed for the device I followed the commit log of [MENTION=5351691]PeterCxy[/MENTION] build.
[Miscellaneous Android Development] a-dead-trousers:
Hi, [MENTION=5351691]PeterCxy[/MENTION].

Finally I was able to build a TWRP recovery and surprise, surprise the touchscreen isn't working.

But during my attempts to get a working TWRP build I came acros a guide that explains how to patch the kernel to get the touchscreen to work.

https://forum.hovatek.com/thread-27132.html

So I tried to follow it but failed to identify the "end" of the zipped Image-file (step 18) to remove the payload from the gz-file. Regardless of which of the null-bytes I use for cutting I always get a warning from 7-zip that there is still data at the end.

Do you know a better approach to achieve this whole patching? Maybe even come up with a scripting solution to easily apply this patch in later builds?

wkr ADT
[Miscellaneous Android Development] PeterCxy:
There is no sane way to solve the problem without kernel source code. Basically the stock kernel just does not load the touch screen driver in recovery mode. That patching guide is pretty out of date and I imagine it won't work on most recent kernels. The only proper way is to pressure Unihertz to actually obey GPLv2 and release their kernel source code. Or maybe someone can try reverse-engineering the kernel, but at least I won't do it because it'll just be too much of a hassle.
[Miscellaneous Android Development] a-dead-trousers:
I'm with you on this one, but as long as we don't have the source code we need to resort to other means to achieve our goals.

Yeah it's from way back in 2019 :p

Anyway, with a little bit of tinkering I was able to modify my kernel to load the touchscreen driver in recovery mode.

Here is the device tree and the manifest i used.

I wouldn't recommend to use it in it's current state at all though because the fstab needs a little bit of tinkering. Everything seems to be either unordered or not mounted properly and I fear anything you do in there now will mess up the whole device. BUT I got the touchscreen goin for me which is nice.

As soon as I have everything sorted out that needs to be fixed on my build (e.g. signing, radio, included gapps working properly, TWRP) I want to dig deeper into the kernel.

There are some devices with Helios P60 out there from other vendors which offer kernel sources.

P.S.: I also uploaded a HOW-TO in my device tree.

If you or someone else wants to try it. Also if you want to you can send me a "symbl.txt" (see to the HOW-TO) extracted from your device then I can do the patching for the Atom_L too.
[Miscellaneous Android Development] PeterCxy:
Happy to hear that you were able to figure the touchscreen out. I tried to port TWRP at the very beginning when I started tinkering with the device but quickly grew frustrated and just ported Lineage Recovery instead. I guess I might try patching the kernel image too at some point later.

BTW, for TWRP to work with devices released after Android 10, I'm pretty sure you need an extra set of patches that are not yet fully merged to the main TWRP repository. I remember there's some guy providing another manifest with all the patches applied but I couldn't remember the name.
[Miscellaneous Android Development] a-dead-trousers:
Hi.

I just officially announced my build for the Atom XL:

https://xdaforums.com/android/development/rom-lineageos-17-1-unihertz-atom-xl-t4171407

Could you please put a link in your first post for those in search of the Atom XL and found your thread instead. Thanks.

wkr ADT
[Miscellaneous Android Development] a-dead-trousers:
hi [MENTION=5351691]PeterCxy[/MENTION].

During my daily usage of the phone I encountered a strage problem:

The audio jack isn't working. Plugging in some headphones I get this slight click in the earpieces when the circuits connect but nothing else happens. Neither a "headphone" icon in the status bar nor hearing anything coming from the headphones itself. The main speaker of the phone keeps playing the music. Using bluetooth everything is working as expected though. So I used logcat to see if something is coming up during plugging in but nothing "catchy" shows up in the logs. My guess is that some (vendor?) service is missing or not started during booting. Next I checked If something shows up on logcat during boot but I'm not sure for what to look exactly. There are quite a few errors and warnings though. In my despair I started to "fix" the "avc: denied" (SEPolicy) entries. Thats when I found a specific error reguarding VoLTE. Maybe this would fix the problems you had with VoLTE in enforcing mode:

https://github.com/ADeadTrousers/an..._Atom_XL/blob/master/sepolicy/private/init.te

(The line with "socket_device:sock_file")

My provider doesn't support VoLTE so I'm not sure if this helps or not. Maybe you could check it.

Anyway can you please tell me if your device's audio jack is working or not?

If you're (by some mysterious coincidence) not affected by this, can you at least give me some pointers for what to look for to get this fixed on my side.

The Internet Is not very helpful when searching for "android audio jack" or something similiar.

Thanks in advance.

wkr ADT
[Miscellaneous Android Development] neo901:
Thank you for a great work!

I just received my Atom L and something does wrong. I successfully unlocked oem, flashed vbmeta and LineageOS Recovery, however it fails when I try to reboot to recovery or just boot LineageOS Recovery via fastboot. It is always old stock recovery ;(

I have impression that stock rom overwrites recovery each time when starts.

Any ideas how to resolve this?
[Miscellaneous Android Development] a-dead-trousers:
I'm not sure why, but [MENTION=5351691]PeterCxy[/MENTION] somehow got the commands a little bit mixed up. It's in fact

fastboot boot lineage_recovery_XXX.img

OR

fastboot reboot

and then simply hold the volume-up key during the entire boot-screen.
[Miscellaneous Android Development] neo901:
Unfortunately the result of both commands is normal phone boot :(
[Miscellaneous Android Development] landsome:
Does anyone get choppy audio (constantly interrupting, to the point of being unusable) on Bluetooth (several different headphones, in my case)?
[Miscellaneous Android Development] a-dead-trousers:
Stock ROM or Lineage ROM?
[Miscellaneous Android Development] landsome:
Stock
[Miscellaneous Android Development] a-dead-trousers:
Sometimes when using my bluetooth headphones with my PC I also have problem with choppy audio.

It took me quite some time to figure out what's causing it: The tramway that's passing in front of my apartment building.

As silly as it sounds, everytime the tram stops in front of the house my headphones loose the connection for a short time. When staying in the back of my flat, far away from the street, everything works fine. The only explanations I have are, because bluetooth and wlan (wifi) operate on nearly the same frequency, that the hotspots used in the tramway are not properly "shielded" (a too broad frequency range) or the built-in bluetooth of my PC is too "sensitive" (reacting to the magnetic field from the overhead contact wires).

So first I suggest you test if staying away from a wlan (wifi) hotspot or other sources of interference "fixes" this problem.

(Or getting near to one causes it)

The only one who might be able fix this though is the manufacturer. Therefore it would be best to contact the support of Unihertz.