Related
I've got this issue where incoming calls and texts are not matching to the contacts database when the international format is used (so incoming 01202 123456 matches if the number is stored in the phone book as 01202 123456 but not if it's +441202 123456)
Seems it's quite common with ROMs / Phones from China.
My phone is a Cube 5H A5300 (a remarkably good bit of kit for the money if I could fix this dam issue) , Android 4.2.1, and MIUI 3.11.15. I don't think this is a MIUI issue hence posting here.
I've been through the suggestions that seemed to offer the best chance of a fix :-
Changing the MIN_MATCH in framework.jar and MMS.apk, and checking that strict comparison if odd from here http://forum.xda-developers.com/showthread.php?t=2268120
Adding ro.phone.min_match=7 to build.prop from here http://forum.xda-developers.com/showthread.php?t=1160343
Various other suggestions relating to stuff in settings.
So I'm at a lost to know where to go next.
Anyone got any suggestions about where number matching is handled in Android? Where can I look for places to check ?
John
Exactly the same problem, also UK
Incoming calls show up in the format 07785 nnnnnn but my phone book has the numbers stored in +44 7785 nnnnnn format, with the result incoming calls only show the number and not the detail in my contacts/people.
I also tried ro.phone.min_match= using 9 and 7 as variables but it made no difference
I have the THL W8s running Android 4.2.1
Brilliant phone but his bug is killing it for me.
Really look forward to a solution
I found the solution for bog standard Android devices, I have a THL W8s running 4.2.1 but it should work on Androids 4.1.x / 4.2.x / 4.3.x according to the threads below.
No credit to me, all down to the guys on XDA, but as a bit of novice it took me ages to trawl all the posts on this subject before finally finding the solution that worked - and easily. It will also avoid you installing lots of apps of playstore that for me anyway either didn't work or gave a poor hack of a work around. In addition, this solution provides a whole host of other fixes and enhancement, brilliant piece of work from the two developers.
Start by removing all your contacts, either export/delete from People to re-import or as in my case delete the corporate email/contacts account
Tip: Reboot after almost every step
1) Your device must be rooted
2) You must be able to install apps direct from your phone: System Settings / Security / Unknown Sources (Unknown Sources may be in a different place)
Then the heart of it:
Install the Xposed Framework
http://forum.xda-developers.com/showthread.php?t=1574401
Full instructions in the thread
Then install GravityBox it's not the a ROM, just the Xposed Framework Module
http://forum.xda-developers.com/showthread.php?t=2316070
Again, full instructions in the thread (Make sure you have a tick next to Gravity Box in the Xposed Framework and reboot)
Then: GravityBox -> General Fixes -> Fix Caller ID
Reboot, re-add or re-import your email/contacts, either add the account or import from contacts and there you go, fixed.
Here's one that didn't work for me but may be worth a try if your version of Android isn't supported with the above solution:
Search on: ro.phone.min_match= where you put a 9, 8, 7 etc after the =
I used ES File Explorer to mount /system R/W and edit the build.prop file, but as I said, after ages of hacking around to get the fix in it didn't work for me.
BTW: I bought the THL W8s after busting my HTC One and not wanting to shell out too much to replace it. All-in-all I'm very impressed with my cheap Chinese Android phone (£155 on eBay), and now that this bug is fixed I'm really chuffed with it. The dual sim/dual standby function saves me carrying two phones, another bonus.
552446934
Thx for posting this, but didn't work for me. Hope it works for others as this is a great bunch of apps.
I'm wondering if my issue is related to the phone (Cube 5H which is a MTK6589 product) or the MIUI ROMs. I'm getting to the point where I think I might need to give up and get a different phone, but I feel the same way about this phone as you do aout the THL - if I could fix this issue it would be a great value for money phone
whalesg said:
I found the solution for bog standard Android devices, I have a THL W8s running 4.2.1 but it should work on Androids 4.1.x / 4.2.x / 4.3.x according to the threads below.
No credit to me, all down to the guys on XDA, but as a bit of novice it took me ages to trawl all the posts on this subject before finally finding the solution that worked - and easily. It will also avoid you installing lots of apps of playstore that for me anyway either didn't work or gave a poor hack of a work around. In addition, this solution provides a whole host of other fixes and enhancement, brilliant piece of work from the two developers.
Start by removing all your contacts, either export/delete from People to re-import or as in my case delete the corporate email/contacts account
Tip: Reboot after almost every step
1) Your device must be rooted
2) You must be able to install apps direct from your phone: System Settings / Security / Unknown Sources (Unknown Sources may be in a different place)
Then the heart of it:
Install the Xposed Framework
http://forum.xda-developers.com/showthread.php?t=1574401
Full instructions in the thread
Then install GravityBox it's not the a ROM, just the Xposed Framework Module
http://forum.xda-developers.com/showthread.php?t=2316070
Again, full instructions in the thread (Make sure you have a tick next to Gravity Box in the Xposed Framework and reboot)
Then: GravityBox -> General Fixes -> Fix Caller ID
Reboot, re-add or re-import your email/contacts, either add the account or import from contacts and there you go, fixed.
Here's one that didn't work for me but may be worth a try if your version of Android isn't supported with the above solution:
Search on: ro.phone.min_match= where you put a 9, 8, 7 etc after the =
I used ES File Explorer to mount /system R/W and edit the build.prop file, but as I said, after ages of hacking around to get the fix in it didn't work for me.
BTW: I bought the THL W8s after busting my HTC One and not wanting to shell out too much to replace it. All-in-all I'm very impressed with my cheap Chinese Android phone (£155 on eBay), and now that this bug is fixed I'm really chuffed with it. The dual sim/dual standby function saves me carrying two phones, another bonus.
Click to expand...
Click to collapse
I'm surprised because the Garvity Box solution was designed around the MT6589 products (I think I read somewhere), my phone is MT6589T.
I did read somewhere that the solution wouldn't work on highly customized ROMs and I think that included MUI. Did the phone come with MUI factory installed, if there is a standard AOSP build for your phone it is probably worth a try using that.
Pity, I nearly threw a party when it worked for me, I'd been hacking around for days.
The phone doesn't come with a full MIUI ROM, just the "themes" part of it. But I really wanted to give MIUI a shot hence me putting the whole ROM on. Good point though - I've been toying with putting the original build back on to see if it fixes the issue. Then I'll know if it's a phone thing or a MIUI thing.
Glas you got yours going though. I crossing my fingers for that party moment!
whalesg said:
I'm surprised because the Garvity Box solution was designed around the MT6589 products (I think I read somewhere), my phone is MT6589T.
I did read somewhere that the solution wouldn't work on highly customized ROMs and I think that included MUI. Did the phone come with MUI factory installed, if there is a standard AOSP build for your phone it is probably worth a try using that.
Pity, I nearly threw a party when it worked for me, I'd been hacking around for days.
Click to expand...
Click to collapse
Strangely - just noticed that numbers in "recent" are now being listed with the correct name matched to the phone book. If I turn off Gravity Box this stops happening, so Gravity Box is having some affect. Just a shame it's not on incoming calls.
johnhelliwell said:
Thx for posting this, but didn't work for me. Hope it works for others as this is a great bunch of apps.
I'm wondering if my issue is related to the phone (Cube 5H which is a MTK6589 product) or the MIUI ROMs. I'm getting to the point where I think I might need to give up and get a different phone, but I feel the same way about this phone as you do aout the THL - if I could fix this issue it would be a great value for money phone
Click to expand...
Click to collapse
The Lenovo Yoga Tab 3 does not come with multi-user, so I've been trying to set it up so my family can actually share the tablet without kid-adult conflicts. I'm running Android 5.1.1
As suggested in a number of forums, I've rooted the device and modified build.prop to include:
fw.show_multiuserui=1
fw.max_users=8
The two lines of code are in the build.prop file after rebooting the tablet and "pm get-max-users" in adb shell returns 8, so the two lines of code are in there. However, there is no multi-user icon either next to the settings on the lock screen or the swipe-down menu (next to settings icon, where I hoped it would be). So I cannot add or switch users.
I've tried manually adding users through the adb shell using "pm create-user [username]" with no luck...they may exist in the back-end somewhere, but as a tablet user I can't see them.
I've tried rebooting several times, removed screen lock, and eaten a bunch of chocolate but nothing seems to work.
Any help would be much appreciated!
same issue for S8-50 running 5.0.1. actually the profile section can be found in settings if search for 'profile' . from there the user can also be switched but that's about it - no ability to switch between users in lockscreen
I bought two tab3 10" 16GB for the kids for xmas, and they had a "Users" entry in the settings, but no user avatar in the quick settings.
It seemed pretty good, so I bought another of the 32 GB version for myself and my wife and that has neither. However, I was able to set up user accounts for us by searching for users in the settings menu, so it appears to be there. Unfortunately, it doesn't allow any sane way of switching users, since one has to be logged in as a user to do it... It cannot possibly be considered a good idea to do this, it has to be a bug...
I'd be very interested in a solution to this problem too.
any findings an that so far? How to "search for 'profile'" Am on tab 2 a8-50f, with mentioned changed in build.prop but no options in settings
It is actually as simple as kjekje suggests.
Open the settings tab. Instead of scrolling up and down and looking in every submenu for a "users" section like i did, just click the magnifying glass icon and search for "users". Seems like Lenovo have just hidden it from the menu.
Further broken in 6.0.1
I just upgraded the tablet to 6.0.1 yesterday, as it was pushed by the usual channels. Figured it couldn't make it any worse. It did
Now, if I search for users, I can switch to a restricted user, but I cannot switch back, because there's no option for it when I search for it in restricted mode.
So, I would still be very interested in a better solution to this problem? The only good solution is to be able to switch users when the screen is locked. Anybody found anything by further digging?
I don't know why on earth Lenovo is doing this to us. Perhaps they figure we will buy another tablet if there's no multiuser...? But it surely won't be a Lenovo, they ought to understand that.
Lets say I want to enable disk access to "drives" (a great software product to display dive space utilization), I can not do so there is no way to do so as I get a message "Screen Overlay detected", of course it is detected I have over 10 apps that require it, if I disable it they do not work PERIOD. so I need to have it enabled, nut then I have many apps that simply do not support Marshmallow (6.0) at all as a result. I can not understand why there are not more complaints and fixes for this as I'm basically stuck I have apps that require overlay including my dialer and I have apps I need that I can not use if overlay is enabled!
One work around I heard of was to boot into safe mode and run the apps there, but in safe mode I can not run any third party apps (so I can not execute those that I need to overlay disabled to set a permission.
I need help, either to fix the overlay prompt (simply put at this point security be damned I'll live without it I need the software to function), but searching and searching I've yet to see any solution or even suggestion beyond safe mode, which does not let me execute the software I need to fix, other than down grading (which does not help since at some point I'll need to move to 6.X), how does one fix the very annoying and Android breaking issue of overlay?
I just do not understand how Overlay a very necessary feature is also able to break many apps, including a few that require overlay themselves. I'm completely confused and sick of wasting time (hours at this point trying to figure out how to get around this).
Thanks,
ERIC
So I came into possession of a commercial grade advertising kiosk (Nintendo Amiibo Display) that runs an Android OS 4.1.1. The device is setup to auto load the "AmiiboFrameWork.apk" package installed. The model of the system is DucoTech D185-ACA-720. I can access basic Android settings menus through a special key combination. Mainly system information, network setup, and volume controls. There is a menu that says App Install and gives the option of installing APKs from SD card or USB with a file structure of USB:\APKFiles\ or SD Card:\ApkFiles\. However no matter how I layout my file structure or name my APKs following that structure nothing appears in this menu to install. However There is a media tab for photos with a similar structure and photos I put on the card do show up. What I'm trying to figure out is how either install APKs, or access the base android system so I can customize the system to run custom apps I plan on making for it. However I want to retain the original AmiiboFrameWork APK or the whole OS so I can restore the system later if I want.
Now what I have tried is plugging it into my PC via the USB-OTG port while on, putting APKs in various file structures and naming conventions, booting it with my PC connected via OTG port, tried to trick my way into other menus through keyboard and settings menu tricks (similar to how people use to bypass lock screen security through menus).
Results:
1. OTG to PC while on: Device shows up as 2 USB 2.0 Flash drives in device manager. The drives appear in my computer but aren't accessible. ADB doesn't see it as an android device.
2. APKs on usb: Nothing shows up in the menu regardless of my naming convention or file structure.
3. Boot device while attached to PC via OTG port: My computer detects it as an NES Classic (previously installed the driver to mod my classic). This leads me to think its an Allwinner device or similar since that is what the driver was made for I believe? ADB still doesn't see it. This might be my best bet to get in.
4. Menus: Options are very limited and I wasn't able to access anything valuable aside from Install APK, Transfer Media, and Set startup APK.
5. Tapping build number: Tapping the build number in settings any number of times doesn't activate the developer mode options. The prompt doesn't even appear for it.
If anyone can assist in trying to gain access to this system, or even figure out the file structure so I can just install my own APKs like I want that would be great. Any ideas on where to look, what to try, and so on is greatly appreciated.
Here are some photos of the main board just in case
Any new updates to this? I made the mistake of uninstalling the Amiibo Framework APK so now all I can do is see the settings menu with no ability to install any APKS. Copying media files over does work though.
hedburnr said:
Any new updates to this? I made the mistake of uninstalling the Amiibo Framework APK so now all I can do is see the settings menu with no ability to install any APKS. Copying media files over does work though.
Click to expand...
Click to collapse
IDK what to say man other than what in God's name made u think framework.res needed to be pulled. It's gone man barring the original firmware and itself install method
hedburnr said:
Any new updates to this? I made the mistake of uninstalling the Amiibo Framework APK so now all I can do is see the settings menu with no ability to install any APKS. Copying media files over does work though.
Click to expand...
Click to collapse
I work with Ducos! In fact there's an Amiibo kiosk a few feet from me here in our offices
mojoswagger1980 said:
IDK what to say man other than what in God's name made u think framework.res needed to be pulled. It's gone man barring the original firmware and itself install method
Click to expand...
Click to collapse
AmiiboFramework doesn't have anything to do with the "framework.res", Nintendo just called the app the "AmiiboFramework"
They only install APKs with a specific package name in a specific folder on your USB device / SD Card (com.general.mediaplayer.player). Unfortunately Nintendo used a different folder than us, and I don't recall what it was. You can go into a "normal" Android screen using a special procedure if the AmiiboFramework app is installed, but it should work without it too:
- Wait for the Loading screen to appear
- Begin to press the CSR and Setup buttons together, quickly alternating between them. Repeat until the CSR appears
- After the CSR appears, leaving the screen open for an extended period of time will cause the Amiibo Display Framework to re-appear
- If Alt+Tab is used, be sure to return to the CSR before returning to any other app, or the CSR will reboot the player
Alt+Tab refers to using a USB keyboard, after you have the CSR up you can exit with it.
They're really not great hardware for general usage.
selaliadobor said:
I work with Ducos! In fact there's an Amiibo kiosk a few feet from me here in our offices
AmiiboFramework doesn't have anything to do with the "framework.res", Nintendo just called the app the "AmiiboFramework"
They only install APKs with a specific package name in a specific folder on your USB device / SD Card (com.general.mediaplayer.player). Unfortunately Nintendo used a different folder than us, and I don't recall what it was. You can go into a "normal" Android screen using a special procedure if the AmiiboFramework app is installed, but it should work without it too:
- Wait for the Loading screen to appear
- Begin to press the CSR and Setup buttons together, quickly alternating between them. Repeat until the CSR appears
- After the CSR appears, leaving the screen open for an extended period of time will cause the Amiibo Display Framework to re-appear
- If Alt+Tab is used, be sure to return to the CSR before returning to any other app, or the CSR will reboot the player
Alt+Tab refers to using a USB keyboard, after you have the CSR up you can exit with it.
They're really not great hardware for general usage.
Click to expand...
Click to collapse
Ohh, I tried to call and they wouldn't answer any of my questions lol. Is it possible to get any documentation on it? I'm sure Nintendo did their own setup, but having original documentation is a good step forward for what we have now. I'd love to setup my own configuration on it even if the hardware is meh.
Enmity said:
Ohh, I tried to call and they wouldn't answer any of my questions lol. Is it possible to get any documentation on it? I'm sure Nintendo did their own setup, but having original documentation is a good step forward for what we have now. I'd love to setup my own configuration on it even if the hardware is meh.
Click to expand...
Click to collapse
There isn't much more documentation than what I mentioned unfortunately. The people who you'd get in a call definitely don't know anything about them (I don't think Nintendo made the AmiiboFramework app in-house either). If you want to repurpose it, you can try getting into the CSR and going into the normal Android Launcher. Try connecting over ADB and force-stopping any process with the letters "csr" in it's name
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
Enmity said:
Ohh, I tried to call and they wouldn't answer any of my questions lol. Is it possible to get any documentation on it? I'm sure Nintendo did their own setup, but having original documentation is a good step forward for what we have now. I'd love to setup my own configuration on it even if the hardware is meh.
Click to expand...
Click to collapse
There isn't much more documentation than what I mentioned unfortunately. The people who you'd get in a call definitely don't know anything about them (I don't think Nintendo made the AmiiboFramework app in-house either). If you want to repurpose it, you can try getting into the CSR and going into the normal Android Launcher. Try connecting over ADB and force-stopping any process with the letters "csr" in it's name
To connect to ADB use a USB mini cable on the "USB OTG" port and ClockworkMod's Universal ADB Driver
I have a few devices similar to this. They are duco DT156-AS4-1080. I was wanting to repurpose them as video players. The devices are wiped of content and load into a main menu. There is an option to exit to administrator, though it asks for a password. I dumped the partitions and tried to look through the binaries, but am unable to come up with anything. I can get into superSU and then exit to playstore, but then some type of watchdog kicks me back to the duco menu. Any help appreciated.
er0ck said:
I have a few devices similar to this. They are duco DT156-AS4-1080. I was wanting to repurpose them as video players. The devices are wiped of content and load into a main menu. There is an option to exit to administrator, though it asks for a password. I dumped the partitions and tried to look through the binaries, but am unable to come up with anything. I can get into superSU and then exit to playstore, but then some type of watchdog kicks me back to the duco menu. Any help appreciated.
Click to expand...
Click to collapse
Just uninstall com.general.mediaplayer.* (anything that starts with that package name) and you should have a normal device
I DID IT! Working tablet
So the story is yesterday I found an Amiibo display at my apartment dumpster where people put stuff they don't want that still works, I nabbed it with the intention of salvaging the "monitor." Judging by the hammer-marks on the acrylic enclosure, and pry marks on the metal cage that held the power supplies for the led strips and the tablet I assume somebody took it home, got frustrated by the locks and screws after some prying, and just busted in the acrylic window to get to the floor model Amiibos.
I cracked it open, and after some fun with a butane torch to melt the acrylic around the screws open (damn security hex) was surprised to find that the "monitor" had a usb dongle plugged into it. I plugged it into my station and found it was a 2.4/5 GHZ wifi dongle.
All code here is from Windows power shell since I don't like to dual boot my main gaming rig. Usually I just use the Bash on Ubuntu on Windows developer option for stuff like this, but I didn't know if the fact I was using Windows usb drivers to connect to this would cause problems and I wanted one fewer step to troubleshoot if I had issues. Forgive me penguin for I have sinned.
I found the item number on the back of it and after some googling found it was an android device. Score!
I plugged the tablet in and it went into an Amiibo advertisement kiosk mode.
After about 8 hours I now have a limited (but functional!) giant Android tablet.
To any future adventurers I am making a guide to get you up and running quickly.
I followed selaliadobor's instructions:
To connect to ADB use a USB mini cable on the "USB OTG" port and ClockworkMod's Universal ADB Driver
Click to expand...
Click to collapse
As well as pressing CSR and Setup to get into the settings screen. This was interesting, but ultimately didn't do much. However using
Code:
./adb shell logcat >> log.txt
and waiting for it to reboot from the csr menu led me to find (with some help from my engineer father) that /system/app/CSR_A003_20160304_BT.apk was the culprit of the restarts.
This was solved with
Code:
./adb shell rm /system/app/CSR_A003_20160304_BT.apk
From there I was stuck. But then I discovered: THE CSR SETTINGS MENU IS NOT THE REAL ANDROID SETTINGS MENU. To get to the real android settings menu use this:
Code:
./adb shell am start -a android.settings.SETTINGS
This allows you to do a factory reset!
However when it reboots the default launcher is stripped of important features like back/home/running apps, keyboard, a launcher etc. I sideloaded the following apps:
Chrome Browser
Microsoft Arrow Launcher (I originally used Nova but it was too much a ram hog to be useful)
Multiling Keyboard (I originally used Swiftkey, but it too was taking up too much ram)
WebTube (stripped down youTube frontend)
Soft Keys (so I had a home and back button, the running apps button still doesn't work :'( )
First post so no links ;(
imgur .com/dGAOmoM
This is what it looks like after boot. I may also have an affinity for Amiibos.
imgur .com/uQ8u7js
Classic.
Quick note: This device doesn't support google play services, so no hulu, official youtube, netflix unfortunately. Try as I might I haven't found a solution.
i bought a box of these units a while back from the carboot and wanted to use them in our coffee shop were opening, i too didnt have much luck with them then i saw this thread, i know abit about computers but never messed with android, we basically wanted to use them for what they are used for now for displaying changing menus and advertising etc, i downloaded the clockworkmods adb, now how to enter the "./adb shell logcat >> log.txt" etc, presumably i just connect the otg port to the pc (win10) run the clockworkmod program then i use commandpromt? i did try it but i couldnt get it to work, do i have to put the android device into a mode like csr? any help would be appreciated?
N/A
Additional help needed
i got to the settings menu but it is only temporary i am wanting it to be like a regular tablet where can i get a rom to do that? to flash it so it will function like a galaxy tab 3 or so, as i would love to use my DT101-ASA-800 like a normal tablet with a keyboard and mouse. any help would be welcomed. as the factory reset doesn't let it work any different it keeps going straight to CSR settings.
so stuck... my head hurts
so i can not get my Model DT185-ACA-720 to connect to my pc..... ok it connects and a K: and F: drive appear but I cant access them. I managed to get .apk files to show up and transfer to the 12gb storage on the tablet but i cant access the storage on the tablet... im so lost... I downloaded the universal driver and ADB but both changed nothing... If anyone has any advice or updates im all ears since I basically destroyed the Kiosk to get this tablet free
jaybanc said:
i bought a box of these units a while back from the carboot and wanted to use them in our coffee shop were opening, i too didnt have much luck with them then i saw this thread, i know abit about computers but never messed with android, we basically wanted to use them for what they are used for now for displaying changing menus and advertising etc, i downloaded the clockworkmods adb, now how to enter the "./adb shell logcat >> log.txt" etc, presumably i just connect the otg port to the pc (win10) run the clockworkmod program then i use commandpromt? i did try it but i couldnt get it to work, do i have to put the android device into a mode like csr? any help would be appreciated?
Click to expand...
Click to collapse
Same issue here with the DT133-AC4-900 that I managed to pull out of a trashed google nest display from where I work. I managed to get the device to always load to the DUCO app by uninstalling the mediaplayer throught the DUCO app. However that is as far as I can get as the device will not communicate with ADB at all. Not sure if it's a win10 thing or if it's the device itself.
TheArcticGentoo said:
I DID IT! Working tablet
So the story is yesterday I found an Amiibo display at my apartment dumpster where people put stuff they don't want that still works, I nabbed it with the intention of salvaging the "monitor." Judging by the hammer-marks on the acrylic enclosure, and pry marks on the metal cage that held the power supplies for the led strips and the tablet I assume somebody took it home, got frustrated by the locks and screws after some prying, and just busted in the acrylic window to get to the floor model Amiibos.
I cracked it open, and after some fun with a butane torch to melt the acrylic around the screws open (damn security hex) was surprised to find that the "monitor" had a usb dongle plugged into it. I plugged it into my station and found it was a 2.4/5 GHZ wifi dongle.
All code here is from Windows power shell since I don't like to dual boot my main gaming rig. Usually I just use the Bash on Ubuntu on Windows developer option for stuff like this, but I didn't know if the fact I was using Windows usb drivers to connect to this would cause problems and I wanted one fewer step to troubleshoot if I had issues. Forgive me penguin for I have sinned.
I found the item number on the back of it and after some googling found it was an android device. Score!
I plugged the tablet in and it went into an Amiibo advertisement kiosk mode.
After about 8 hours I now have a limited (but functional!) giant Android tablet.
To any future adventurers I am making a guide to get you up and running quickly.
I followed selaliadobor's instructions:
As well as pressing CSR and Setup to get into the settings screen. This was interesting, but ultimately didn't do much. However using
Code:
./adb shell logcat >> log.txt
and waiting for it to reboot from the csr menu led me to find (with some help from my engineer father) that /system/app/CSR_A003_20160304_BT.apk was the culprit of the restarts.
This was solved with
Code:
./adb shell rm /system/app/CSR_A003_20160304_BT.apk
From there I was stuck. But then I discovered: THE CSR SETTINGS MENU IS NOT THE REAL ANDROID SETTINGS MENU. To get to the real android settings menu use this:
Code:
./adb shell am start -a android.settings.SETTINGS
This allows you to do a factory reset!
However when it reboots the default launcher is stripped of important features like back/home/running apps, keyboard, a launcher etc. I sideloaded the following apps:
Chrome Browser
Microsoft Arrow Launcher (I originally used Nova but it was too much a ram hog to be useful)
Multiling Keyboard (I originally used Swiftkey, but it too was taking up too much ram)
WebTube (stripped down youTube frontend)
Soft Keys (so I had a home and back button, the running apps button still doesn't work :'( )
First post so no links ;(
imgur .com/dGAOmoM
This is what it looks like after boot. I may also have an affinity for Amiibos.
imgur .com/uQ8u7js
Classic.
Quick note: This device doesn't support google play services, so no hulu, official youtube, netflix unfortunately. Try as I might I haven't found a solution.
Click to expand...
Click to collapse
This worked, but I couldn't get ADB to work in Windows, I had to go grab my laptop running Deepin Linux and set up ADB on that, but no USB drivers are needed in Linux, so once I set up ADB, it just worked. So I'm hoping that might be the solution for others who are having trouble, just use Linux, it just works. ADB works on the CSR level, so no need for security key. Got CPU-Z on there for any curious about the hardware specs, my model is a DT101-ASA-800
Hi all,
So here's the situation: I have a Pixel 1 with stock (read: overbloated verizon) android. Whatever, I'm lazy and I haven't gotten around to rooting it. I installed a firewall recently for giggles. I'm going through the system apps and merrily blocking verizon junkware when I come across this thing (bear with me for the complete description, as XDA's spam filters are blocking my image links)
It's a system process called 'nobody' with a version number of 10. The Netguard app also gives a number above the name (i don't know what it's supposed to mean) that for most apps seems sort of random, but for this app is 9999.
I try to find this thing in my system app manager, and it's nowhere to be found.
So I keep on keeping on, thinking 'weird, but whatever', and then I come across another app called 'root' with a version number of 10 and (maybe it's a process id?) of 0.
Also, nowhere to be found.
And here's the thing; there's a gear icon in Netguard, that for _every other app_, opens up the system app manager page for that app. For these two? Nothing.
Now, I am not super proficient in android stuffs. My questions for you smart and pretty people are these:
1. How can I go about digging around in my phone to find the files that are running this thing?
2. What's the best way to get more information on what this is? (and yeah, I tried googling 'nobody' and 'root'. It went predictably).
3. How can I prepare a report / who would I send this to? There's gotta be security researchers who could use logs pertaining to this ****.
Yeah, I know that I need to nuke & pave the device. I will. I want to try and recon a little first. So, what do you got?