yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] merkman:
So I've been using R0 for about a month now. The original install went smoothly, and I've updated QuickGPS, applied a couple other fixes, including modding the weather app to allow for my own city list, and I'm pretty thrilled with the device.

One thing I DID notice the other day, went I went to use the GPS for the first time, is the onboard GPS doesn't always work. Seems like if I use it for a bit, then go into a store and come back out, sometimes it's "locked up". I know because I go into GPSGate and it says it's connected, but no data is coming in.

Figuring this must be an onboard GPS issue, I went to change the default com port it uses. But when I launch the app under settings, and change it from COM4, the program seems to lock with a spinning cursor. At that point I'm forced to soft-reset, I change the internal GPS *back* to COM4, and it works great again.

Has anyone else had this issue? Probably the BEST fix is just going back to using my old iTrip BT GPS with iGuidance v4, and that really should eliminate the need for using the built-in GPS anyway. But it IS nice not needing the extra device. So if there IS a simple fix and someone cares to share, that would be cool.

Thanks to ALL the posters here. I wouldn't have done 1/2 as much with my HTC devices without the great site and posts! :cool:
[Touch Cruise ROM Development] merkman:
Well, maybe someone could at least tell me if they've tried the new radio, suggested for Syrius R1, in R0, and if they had any problems thereafter?
[Moto G Power (2021)] whoshotjr2006:
Hi everyone

I've been working on getting twrp to boot on our borneo device for a week or so, borrowed I the device tree made by mistersmee for the g9 power since the two devices are almost completely the same

https://github.com/TeamWin/android_device_motorola_cebu

heres where I'm at:

https://github.com/touchpro/twrp_device_motorola_borneo

The only thing I cant seem to get working is the touchscreen. I realize others have tried before me already and had the same non working touchscreen, I believe the majority of us have an Ilitek touchscreen while others have focaltech or nova. I got the driver framework up and recognizing it exists from dmesg output but cant seem to get any actual touch input to register. You can look at my changes to android 11 twrp in the github above by selecting branch twrp-android-11 and using a diff program. I use meld in ubuntu.

if you want to build for yourself and help out: (i'd use ubuntu 20.04, i tried 20.10 first but one of the packages is too new and doesnt like the toolchain)

follow the instructions here to set up your build environment

mkdir twrp (you can name this whatever you want)

cd twrp

repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0

repo sync

add the device tree above to twrp/device/motorola/borneo

also add this to device in twrp/device/qcom/twrp-common

make your changes inside device/motorola/borneo then

. build/envsetup.sh

export LC_ALL=C

lunch omni_borneo-eng

mka -jx clobber && mka -jx recoveryimage (-jx is number of cores you have, i have quad core i7 with hyperthreading so i use -j8. personal preference really)

your completed build will be in twrp/out/target/product/borneo as recovery.img

reboot to fastboot (adb reboot bootloader) and type

fastboot boot recovery.img

see if your changes worked! look forward to seeing what you guys can do
[Moto G Power (2021)] whoshotjr2006:
mine for later
[Moto G Power (2021)] Onoitsu2:
Have not had the time to toss together a build environment for this, since I'd have set up the entire OS and beyond for that task, since my only Linux is Garuda in a much too small VM that is nowhere near right for that., been only hacking my way through it with Android Image Kitchen in Windows and some other utilities to get touch support in my 3.5.2.10-0 cebu source image.

It works perfectly if booted into TWRP just takes about 30-seconds before touch enables itself fully, but not when flashed (fastboot or applied internally via DD, or using a modified TWRP zip via Magisk that has had my ramdisk swapped into it).

When flashed, touch simply will not function, so something is obviously not being carried over properly so when being loaded from the recovery partition it seems, despite it being the exact same ramdisk (I extracted the recovery img, pulled out my ramdisk, popped it back into a whole new image, booted it and it had touch, so I know it's supposed to have the data there but likely needs a full from the ground up build of TWRP to behave on flashed installs.

@whoshotjr2006, had any more luck with your building of it? I can test or anything you may need in your own efforts, but just have no time for the actual building of it to tinker.

Oh, and thought you should know this works if you were wanting to go RW for System, but you'll have to use Linux due to falling prey to Error 73 https://xdaforums.com/t/script-android-10-universal-mount-system-r-w-read-write.4247311/. I put mine back because it didn't seem to behave quite right there, but could be useful in your own tinkering.
[Moto G Power (2021)] Onoitsu2:
OK, got it where it is fully flashable and bootable with touch for mine. Used Android Image Kitchen, unpacked TWRP image that boots with touch working, copied out the kernel and ramdisk from split_img folder, extracted stock recovery, replaced those 2 items with properly renamed versions and then repacked it with --original argument, and then it boots and flashes properly. Just a quick hack on it, but functional for those that need it.

This should be easy to combine in your /vendor/lib/modules from your own, as well as /vendor/firmware as long as you're rooted to pull it, into your TWRP ramdisk before putting it into the stock recovery this way. So you can get fully functioning touch for any display type in use.
[Moto G Power (2021)] Onoitsu2:
finally having time to try to build an environment. Making a generic VM and will post it when done and easy to use, but running into some issues in my getting it to a point to test its success even. The steps you provided, missed a needed command "sudo ln -s /usr/bin/python3 /usr/bin/python" if using the 20.04 Ubuntu. But then how do you "add the device tree" as you put it? I'm normally a repacker to get things working, versus building things. I'm sure downloading the zip of the code and loading it into those folders is bound to break something as it always does when it comes to using links and ramdisks.

Perhaps you can provide more clear instructions of what you mean by that and I could finally gladly be able to contribute to this as more than a hackish throw-together process, since the description you provided "add the device tree" yields no meaningful results for any process for that to be pieced together from other builders.
[Moto G Power (2021)] whoshotjr2006:
git clone -b main https://github.com/touchpro/twrp_device_motorola_borneo.git

or you can just download the zip from my github, the only time it breaks symlinks so far that i know of is when you download a kernel in a zip file instead of git cloning it

take the twrp_device_motorola_borneo files and put them in /device/motorola/borneo and you should be good to go
[Moto G Power (2021)] Onoitsu2:
That won't work, as it doesn't seem to have a twrp-10.0 as it looks to be depreciated, https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-10.0-deprecated. How'd you get yours, or did you mean 9.0?
[Moto G Power (2021)] whoshotjr2006:
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0-deprecated

Twrp has always been built in an omnirom build environment but with a11 they switched to being built in an aosp environment. Twrp-10.0-deprecated they recently renamed to add the deprecated tag on but thats the one for android 10 that I initially used
[Moto G Power (2021)] Onoitsu2:
Got my build environment set up and can upload the image in a bit if anyone wants it. @whoshotjr2006

using your steps it builds, but even having modified the firmware and modules to include the changes I put into mine to have it have touch support, it still will not. But the hacked android image kitchen one works just fine, which makes absolutely no sense when there are no errors, only warnings reported, but even those all look to be minor type casting of variables that I've noticed.
[Moto G Power (2021)] whoshotjr2006:
remind me again where you found that twrp that youve used android image kitchen on? was it from moto g9 power or another device? if you can let me know ill look through device trees and see what they have that we dont

seems like maybe its not insmod'ing the .ko file for your touchscreen, or it is and your touchscreen needs a firmware check/update at load. you'll have to remind me again which touchscreen you have (sorry its been a minute i've been busy) and we can look through other's device trees at the firmware loading portion
[Moto G Power (2021)] Onoitsu2:
Source I used in AIK was cebu's 3.5.2.10-0 from https://twrp.me/motorola/motorolamotog9power.html. used AIK to unpack it.

To get touch using my quick hack, I just dropped in my matching .bin's from /vendor/firmware plus my ilitek_fw.bin to go with their novatech*.bin's and NT36xxx_MP_Setting_Criteria_601E.csv in place of their NT36xxx_MP_Setting_Criteria_6026.csv (deleted theirs).

Then also popped in my /vendor/lib/modules (minus audio ones).

At that point in tinkering it boots with touch. But fails to keep touch on booting into recovery.

Then I stumbled upon some obscure guidance about something in the kernel in recovery not initializing the touch on some devices and potentially being able to hex edit it after manually extracting the kernel using a hex editor. And then unpacked my booting version again, saw the kernel already separated out and pulled that and my ramdisk from split_image folder. cleaned up. unpacked the stock recovery. replaced with appropriately named kernel and ramdisk files and used the repack --original. Flashed it and it booted with perfect touch, just takes about 30-seconds on start before it's responsive. I have mine encrypted still so must input a passcode and just tap on the log button a few times till I know it's working then input my code and off it goes working normally.

Should not have anything too crazy different. I think the only thing I did was delete the etc file from the cebu, replacing it with an etc folder with a recovery.fstab and twrp.fstab I had scavenged from @svoc 's 3.4.0.0 (https://xdaforums.com/t/working-twrp-but-very-unofficial-but-very-useful.4313665/ of which touch did not work for me, but it booted perfectly enough to extract my firmware and lib modules initially to put into my 3.5.2.10-0). Since every time I'd use Android Image kitchen to extract the cebu image it complained about things in /etc, and that was the only difference I could find between 3.5.2.10-0 and the 3.4.0.0. That is the only potential thing I did that could be of unknown consequence.
[Moto G Power (2021)] Onoitsu2:
And never be sorry, you're helping out here, we understand, just like if you're waiting on a response back, that you're as understanding too :)
[Moto G Power (2021)] Onoitsu2:
Compiled, touch working when booting it. Only change I made was to add my files as I outlined before, but into the firmware and lib folders respectively, but also edited the load_ts_firmware.sh to ensure nova and chiptone are no longer commented out. Flashed and has touch fully working as well. So it should be an easy build if I can get it working.

Edit: And touch does not take 30+ seconds per the 3.4.0.0 @svoc version I believe because it's not re-flashing the display code. So that could be why some perm lose touch, and I just got VERY lucky with mine to not.
[Moto G Power (2021)] svoc:
Yes you are right all I did was put the touch screen driver in the twrp and send it to you that is why it takes less then 30 secs to do no need to recomile it each time just add your files in it and rezip it
[Google Pixel 6 Pro] scottb908:
Anyone run into this yet. https://www.androidpolice.com/google-pixel-6-and-6-pro-screen-flicker/
[Google Pixel 6 Pro] blackhawk:
"Some Redditors speculate that the flickering might be related to static discharge that's released when hitting the button."

Yeah, nothing like the rocket scientists at Reddit to come up with sound answers🤯🤣🤣

Static electricity would destroy the display.

FET's are very sensitive to over voltage on their gates.

Maybe what they were trying to say was unintentional temporary surge on the gates of the matrix TFT's.

If that's the cause long as that surge doesn't exceed the max specs for the FET's in the matrix it's not damaging. If it does, outlook not so good.

If it's not happening during normal operation once on, it's probably a harmless quirk.

Who knows maybe intentional to give it some character🤣 I sort of think it looks cool... but Google isn't cool so yeah, it's a fk up.
[Google Pixel 6 Pro] nxt:
I have it on my P6P. Turn phone completely off, quickly tap power button and it'll flicker. I'm guessing it's trying to power up but since you only quickly pressed the button, not full power is given.

I'm not worried about it.
[Google Pixel 6 Pro] kboya:
I've seen no noticeable flicker at all. Perhaps I just lucked out on this phone? 😂
[Google Pixel 6 Pro] PhilipL2021:
By design there is an inbuilt delay so you have to press and hold the power button, this helps prevents accidental power ups and also allows time for the user to press other combination of buttons (i.e. to get the bootloader screen), so on a quick press things are still happening behind the scenes like a pre-flight check, and the screen electronics are probably immediately powered up as part of this pre-flight check.

When the button is released without reaching the timeout period to trigger a full power on, the phone just goes back to being off again, now you have a falling voltage which doesn't always drop immediately due to stored charges in capacitors, and that can cause odd glitches sometimes as components see lower voltages than they are designed to work with. With sensitive chips (like flash memory) there will be brownout detection, so they immediately stop cleanly when they see a low voltage, and before that voltage has dropped so low it starts causing oddities or malfunctions. The glitching might also just be the effect of other devices stopping and magnetic fields collapsing causing some spurious data to get to the screen before the screen itself has powered off.

It certainly isn't a fault or anything to worry about, just a quirk of the design.
[Google Pixel 6 Pro] skimminstones:
is it really an issue? Or just phone geeks looking for something to complain about? What effect does it actually have on the usage of the phone?
[Google Pixel 6 Pro] blackhawk:
Without knowing what's happening it's impossible to say it's harmless.

See my previous post.

At this price point I would send it back... or not and risk eating the repair latter. It could be mobo hardware related.
[Google Pixel 6 Pro] bouchigo:
Google addressed this today saying to basically power your phone like you normally would, without pressing the power button in quick succession without powering the phone up, and that a fix will be out in the December patch/update.

It's not a hardware issue.

Link (Google community post): https://support.google.com/pixelphone/thread/133351387/pixel-6-pro-display-residual-light?hl=en
[Google Pixel 6 Pro] danw_oz:
I had this happen once where the scrolling on the screen stuttered the entire time scrolling, then after closing the app and opening it again it was fine again, and haven't seen it since. My guess is that phone went into a deep sleep state, and took some time to wake
[Google Pixel 6 Pro] galaxys:
Ironically, I'm getting it using XDA website!😳🤖
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Bruh124:
The title says it all, if it changes anything im on the 12 beta, any help is appreciated guys!!

Thanks in advance
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] sorandumb:
+1 on this, i assume you are using the new Android 12 beta yes?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Bruh124:
Bingo
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
ArrowOS

/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/

ABOUT

ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.

Website: https://arrowos.net

Telegram: Channel | TG Portal/Links

Github: https://github.com/ArrowOS

Code Review: review.arrowos.net

E-mail: arrowos.contact

PayPal: Donate to us

Blog: blog.arrowos.net

Checkout more documentation at (maintainership/contributing): Check this out

WHAT WORKS?

Almost everything

WHAT DOESN'T WORK?

You tell me

Be sure to include a log : check how to

DOWNLOAD (ONLY GAPPS VARIANT)

https://mega.nz/folder/iQFXCSAa#N_SqYZA1TptEJVyPVg5iXw

Guide for flash ROM:

Boot TWRP

Make backups

Tap Install -> Select Rom zip

Go to reboot menu -> Select opposite inactive Slot

Reboot recovery

Now in Arrow Recovery

Factory reset

Apply Update -> Flash Magisk if any

Reboot system now

Read our blog article/post about:

* HOW-TO report a bug

* GAPPS and VANILLA variants

* Checking build integrity

GPL compliance:

ROM Source- https://github.com/ArrowOS

Kernel Source- https://github.com/anht3889/android_kernel_lge_sm8150
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
Screenshot

View attachment 5445591View attachment 5445593View attachment 5445595
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] minhthien0711:
long time no see bro :)

thanks u for share

i will test and feedback ♥♥♥
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
Changelog:

10/31/2021

Fix Double tap to wake

11/01/2021:

Fix bluetooth

Add DAC back to Sounds settings

New changes from Arrow OS
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] Ebizza:
I'm on Sprint Stock 10. I take it I have to crossflash to Korean 11?

And what do you mean by 'Copy partitions'?
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] minhthien0711:
it had bug , the bluetooth can not turn on and fingerprint not run !
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] smartphone_lg:
waiting for the update to be complete and hoping for face unlock and DAC.
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
New build is up guys. I need someone to test Bluetooth and DAC since I don't have wireless or wired headphones to test. Thank you.

Build for G8 US is coming soon.
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
Another build is uploaded for fixing bluetooth again. I also make a build without gapps as well.
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] minhthien0711:
i tested new version , Bluetooth and DAC ok , thís rom's very smooth and excellent !

thanks bro so much
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] shivaluma:
Really excited for the g8 US version :p
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
G8 US: https://androidfilehost.com/?fid=7161016148664832545

Please test if it works for you. Be cafeful to backup and prepare anything needed if it is failed to boot
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] anhtuan70000:
The arrow os 12 for lg g8 us is super smooth, everything work fine, but when i install, it lost twrp and root (it have but the magisk not recognize) i cant flash or do anything what can i do
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] smartphone_lg:
Inbox telegram Anh Tran. Rom made in VN 😀😛
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] yusofsafuan:
What the difference between alphalm and alphaplus and which one i should download for my lg g8 korean set
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] quantan:
alphalm is for G8 US.

alphaplus is for G8 KR.

So you should flash alphaplus build.
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] yusofsafuan:
Ok thank you
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] DebiruLatte:
flashed on my cross-flashed sprint g8, and it works well! Thanks!
[LG G8 ROMs, Kernels, Recoveries, & Other Developme] Pypy50:
How did you get it
[Nubia Red Magic 5G / 5S  Questions & Answers] zeymhie07:
Hello to everyone,

actually i have problem with my neocharge as it is not showing so i guess fast charging is not working.. i tried to do these things.

1) Buying new charger adaptor & Cable (Original of Nubia)

2) Downgrading from the very first version. of Nubia

I have Global rom,NA version 864. before downgrading and coming back to v413.. but still the same. neocharge is not there anymore even with the downgraded version.. is there any more solution for this one. thanks in advance.
[Windows Mobile Development and Hacking General] WhiteRussianBC:
I need help. Im using Microsoft Visual Basic 2008 on my computer and I recently discoverd you can use it to make mobile applications. The problem is I dont know how to. Is there a plugin you need to download? Please tell me if you know how to. And also the requirements on my phone
[Windows Mobile Development and Hacking General] cmilian:
You Need the Windows Mobile DSK

You need to download the Windows Mobile SDK

http://www.microsoft.com/downloads/...3A-A651-4745-88EF-3D48091A390B&displaylang=en
[Windows Mobile Development and Hacking General] WhiteRussianBC:
Thanks a million
[Redmi Note 9 Questions & Answers] Thekshreal:
After updating to MIUI 12.5.2(RJOINXM) system launcher sometime refreshes when I go back to homescreen which results in changing of wallpaperback to stock one i.e., the snowy mountain one. Is this a known bug? I have tried clearing the data and cache, it doesn't seem to work. Are there any known fixes?
[Android Q&A, Help & Troubleshooting] randomuser654321:
Thanks to a lot of misinformation, tiredness and broken links from url shortens, I felt for a fake site pretending to be the official Magisk publisher. The site is:

masgisk.me

Now I know the official release is exclusively via Github. But it's already done, I've installed. Since it had root access via fastboot and it was installed using TWRP, I believe it is deep in the system and I'm not sure if flashing another rom would get rid of whatever I installed.

Is there a way to make sure there is nothing left and the system is safe?

I attached the file I used.
[Android Q&A, Help & Troubleshooting] randomuser654321:
Update: I checked the hash, it is the same as the official. So, I guess no real harm was done