yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] thedru13:
So jumped in with out doing enough research.. I just installed one of the double din android units in my car. I was able to get everything wired up and running. But not much is working well.

I got this unit

GCS APEX ANDROID HEAD UNIT W/ GPS - 2015+ WRX / 2015+ STI

Android Operating System Version: 5.1.1

Processor: 1.6Ghz Cortex A9 Quad Core

Memory: 1GB RAM, 16GB flash

Stereo Power: 4x50W

So the unit itself seems very slow. I installed 2 apps. Spotify and Waze. The apps take a long time to load/open.

Spotify. Ok this is odd but not sure if its normal. I open spotify and I have the HU paired with my hotspot. It loads and starts to play but the sound is awful. I am not able to control anything via the headunit for sound such as fader/balance/eq. They don't do anything. Now if i open spotify from my phone and cast it to the HU i have all those controls and it sounds 100x better but the volume can be adjust from the phone and have to set that low. Is that normal? I have tried to get the USB to work and it will charge my phone (iphone 7+) but the headunit won't recognize the phone at all. don't even give me an option to use it via usb. I can also connect via bluetooth and stream that way but its similar where I can adjust volume from the phone. Sorry if this is really n00bish but thinking maybe its a setting? I can't seem to find anything.

After doing some reading i guess the 1gb was not the way to go but stuck for now. so any suggestions? I just want to be able to use Waze, and spotify and have the unit respond. When I click a button the delay is not a second or two but over 50 seconds and seems like it just crashes. I clear the memory and dont' have any live wallpapers running just nothing seems to be responding at all

Hope this makes sense and or someone might be able to give me some insight. Thanks for any help.

I can't post the link to the actual unit since I don't have enough street cred with the forum yet.
[Android Head-Units] thedru13:
Any thoughts?
[Android Head-Units] boss126:
radio

My radio has the same specs as yours apart from the android version (4.4.2), i can confirm that Spotify and waze are both up and running within a second or two.

It does sound like you might have a faulty unit, is it possible to return it ?

You could also try a different rom but will kill any warranty I guess.
[Android Head-Units] thedru13:
Yah that is what i am worried about. The vendor is not so eager to exchange it. I am going to take some video of what I am talking about maybe that will add some detail. Maybe someone will see it and point out that I might be doing something wrong. Not sure but very frustrating.
[Android Head-Units] m00n61:
If yours is a MTCB/C unit (check the MCU version, it should start with this either MTCB or MTCC) you can flash a 4.4 ROM.

I also received my unit with 5.1 and downgraded to 4.4.
[Android Head-Units] thedru13:
So tried a bunch of things over the weekend. No luck. I did do a factory restore and then was not able to even log into the play store at all. Google services kept crashing. I tried all the trouble shooting I could find online with no luck. Also I was not able to get the USB connection to see my iPhone. I could plug in a thumb drive and it worked fine. Are these just not able to use an iPhone at all? Not sure if anyone has been able to get the USB connection working between headunit and iPhone.

I sent the unit back hopefully getting a replacement to continue to try and get it to work. If not guess I will look for something else.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] hemarx:
Hello Guys

i have a galaxy a5 with broken black screen and i wanna restore my stuff fromthe internal storage

the phone has a pattern lock and no usb debugging enabled and also not rooted

is there any solution that i can get at least my photos from it ?

thanks alot
[Nexus 6P Q&A, Help & Troubleshooting] jmaclean62:
I have tried DP1 and DP2 on my 6P and have found that both of them wouldn't connect with my Pumpkin Android Head Unit in my car. It would connect/disconnect constantly. This appears to be a known problem with many bluetooth devices, but not all, but still isn't fixed as far as I know.

Everything works fine on 7.0.

Would it be possible to flash something to get the bluetooth working on the 7.0 "version" of bluetooth and run the 7.1.1 for the rest. I am imagining the radio might work if I flash it somehow.

Thoughts?
[Nexus 6P Q&A, Help & Troubleshooting] boxguy1:
Use wugfreshes tool try a clean install

1.download wugfreshes Nexus toolkit

2. Follow setup and install the drivers from the toolkit by selecting Nexus 6P and 7.1.1 build

2a. Confirm that your PC detects your phone in bootloader

2b. Make a backup of media and pictures

2c. Unlock your bootloader inside the toolkit for all l the toolkit features to work

3. Go to TWRP wipe everything by going to advanced and format your phone this deletes everything including OS

4. Once you do that reboot to bootloader open Wugfreshes toolkit click on flash stock + unroot then select the new Android 7.1.1 build and follow instructions in the toolkit

5. Once it reboots set up your phone and restore your backed up content

6. Attempt connected to your device and see if the problem is gone

7. If it isn't gone revert back to 7.0 by booting to bootloader and using wugfreshes toolkit by click on flash stock but change build to latest 7.0 this will delete everything again and this should work as your final resort

Sorry about all the writing i wrote too much :silly: good luck ;)

---------- Post added at 07:47 AM ---------- Previous post was at 07:37 AM ----------

Radio builds have to correspond with Android version so it isn't possible but look at my other comment
[Nexus 6P Q&A, Help & Troubleshooting] santroph:
It is a known problem with BT on all cars stereos. Google is ignoring it...

https://productforums.google.com/fo...ce=footer#!msg/nexus/Mv5Hc6Lw7rA/bLJjs-W8DQAJ
[Nexus 6P Q&A, Help & Troubleshooting] jmaclean62:
I'll give this a try next week while I am on Winter break. Seems like based on what I have been reading it probably won't solve my problem, but it will give me something to do. :)
[Nexus 6P Q&A, Help & Troubleshooting] boxguy1:
You could revert to 7.0 and see if it works as you said it worked in 7.0
[General Questions and Answers] bigcheekybird:
I have recently replaced a broken screen of an apache with a new one and when i turn it on the screen turns on and is white, when I look at it side on I can see the devices screen is working but it is faded, e.g the today screen is there but very faded.

I was wondering what could be the problem?
[Xposed Framework Modules] QBANIN:
Hi,

This time I'd like to share with you my new module Unlimited CallLog which simply remove built-in limit of 500 records in call log :)

Compatibility:

It has been tested to work on AOSP MM and CM13, should work on LP and Nougat too...
[Xposed Framework Modules] sapthesh:
Thanks for the module... :fingers-crossed: :good:
[Xposed Framework Modules] rfilipoiu:
Hi,

If you backup, you get over 500, but how do proceed in order to actually see over 500 in the list of your dialer?
[Xposed Framework Modules] QBANIN:
Scroll the list to the oldest entries. ? ... And don't use ExDialer.
[Xposed Framework Modules] jaishreemataji:
I have j700f and install adavance seven rom v.2 but it doesn't work
[Xposed Framework Modules] QBANIN:
I have no idea what adavance seven rom v.2 is.
[Xposed Framework Modules] hoshos2006:
Didn't work on samsung MM stock twiz rom
[Xposed Framework Modules] luste:
Hi QBANIN, I use your module on 2 mobile, one with android 6.0, the second with 7.1. Both work and allow to store more than 500 calls. I see all of them when I generate call log backup. But they don't show in google dialer after scroll to the end of the log - still they are cut. On both phones I use the same version of google dialer - 11.0.164102751. Can you help with that?

Thanks!
[Xposed Framework Modules] QBANIN:
I can't say anything about Google Dialer coz I don't use it :) Both https://play.google.com/store/apps/details?id=com.dw.contacts.free&hl=en and stock CM dialer work fine with 500+ entries so it looks like GD issue to me...
[Xposed Framework Modules] jeepcook:
Doesn't work with LineageOs 14.1 and stock dialer...
[Xposed Framework Modules] QBANIN:
What about other dialers?

Wysłane z mojego XT1572 przy użyciu Tapatalka
[Xposed Framework Modules] jeepcook:
Not tried...which one?
[Xposed Framework Modules] QBANIN:
https://play.google.com/store/...com.dw.contacts.free&hl=en
[Xposed Framework Modules] jeepcook:
Oh no!! This app is very too ugly.....
[Xposed Framework Modules] QBANIN:
You don't have to use it, just tell me if it shows 500+ calls.
[Xposed Framework Modules] jeepcook:
The problem is not the number of shown calls but the real number of calls. It stay limited to 500 (test with sms backup and restore). The database contains only 500 calls, the older call is deleted when I have a new one.
[Xposed Framework Modules] QBANIN:
Ah, ok. I have to dig into Los 14 code then.
[Xposed Framework Modules] QBANIN:
Try this one and tell me if it works for you. I don't own any device running N therefore I can't test it.

EDIT: Buggy version, will reupload soon...
[Xposed Framework Modules] QBANIN:
Make a nandroid backup and try this. If it won't work and/or make your system crash please paste your logcat.
[Xposed Framework Modules] jeepcook:
I'll test this version tonight (France). Thanks

Envoyé en utilisant Tapatalk
[Xposed Framework Modules] QBANIN:
Any feedback?
[Xposed Framework Modules] jeepcook:
I have a lot if work currently, I will try the new version as soon as possible.

Envoyé en utilisant Tapatalk
[Xposed Framework Modules] jeepcook:
Tested: previous version need to be uninstalled (conflict). And the number of calls is still to 500, older call is deleted.

Edit: in fact last call is not registered !
[Xposed Framework Modules] QBANIN:
Logcat?
[Xposed Framework Modules] topmet:
Any solution for lineage 14.1 pls ?
[Xposed Framework Modules] QBANIN:
No logcat = no development
[Xposed Framework Modules] fatjoez:
Can you please add support for stock samsung android 7.0 (touchwiz)

Tried but didnt work
[Xposed Framework Modules] QBANIN:
Read my previous post.
[Xposed Framework Modules] QBANIN:
New test build...
[Xposed Framework Modules] dn_1983:
The version 1.1alpha works good on Android 7.

Thank you for this great work.
[Xposed Framework Modules] topmet:
1.1 work, lineage 14.1 !
[Xposed Framework Modules] Barruel:
Partially (LineageOS 14.1 10/26), but it seems to be LOS fault.

Restored XML with 2700+ calls with TiBu. Statistics show data from all my 2700+ calls, and missed calls show data from february, but "all" calls section and the history tab in the start Phone app screen show only calls back to july.

When in the "All" calls section, filtering by incoming, outgoing, missed, etc do indeed show calls prior to july.

Probably a hardcoded 500 calls display limit on LOS. This Xposed module seems to be working fine.
[Xposed Framework Modules] QBANIN:
Try a different dialer, ie. https://play.google.com/store/...com.dw.contacts.free&hl=en and let me know if anything has changed. Don't use ExDialer as it has hardcoded 500 calls limit.
[Xposed Framework Modules] Barruel:
That dialer (DW Contacts) shows even less calls. It only goes back to august. Just end of july filtering by outgoing.
[Xposed Framework Modules] QBANIN:
Perhaps your backup XML is broken? Try deleting phone history data and restore once again.

What happens when you make a call and then re-run backup? Does it show +1 (or more) calls?
[Xposed Framework Modules] Barruel:
Unlikely. It is a plain text file, and the restoring process progresses call by call without sign of corruption.

Besides, the "Statistics" section on LineageOS Phone app shows data for all calls, and by filtering the calls I can see the older calls.

Also, restoring that same XML shows the full call log on older Android (stock Lollipop Moto G3).

New calls after backup are added to the log as expected. The oldest call shown in the log is still the same july 3 call. It doesn't show calls past it for some reason, but new calls don't delete oldest calls.

If I make a call and re-run backup, the full call log is overwritten by the backup.
[Xposed Framework Modules] jeepcook:
Same problem with stock lineageos dialer. Database is correct, first call in September 2016 is in it but only calls from 2017 May and recents are showed.

Edit: same problem with Google dialer

Envoyé en utilisant Tapatalk
[Xposed Framework Modules] QBANIN:
As I already said I don't own any N-running device so it's quite difficult to debug this kind of issue... You can run the following test to narrow down possible causes:

1. Run a backup on M-running device

2. Move it N-running device and restore

3. Backup again on N-running device.

4. Compare both XML files (from M and N) in text editor and look for differences if there are any.
[Xposed Framework Modules] Barruel:
I used a backup from L, not M.

Files are identical. Only difference was a 'geoLocation=""' tag void in a single call entry. Had a value in the L file but none in the N XML.

BTW, I don't think that TiBu is the culprit. The call database is restored OK.
[Xposed Framework Modules] QBANIN:
Can you try to count approx. number of calls VISIBLE in call log?
[Xposed Framework Modules] QBANIN:
alpha 2 for testing...
[Xposed Framework Modules] Barruel:
Exactly 993 right after restoring the XML.

But new calls don't hide older calls.

---------- Post added at 04:14 PM ---------- Previous post was at 04:08 PM ----------

Didn't fix the issue. It stops showing the calls in the same call it did before.
[Xposed Framework Modules] QBANIN:
Well... 1000 visible calls limit is hardcoded into both MM and N stock (and probably Google) dialer including LOS 13/14. I can try to fix it in this xposed module, but what's more interesting that https://play.google.com/store/apps/details?id=com.dw.contacts.free&hl=en is limited in N as well, coz it displays unlimited calls in MM without any issue, at least in my case...

Please reinstall dialer linked above and try to modify/increase settings->history default limits.
[Xposed Framework Modules] Barruel:
That feature is only available for paid licenses.
[Xposed Framework Modules] QBANIN:
Until I figure out how to hook stock dialer you have to look for a 3rd party dialer without call log limit.
[Xposed Framework Modules] vsrkmurthy:
Hi,

I have been using Redmi SD phones eversince their launch of Redmi 1S in India around 5 years back. For unlimited Call Log, it is the best device I have ever used. To be more clear my phone, right now had a call log history of around 38K (you heard correctly, it is 38823 entries as of this moment),

I have 1 more device of Samsung J700f, the first version with 1.5gb ram and 16gb rom variant.

Instead of this rooting and installing exposed, can we port the dailer of redmi to any of other devices ?

Earlier I had, Lava Iris x8, 2gb and 16gb variant, ported miui8 rom to that and even also can maintain same unlimited amount of call logs.

Baased on this my message, please let me know whether we can do any miracle to other devices in a very simplified manner to make the default call log as unlimied ? of course, I agree, rooting is mandate.

Refer this post http://en.miui.com/thread-1518113-1-1.html
[Xposed Framework Modules] ThunderStormer:
Pie Support

Any interest in supporting Pie?

Some pointers that might help: https://xdaforums.com/xperia-t-v/guide-how-to-make-call-log-limit-t2866632

I'd really appreciate an updated version..

Thanks.
[Xposed Framework Modules] QBANIN:
V 1.2 - should be compatible with all Android versions from LP to P (Q untested)

It's also available for download from xposed beta channel.
[Xposed Framework Modules] bountyman334:
thanks for this will try on Razer phone 2 with stock Pie nov 2020 update
[Xposed Framework Modules] QBANIN:
v 1.3 - bugfixes
[Xposed Framework Modules] QBANIN:
- few more fixes
[Xposed Framework Modules] xxy0:
Initially installed v1.2, then v1.3 & v1.4 couldn't be installed . After uninstalling v1.2 and rebooting, v1.3 & v1.4 still couldn't be installed, but v1.2 could be.

Rom is 3rd-party android 10, edxposed 0.4.x - 0.5.x

How to solve this problem? Thanks
[Xposed Framework Modules] QBANIN:
Does v1.2 work for you?
[Xposed Framework Modules] xxy0:
v1.2 seemed to have worked, i can't recall this very clearly now.

v1.3 & 1.4 seems to work well on another device now.

If v1.2 works, is it necessary to update to v1.3 or v1.4 or those will be published in the future?
[Xposed Framework Modules] xxy0:
In LSPosed, this module is always gray after installation. Does this mean the module isn't enabled?

If yes, to enable this module, on which apps the module should be enabled/checked?

I guess com.android.providers.telephony & com.android.server.telecom
[Xposed Framework Modules] blkswanpres:
Does this still work? Wanting to try it on a Pixel 6a
[Xposed Framework Modules] maxs8007:
does this work in android 12?

Edit : Version 1.4 doesn't work on android 12. Cannot save more than 3000 call log limit of A12.
[Xposed Framework Modules] ar.les:
hi did you manage to solve this problem somehow?
[Xposed Framework Modules] maxs8007:
No
[Xposed Framework Modules] devilosmania:
Which version may work with android 13.

Instead it is possible to modify directly the java file using a root explorer without the need of extracting and compiling a ROM??

Details in this link:

https://xdaforums.com/t/guide-updated-mod-how-to-make-call-log-limit-practically-unlimited.2866632/post-57965986
[Xposed Framework Modules] Vilino:
Tired of waiting for someone to offer a solution, I had to do it myself.

Here is the solution for android 13

[MOD][Xposed] Unlimited Calllog for Android 13(Tiramisu)

Hello! In an attempt to find a working solution for an unlimited call log on Android 13, I had to write a module myself. The logic of the work is to intercept the addEntryAndRemoveExpiredEntries function and instead execute the same code from...

xdaforums.com
[G4 Q&A, Help & Troubleshooting] atsamoon:
Hi

I have owned an lg g4 T-Mobile for a few months now and it's on stock marshmallow and it's been working fine up till recently.

Here is the issue

1) phone sometimes doesn't recognise the charger, I tried different cables and chargers with the same result, although the problem was more consistent with a quick charger 2.0.

2) phone sometimes recognises the charger but I leave it plugged for an hour and the phone doesn't charge at all.

3) I used to charge my phone using a quick charger 2.0

4) no change in battery life

5) everything else is fully functional.

6) I stopped using the quick charger since and the phone has mostly been charging normally, I don't know how to explain it but after stopping charging with the quick charger, other chargers started charging normally again.

I can use the regular charger with no problems but I really miss the fantstic quick charging.

Could the quick charger have actually damaged the phone, is it safe to use it ?
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
Today I just want to share how to disable capacitive button and enable On Screen Button on Redmi 3 Pro CM14.1 Official, but this mod should work for any devices and any ROM.

I was try with some devices and its work

REQUIREMENTS

-ROOT ACCESS

-File Manager (ex. LCG X-Plore or Root Explorer)

Step 1

- edit build.prop and add line

"qemu.hw.mainkeys=0" without quotes

- open file manager and go to dir. system/usr/keylayout/generic.kl

Edit with text editor the file "Generic.kl" and find

key 158 BACK

key 139 MENU

key 172 HOME

key 217 SEARCH

Edit these line to

#key 158 BACK

#key 139 MENU

#key 172 HOME

#key 217 SEARCH

*Yes just add "#" symbol to the start of these lines* and then SAVE and Reboot.

I recommend to use X-Plore by Lonely Cat Games

Here the guide at YouTube

[youtube]c-xhd3gVeVA[/youtube]

Dont forget to hit thanks button guys. :)
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
Some Screenie here :good:
[Xiaomi Redmi 3 Guides, News, & Discussion] michiamoantonio:
Awesome man! May I ask a question? Which rom are you using?

Inviato dal mio Redmi 3 utilizzando Tapatalk
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
Im using Official CM14.1 by Anik, pals. But I was try on CM13 and MIUI 8 Global dev its working also ;)
[Xiaomi Redmi 3 Guides, News, & Discussion] michiamoantonio:
Thanks mate! I used with 71.0 mokee but my navbar is in MM style. But yours is N style

Inviato dal mio Redmi 3 utilizzando Tapatalk
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
No no its not bcoz of the rom, I was modify my systemUI, :)
[Xiaomi Redmi 3 Guides, News, & Discussion] michiamoantonio:
How? Theme engine is not present in cm 14.1

Inviato dal mio Redmi 3 utilizzando Tapatalk
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
Just pull out systemUI, unpack the APK and change the navbar icon and repack again then put it back
[Xiaomi Redmi 3 Guides, News, & Discussion] AleShark:
how can i able it again?
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
Just delete "#" symbol at 1st post in "generic.kl" file
[Xiaomi Redmi 3 Guides, News, & Discussion] AleShark:
i cant find dir.system
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
What file manager r u using? Have ur phone rooted?
[Xiaomi Redmi 3 Guides, News, & Discussion] AleShark:
I resolved, thanks
[Xiaomi Redmi 3 Guides, News, & Discussion] CallMeBb:
yep, it's worked on CM13 or even CM14, but in Custom ROM like RR, you just put "#" on system/usr/keylayout/ft5x06_720p.kl

You should add it, in generic.kl it doesn't work for me :D or i'm mistake?
[Xiaomi Redmi 3 Guides, News, & Discussion] Kuato:
Yes on specific Rom like RR, thanks to remind me mates :good:
[Xiaomi Redmi 3 Guides, News, & Discussion] Selvakmr123:
Not working
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] nikkali25:
#Disclaimer

Your warranty is now void.

I am not responsible for bricked devices, dead?*SD?*cards?*, ...

Please do some research if you have any concerns about Custom Build Roms before flashing it!

#Supported devices

Lenovo k4 a7010 a48?*That Upgraded To MM

#differences

V2 plan to do

*rename rom since remove pixel apps

*Ported sony apps

*theme framework/system ui

#nothing happen if you sony help me.

*bravia mod

*

V1changelog

*base to nikkali rom v3

*init.d and insecure on kernel

*fast boot

*pre rooted w latest supersu v2.79

*fast build

*busybox

*super tweaked

*arise sound mod

*keyboard change to sony

keyboard

*video change to sony video

* sony bravia mod

*galery change to sony album

*launcher change to sony home

*boot change to pixel boot animation

*device sound mod

*sms change to Pixel/google sms

*contacts change to Pixel contacts

*dialer change to Pixel dialer

*build prof tweaked

*system is modified to maka all

sony apps is downloadable

*clock from sonny

*email change sonny email

#download

V1:https://mega.nz/#!el5SRJyZ!NkGxmR5gSJEbSVZEsVH5ZkTaQrzl669vgPEtPxLXOF0

#how to install

*boot into recovery

*wipe system,data,dalvic and cacher

*flash sony-pix zip

*reboot in system.

#bug: can not send sms.

Sol:after completing the first boot,please select a sim for sms.

Reported f.c on contact.

-------do not update web view--------

#thanks to:

*lenovo for stock

*chainfire for super su

* superr kitchen

*4pda

*google

Comment

*i am only sharing my daily use rom

*i am not a developer,found bug/s help me or share your solution

#screen shot

xxxxxsmsxxxx

xxxxxcontacts and dialerxxxxx
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] sabeehp:
where is the download link? cant see anything

where is the download link
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] nikkali25:
I upload till sunday
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] hirencj:
Wow sounds great... Volte support must bro in the rom .. thank-you
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] sharan565:
which build base s219 or s230?
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] nikkali25:
Here is the base row 230 in my nikkali rom v3..some[/url] one reported that volte is working
[Lenovo Vibe K4 Note ROMs, Kernels, Recoveries, & O] nikkali25:
Yes.row 230 volte is ok