*** Not Working*** Is what I meant to put in the title...
Hi all, I searched the Paranoid Android, CM10, and AOKP threads but could not find anything on this.
I'm running Paranoid Android 2.56 and after flashing my computer can no longer read the phone as an MTP Device. I confirmed that flashing back to a touchwiz based rom allows MTP to work, and my Nexus 7 and my old Galaxy Nexus still function with MTP. I've tried various things (installing, uninstalling, reinstalling drivers), registry edits, etc, and nothing is working. In the Paranoid Android thread, it was mentioned that this is a known issue... but I'm just wondering if anyone has been able to find a way around it. It didn't seem like every single person had this issue, just a few, and unfortunately I am one of them.
Any success stories to share?
Thanks.
Related
I've been working at this for about 2 hours now. All I want is to update my phone to Android 2.
The situation is as follows:
I have an original HTC Hero, build 1.76.405.6 etc. I'm trying to install the ROM update to 2.73.405.5. I have to install it with HTCSync. Since I'm on Windows 7, the original HTCSync that came with the phone has issues with the drivers. I've tried several ways of installing those drivers manually, and eventually resorted to using the new all-purpose HTCSync from the HTC website. The program itself works, but, now, when I'm trying to sync, that action itself does not work. If I try to install the update, the connection turns off. If I try to sync the files, it fails to access the PIM. And I already made Outlook my default program on PC, which, according to sources, should have helped the issue.
Oh, and it seems I can't download apps through the marketplace at this time anymore either. I'm not sure if this is related or not, but better safe than sorry, right?
I can't find anything else on this in the archives, so I'm asking you all for help.
Oh, and my knowledge of these kinds of phones is barely above digibetic, so, please, I beg of you, no solutions that have me crack open the entire software shell, or something like that?
Thanks in forward, Sonto
Hey all, I've tried several ways to delete some of the system apps like Google+, TuneIn,... up to cooking up roms based on stock in rom kitchen and so on... it seems like HTC has changed some things with this model because none of them worked.
If I just go with the stock rom and delete them, they invariably come back, like weed or something lol and if I use a "lite" rom made in rom kitchen, there's usually something else that breaks. Closest I've gotten is everything working, except Google Play giving me a 406 error if I try to download something.
What's even odder to me - remember I'm new to Android - is that freezing them using Titanium Backup or even the stock app manager does work and the OS works, without error. It's like HTC buried some software checks in the OS to make sure all stock apps are there, regardless of them actually running.
I followed these guidelines to know which apps to delete : http://forum.xda-developers.com/showthread.php?t=1532366. It's for the HTC Rezound, but many of the apps on there are on Desire X too.
Anyone have similar experiences ?
Well, i did it the way i explained in the AIO Toolkit Thread: here
i removed only the necessary stuff, everything's working great here, no errors, no bootloops.
Only issue was, that some sense widgets were missing, when they weren't deleted. I guess, there's some linking with all HTC stuff (maybe, don't know) and i deleted something wrong. Flashed everything again, now it's ok. :-|
This has been bothering me lately. When I open my Instagram (using xperia ray latest Gingerbread stock ROM), and go to "Photo Maps", a dialog box appears saying "Photo Maps requires that the Google Maps Android API is installed on your device
I tried uninstalling and reinstalling both Google Maps and Instagram, I restarted my device too. But it doesnt solve the problem.
I tried checking /system/framework/com.google.android.maps.jar , I thought I lost this file but the file is there..
This is a rare problem and I only found 2 search results on Google about this problem, and both were found on XDA forum. One had his problem solved by placing this .jar file there. The other one tried placing the .jar file but no luck.
It's bothering me. Because I think it will affect other application that uses google maps. But I'm not sure. And I don't want to reinstall the whole ROM because I have partitioned my SD card, put many stuff in it, I dont want to start it all over just because of this small problem.
Thank you very much in advanced.
I am having the same problem, but it has caused me to realize that I cannot download most things that have a main function that utilises the gmaps API... I'm running a CM9 fork, though, so I expect that to be the cause. Furthermore, I tried to replace the files and gapps installation through recovery, it yields no changes. I see no new files, which is odd imo... Placing the JAR through a file manager and rebooting doesn't change anything for me either. Would love a followup because I too have seen the threads Fun is talking about but I have also seen at least a dozen on here that have gone unanswered
yes. Someone has to got to have the solution. So bump.
bump... i guess? I havent been able to fix this. Althoug a simple flash will fix this, I'm curious that we can fix this.
Still having this issue myself.
Running CM10.1 on my Galaxy SII (i9100P), although its not just with my current ROM that I'm having the issue. Tried refladhing ROMs and GAPPS but no joy. Countless data/cache wipes have done notjing to fix it. Also tried the.jar solution but did nothing.
Really annoys me that I can't find a solution.
No one any ideas on what this could be?
Hello
I have an Xperia Ray and was running a 4.4.4 ROM based on CyanogenMod till a few weeks ago when I started to realize that many of the newer versions of different apps caused strange troubles. Some of them crashed most file explorers I tried just on loading the icon from the downloaded APK. Some I managed to install nonetheless only to have the same problem with the launcher/drawer itself. Every time it tries to display the icon of the app it dies. Looking for a solution I discovered that CM13 got ported for my phone and was happy to be able to change to Android 6.0.1.
Sadly the troubles did not go away. The apps that showed the above mentioned symptoms on 4.4.4 have similar effects on 6.0.1. Only that now these apps are crashing the whole phone forcing a reboot and that the launcher app does not load at all anymore. Only solution is to uninstall the app manually in recovery mode via adb shell.
After a lot of tinkering, experimenting, talking to other app devs, and rebuilding open source apps I found that the problems appeared with the update to Android Studio 3. It seems that without changing anything code wise for these apps only the update from gradle wrapper 3.5 to 4.1 seems to cause these troubles. On the other hand I can build my own apps with the newest Android Studio with everything up to date without these problems showing up. So I guess it is some library, API, or whatever in combination with the newer gradle versions that causes these troubles.
Well, it seems that there is a bug in the CyanogenMod ROMs, as far as I know by now. It's not a Xperia Ray specific problem as people with other hardware running CyanogenMod have the same problems. For example this thread here. And I got confirmation from an app developer team that they were able to reproduce the problems on a Galaxy S2 running CM13.
It's also not Android version related as updating to 6.0.1 did not help at all.
Have you experienced what I'm talking about and maybe found the solution for that problem? I think there is a bug in the CyanogenMod system somewhere but I'm not skilled enough to find it.
I fear that these problems will render my phone incompatible with more and more upcoming app versions and would really hate to have to switch to a bulky modern phone.
Here are some log files showing the errors. Maybe you can read something useful from them.
Thanks in advance!
EDIT:
Here some additional info that came as answer from a dev team I contacted regarding this issue:
The issue you have reported tends to only occur in devices with the older memory layout used by manufacturers for devices that run Android 2.x onwards, such as the Galaxy S2 - this layout still sticks around even when upgrading to custom ROMs with newer android versions. A unified internal layout for Android devices only started to appear in 2013 and it became the de-facto layout in 2014 or so.
In the old layout, you have both an Internal System Partition (1-2GB) and then an Internal System Memory (the rest of the device's advertised internal memory - its seen as emulated "External memory" - an external SD card then becomes "SD2" in these devices when running a custom ROM). This causes problems for apps that are created and compiled with the unified memory layout in mind, even if the old SDK is the target, because the system will not direct them to an accessible storage area to store user data.
The apps that do not have problems were the ones that have been around since android 2.x; they will instead have their own set of problems for newer devices and versions of Android.
Right now I'm not sure what to think of this...
Push...
push too , if i use a non cyangenmod based rom like paranoid android (6.0 Android MarshMallow Pure AOSP for Google Nexus 7 2012 WIFI), is this prob fixed then ?
i have nexus 7 (2012) wifi only device , i have cyanogenmod 11 (20141112) / android 4.4.4 ( this tablet has no SD card slot so no SD2 assignment )
Not Sony Xperia,..
Only a cheap Haier A16C3H with CM13 Nightly...but..
Yes the trouble is exactly the same in my experience here. I don't know what to do for the solution, except perhaps one of:
# "keep/looking for & install - only the old version of apps, or
# buying a new phone (if I can)
Sad
Nothing new
Push
Nothing new from my side, except that I think twice before updating an APP by now.
So far I've managed to get around with my old Xperia, but would be nice if someone more knowledgable could look into this matter.
Thanks.
Anyone figured out how to fix this? or even a workaround?
My problem was the cm13 based rom I am using on my LG G3 Beat had this problem with newer versions of apps, but someone made a cm14 based rom that fixes this problem but in exchange it created another problem, lag in the touchscreen, playing games where you have to do combo/multiple taps became impossible.
I got so frustrated that I just went back to stock lol.
I'm trying to upgrade my Samsung p7510 10.1 tablet from Ice Cream Sandwich 4.0.4 to either Marshmallow or Nougat, or better. I've installed TWRP 3.1.1 and rooted with SuperSu. I've had to assume root has worked as can't download root checker onto my tablet.
So, far I've managed to find a version of Marshmallow "ROM-STOCK_MMB29K-seed.zip" on androidfilehost.com. But when I try installing I keep getting error message "Updater process ended with signal: 4". I've wiped the Data, cleared the Cache and Dalvik Cache. Also searched the internet for info on the signal 4 problem but not found much other than to remove the "assert" line from the updater-script file in the OS zip.; that did nothing.
So, a few questions:
- Anyone know where I can get OS zips from for a Samsung P7510?
- And any ideas on resolving the signal 4 issue?
- Any other ideas?
P.S. The only reason I'm updating is I want to use it for Kindle but can only reach HTTP sites, not HTTPS. Assumed that is because it's so old that everything is out of date. And that stops me from downloading anything from just about anywhere, including Google Play.
P.P.S I have searched the forums but couldn't find anything helpful or with links that worked.
Thanks in anticipation
Might I suggest the stabelest ROM I've ever run on my P7510. I've had this installed on mine for over a year now. There are of course some minor bugs.
The signal 4 issue is most likely a Binary issue and should no longer be relevant since you should reset the device to factory and start over. Another thing is once you Root it you can't download from Google play because you now have an unverified device, it has something to do with Google Pay. You'll want to look for APKs. Although SuperSu is usable, you're going to want Majisk insted. I hear of some problems using SuperSu.
I have these files here in my PC if any of the links no longer work but you'll want to know how to flash it so you'll need the video. I'll check back soon and drop a link to my files. if you need them. I'd need to upload them to my Google Drive first.
If you have any other difficulties I'm usually here about once every week.
P.S. Your tab is better than a Kindle and I would not suggest using it as such, it runs pretty crappy that way . Amazon does have an app you can use. And I see that you have been having difficulties finding Operating Systems for your tab and yes it's because the P7510 first hit the market in March of 2011 there aren't many people doing much with it anymore. There's about 3 or 4 of us left.
Firstly, thanks for your help @Casper Young .
In particular the video was brilliant. I did have a few runs at the update, however, the process was very straightforward. The key issue was the TWRP version I was using. It was supposed to be for the P7510, but realised it was actually for the P7500, consequently the aosp files weren't loading. I think that was also the cause of the errors I was getting. And although none of the links were working I managed to get the file names from the video and sourced them from androidfilehost.com:
twrp2870-20150814-p4wifi.tar.md5
aosp-7.1-p4wifi-20170506.zip
Once I had those it was simple and the update worked smoothly.
I've also added the app from apkpure.com as Google play was a complete pain trying to get the tablet recognised. Now very pleased with the build and apps, all running very smooth.
thanks again
Glad you had no problems. There are some minor bugs. Flash doesn't work for the camera. And check your memory capacity. I use Apex Launcher for my home screen which organizes better for me.