• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Crazy Hockey - Air Hockey Challenge.

Hello guys, Crazy Hockey is now available on playstore. Crazy Hockey has 4 exciting Air Hockey tables and there are 4 levels in the game. It is a very relaxing and easy game to play but hard to master. There is a global leaderboard which will give you your rankings compared to other players. Here is the link to it: https://play.google.com/store/apps/details?id=com.myComp.hockey
Thank You.
highres7.png

Guide to root LG stylo 6 without PC?

Rooting android device is easy now a days. You don't need any technical skills in order to root your LG stylo 6 device.
In this article I'll guide you to root Lg stylo 4 device via a third party application.
Note - I'll not responsible for any kind of loss. Do at your own risk. Somethings may be work for you or may be not.

Here's the steps to Root Lg Stylo 6 without PC-
This method is independent, Mean this method doesn't require any PC/Laptop to root your device. The only need is your smartphone and KingoRoot Application. After that, you are good to go.

Root-LG-Stylo-6.jpg


Requirements

  • Unlock Lg Stylo 6 bootloader.
  • Charge battery 60-70%.
Steps to Root Lg Stylo 6

  • First, Download Kingoroot application and install in your android device
  • Next, Open KingoRoot app and tap on
    One Click Root
  • Once you click above button then it will start the rooting process
  • Soon Process will be done! And you'll notify by notification i.e. " Root Succeeded "
  • All Done! You have successfully root the LG Stylo 6 device
By using this method you can easily root your device. This is the easiest ever method I saw in my entire life. Next Method is similar because of that one also without a PC/Laptop.
If this method is not usefull for you then I recommend to follow safe Box Guide website full guide. Inside that article they guided the 3 different methods to root Lg stylo 6 device. Believe me it's worth your time.

If you have any query let make sure you comment below. I'll solve your query as soon as possible.

Help SD card crashing LG V40

Hello all.

Yesterday (02/24/2021) at approximately 1900 hours, my LG V40 ThinQ stopped recognizing my SanDisk Ultra 128GB Micro SD xc card. My phone was unlocked, and I went to access a painting app that was stored on the SD card, and I noticed it was greyed out. Upon further app inspection, I realized everything on my SD card was not currently being recognized. At this time, I shut my phone off, believing a restart may be required. (Side note: I turn my phone off every night and let it charge overnight.) I turned the phone back on approximately 1 hour later, and it became stuck in the boot sequence. The phone will get to the point of allowing me to unlock it, and show my background. It will state "Android is starting..." and at the top it will show the SD card icon that it does on startup when it is reading the SD card for the first time after booting. A few seconds later, the screen will go black, with the exception of the top toolbar and the bottom toolbar. The touchscreen becomes unresponsive as well. After a minute or so, the Verizon loading screen will come up (Verizon logo with pastel loading dots) The phone will remain here until I perform a forced restart with the Down Volume and Power button.

Safe Mode is inaccessible to me when the SD card is in, as the long press on the touch screen Power button will not bring up the secondary menu. I have accessed and successfully transferred over much of the SD card data to my PC (it notes that some JPEG files are corrupted), although the PC initially has issues with reading the SD card. Attempting to repair the SD card on the PC (Windows 10) leads to an endless loading bar. Can anyone help me save this SD card from a formatting, or worse, an untimely demise? I bought it new approximately 1 year ago.

Save me Old Ben Kenobi, you're my only hope.

Dark Born, Big update v0.2.4 is out!

Hi everybody,
Im an indie developer, Ive been developing this game for a while now, and i wish to share it with you and get feedback.


J2bw6NT.png


CIluLoJ.png


To Download the game:
https://play.google.com/store/apps/details?id=com.SaudAlomari.DarkBorn

For feedback:
you can reply here.
or contact me on https://discord.gg/xpjMveUH
or email me to dark.born.feedback@gmail.com

Quality:
i believe the game runs on medium to high end mobile devices, i wish you guys try it and tell how it performs on your device.
the game has 3 quality presets that might improve performance.
the game runs at 60fps, if you want to decrease battery consumption you can change it to 30fps in games settings.

All applications crashing (foreground)

Over the last 3-4 weeks, I've had applications crashing in the foreground, normally Pokemon Go. When this happens, all the apps crash and I'm returned to the home screen. After doing some digging with adb/logcat, I've found this error:

02-25 20:14:09.736 1856 10366 I ActivityManager: Too many PendingIntent created for uid 10150, pendingIntentRecord:pendingIntentRecord{3ac0c70 com.google.android.gms broadcastIntent}
02-25 20:14:09.737 1856 10366 I ActivityManager: incrementUidStatLocked count:5000
02-25 20:14:09.737 1856 10366 I ActivityManager: kill process:com.google.android.gms for too many pendingintentrecord
02-25 20:14:09.807 1856 2159 I ActivityManager: Force stopping com.google.android.gms appid=10150 user=-1: too many pendingintentrecord

uid10150 is Google Play Services, the same one which is complaining about too many pending intent records (alarms/notification, I think?).

Just prior to this happening, I can see a bunch of messages about "SensorService" and "AlarmManager" which may be related; see below. Anyone know what's going on here? The crashes are fairly erratic and don't seem to care how long the app has been running. I've removed updates from Google Play services and cleared its app data but the error is still happening.
Phone is a Realme 7 pro (RMX2170) running Android 10 and latest updates.

02-25 20:14:07.399 1856 4649 V AlarmManager: set(PendingIntent{107fad3: PendingIntentRecord{1044610 com.google.android.gms broadcastIntent}}) : type=3 when=1611405692whenElapsed1611405692m
axWhen =1611405692 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:07.662 1856 1856 D OppoPowerMonitor: Receive broadcast android.intent.action.BATTERY_CHANGED
02-25 20:14:08.289 1856 4024 I GnssLocationProvider: Total SV info received at framework: 74.
02-25 20:14:08.427 1856 5072 V AlarmManager: set(PendingIntent{acfb33c: PendingIntentRecord{f73c8c5 com.google.android.gms broadcastIntent}}) : type=3 when=1611406695whenElapsed1611406695m
axWhen =1611406695 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:08.732 1856 10366 W SensorService: SensorEventConnection sensor handle=11, package = com.google.android.location.collectionlib.SensorScanner$SensorEventListenerAdapter disable
02-25 20:14:08.732 1856 10366 D SensorService: recordConnection in disable
02-25 20:14:08.732 1856 10366 D SensorService: SensorDevice::activate: ident=0x7d45906200, handle=0x0000000b, enabled=0, count=6
02-25 20:14:08.732 1856 10366 D SensorService: disable index=4
02-25 20:14:08.733 1856 10366 D SensorService: >>> actuating h/w batch 0x0000000b 10000000 0
02-25 20:14:08.735 1856 10366 D SensorService: 12 active sensors
02-25 20:14:08.735 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[0].handle=0x0000000b
02-25 20:14:08.735 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[1].handle=0x00000015
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[2].handle=0x00000029
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[3].handle=0x0000005b
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[4].handle=0x00000065
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[5].handle=0x0000006f
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[6].handle=0x0000008d
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[7].handle=0x000000a1
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[8].handle=0x000000bf
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[9].handle=0x000000de
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[10].handle=0x0000010f
02-25 20:14:08.736 1856 10366 D SensorService: removing connection 0x7d45906200 for sensor[11].handle=0x000003e9
02-25 20:14:08.739 1856 10366 D SensorService: ~SensorEventConnection(0x7d45906200)
02-25 20:14:08.785 1856 10366 V AlarmManager: set(PendingIntent{8d6b21a: PendingIntentRecord{68dfb5c com.google.android.gms broadcastIntent}}) : type=2 when=1611400167whenElapsed1611405168m
axWhen =1611405168 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.290 1856 4391 I GnssLocationProvider: Total SV info received at framework: 72.
02-25 20:14:09.443 1856 5078 V AlarmManager: set(PendingIntent{a153ec3: PendingIntentRecord{1fd5340 com.google.android.gms broadcastIntent}}) : type=3 when=1611407695whenElapsed1611407695m
axWhen =1611407695 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.451 1856 3994 V AlarmManager: set(null) : type=2 when=1611410831whenElapsed1611410831maxWhen =1611410831 win=0 interval=0 flags=0x8 pkg = android
02-25 20:14:09.454 1856 10366 W SensorService: SensorEventConnection sensor handle=11, package = com.google.android.location.collectionlib.SensorScanner$SensorEventListenerAdapter enable
02-25 20:14:09.454 1856 10366 D SensorService: Calling batch handle==11 flags=0rate=20000000 timeout== 0
02-25 20:14:09.454 1856 10366 D SensorService: SensorDevice::batch: ident=0x7d45906200, handle=0x0000000b, flags=0, period_ns=20000000 timeout=0
02-25 20:14:09.454 1856 10366 D SensorService: >>> curr_period=10000000 min_period=10000000 curr_timeout=0 min_timeout=0
02-25 20:14:09.454 1856 10366 D SensorService: >>> actuating h/w flush 11
02-25 20:14:09.454 1856 10366 D SensorService: recordConnection in enable
02-25 20:14:09.454 1856 10366 D SensorService: Calling activate on 11
02-25 20:14:09.454 1856 10366 D SensorService: SensorDevice::activate: ident=0x7d45906200, handle=0x0000000b, enabled=1, count=6
02-25 20:14:09.454 1856 10366 D SensorService: enable index=4
02-25 20:14:09.456 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.457 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.457 1856 3000 D SensorService: First flush event for sensor==11
02-25 20:14:09.457 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.670 1856 4649 V AlarmManager: set(PendingIntent{b855422: PendingIntentRecord{7a3d7df com.google.android.gms broadcastIntent}}) : type=2 when=1611406052whenElapsed1611406053m
axWhen =1611406053 win=0 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.720 1856 5072 V AlarmManager: set(PendingIntent{bb35eb3: PendingIntentRecord{7a3d7df com.google.android.gms broadcastIntent}}) : type=2 when=1611406052whenElapsed1611406104m
axWhen =1611406729 win=625 interval=0 flags=0x0 pkg = com.google.android.gms
02-25 20:14:09.457 1856 3000 D SensorService: flush complete event sensor==11
02-25 20:14:09.724 1856 10366 D OppoNlpProxy: OppoNlpProxy onlocation changed!!

Binamce must be teported by the masses

#unfair #profiting
Voiding coins on mayor market movements.

The list is endless.

When ypu want to buy the market rockets.

When you sell the market dives.

Buy nearly any profitable coin and 5 seconds later it will tank!

The small fish in the pond pay for the giants to have all the rights.

Im sick of it. Not keeping solent anymore.

Only Binance goes offline in mayor trades no other exchange.

If you know you have more users then surely you can upgrafe for the insane profits taken from us.

Report Bimance

ML Audioserver and Audioclient in devices directory

Hi Guys

Quick question, running rooted SM-G925 (Samsung Galaxy 6) with Version 7.0

IS anyone familar with audioserver and audioclient in /dev/socket/mlaudio ?

This appears to be comms for hardware bus via IPC unix socket streaming to audioserver in /system/bin


__
netstat -aWep

SEQPACKET LISTENING 15518 3182/audioserver /dev/socket/mlaudio/audio_server
SEQPACKET LISTENING 9022 3182/audioserver /dev/socket/mlaudio/audio_client
STREAM CONNECTED 43024 3182/audioserver
DGRAM 13491 3182/audioserver

Unsure best way to analyze pipes on android [43025], not unix socket like others on netstat

lsof

3182/system/bin/audioserversocket:[15518]
3182/system/bin/audioserversocket:[9022]
3182/system/bin/audioserversocket:[43024]
3182/system/bin/audioserversocket:[13491]

3182/system/bin/audioserverpipe:[43025]
3182/system/bin/audioserverpipe:[43025]

3182/system/bin/audioserver/dev/null
3182/system/bin/audioserver/dev/null
3182/system/bin/audioserver/dev/null

3182/system/bin/audioserver/dev/pmsg0
3182/system/bin/audioserver/dev/binder
3182/system/bin/audioserver/dev/snd/controlC0
3182/system/bin/audioserver/dev/cpuctl/tasks
3182/system/bin/audioserver/sys/kernel/debug/tracing/trace_marker
3182/system/bin/audioserver/dev/ashmem

Need to upgrade, looking for recommendation.

I need to upgrade from my LG G4 to some other device. My phone has started deleting apps every time I boot. I'm looking for a recommendation regarding what I should upgrade to. It does not necessarily need to be LG. It should probably not be longer than six and a quarter inches though so that it can fit in my 7-in running pouch.

I should add though, that I would like the SD card to be accessible without having to open the case.

MediaTek - Bypass SPFT Auth FIle

A contact of mine just sent me the following link to XDA News about someone that found a way to bypass SPFT authentication on a lot of MTK chipsets

https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/

I had to repost this here because this is pretty important. Anyone that has a compatible phone/chipset can now read and write partitions with SPFT like the good old days. No authentication file? No problem. Just run this python script before connecting and in a few short minutes you'll have full read/write access to the phone's partitions just like you wanted to have. Full instructions for how to use the exploit are on the XDA post linked above

Here's a list of compatible chipsets copied from the XDA post. I assume there MIGHT be others that will work, perhaps they just didn't try all of them yet. But if you have one in this list it should DEFINITELY work according to the XDA post
  • mt6261
  • mt6572
  • mt6580
  • mt6582
  • mt6735
  • mt6737
  • mt6739
  • mt6755
  • mt6757
  • mt6761
  • mt6763
  • mt6765
  • mt6768
  • mt6771
  • mt6785
  • mt6799
  • mt6873
  • mt8127
  • mt8163
  • mt8173
  • mt8695

Filter

Back
Top Bottom