Hi !
Have a small question regarding the last version of the supercharger (beast rc2).
No issue, I'm 100% supercharged.
But the amount of RAM available that the script reports isn't good.
I previously had "Update 9 - RC 12 - Test 6" installed and when I reinstalled the script after updating the ROM I was using, it told me I could use the old settings.
I said no and went for a complete reinstall. As the numbers provided were different, I checked and saw that the script detected only 592MB of RAM instead of the 768MB available on my Desire HD.
Question is : is this intended or a bug/incompatibility ? Despite upgraded version of the ROM and this script, the only thing that has changed between the two installations is a new kernel (T7).
Related
Hello,
Since my wipe, I use modaco 1.8 and Teknologist kernel 1.8.
I remarked since that, that BlueRSS is not accessible anymore on the market.
Thought, I can find it with androlib : http://fr.androlib.com/android.application...rilla-jEnm.aspx
A friend give me its apk but it tells me at installation that my phone is not compatible.
I don't understand as this app has always been compatible with my phone, by the past.
Do you have an idea?
Thanks
Hello, sorry for the lame question. I know, simple answer is "just re-flash it", but I would really appreciate another way advised to save the config and time.
I have lot of troubles after installing the subj. (http://forum.xda-developers.com/showthread.php?t=929941).
It's LG P500 running at 2.2 Froyo (stock, rooted, custom recovery):
- after applying the first version, battery management gone, access recovered by re-applying; but since then, scrolling became not so smooth as it was before; not a big problem, so I was waiting for next version;
- now, there is 1.1 version: applied that, but all the sounds individually matched to some contacts are gone, I can choose only standard sounds from /system/media, but not from /sdcard/media; tried to re-apply, get back to first version - no changes; get back to 1.1 - and now cannot choose those sounds in any system menu - for all the contacts, alerts etc etc.; but way more important, the I/O performance severely degraded, appearing as up to 10 second to open an app., which was never observed before; "SD tools" measuring shows degrading both R and W (~5 Mb/sec less now).
Is there standard stock 2.2 kernel available separetely, maybe switching back could solve these problems?
Thanks for any thought.
It's not a patch. It's a whole different zImage (kernel?). You may want to restore your backup. If you don't have one, I uploaded the stock 2.2 kernel. It's in the 2nd page of this subforum. Look for "unflash kernel".
I suggest u flash dev cavermans v3 kernel, I loved the response of it ever since I flashed it.
OK, thanks a lot for replies and links!
Yesterday, I re-installed a kernel, tried different versions... Unfortunately, something dramatically wrong with my phone.
With ringtones, it seems I ran into that problem:
http://forum.xda-developers.com/showthread.php?t=998520
- android does not aware of /whatever/media folder anymore.
With performance, it became a bit better after moving most of apps to SD card, but still unacceptable.
Probably, I have to re-flash the whole stuff
First of all, I would like to say thanks to all the developers for all their hard work to make our mini phones better and better everyday. At present, I am using my x10 mini pro with minicm9-3.0.2 installed and in working condition.
I do notice some problems related to battery drain and other issues concerning usb tethering with windows PC as already discussed in older posts. And I believe that these issues would be resolved in future versions of minicm9.
However, the most dreadful thing for me while using my x10 MP is the inability to install my favourite apps due to shortage of internal memory. I didn't have the same problem when I was running minicm7 as I used link2sd app to link all apps to sdcard.
But now, from the time I've installed the latest ics rom, my most favoured app 'link2sd' seems 'out of order'. I don't think there''s any problem with the app, but, I'm frequently notified about low internal storage even after creating links to sd card. I had over 120 apps installed and linked to sdcard '2nd partition' earlier with minicm7 whereas now I have only managed to install about 20 apps. There's another thing that I've noticed. The apps that's been linked to sd crashes on its own and this problem is resolved as soon as the link is removed.
So, somebody please help me out of this situation.. (APP2SD is not the answer I'm looking for)
app2sd is the first thing you should do. because the difference between link2sd and app2sd is only the dex files. that means, even with all the dex files, you can install up at least 50 apps using original Android app2sd.
I believe the cm9 has not solved this problem yet. I have also read all the post online and in the developers form. no one talked about this bug.
The apps linked by link2sd will be automatically move back to internal memory while starting system (before asking PIN). it says:
Android is upgrading...
Optimizing application x of xx
Im screwed
IF I KNEW ABOUT LINK2SD ISSUE, I WOULDN'T HAVE FLASHED ICS (MINICM9) ON MY W8, IM SCREWED...
Hello,
I noticed after upgrading to ICS the available ROM System decreased from 180 MB to 51 MB (see attachment).
I wonder if there is any way to improve it, knowing that my device doesn't appear to suffer lot from that. But in case there is a solution, I will try.
Thanks
I think it's possible increasing system partition but not now. Because partition table can be changed but requires compatible bootloader which no exist yet. You can delete system apps, ringtones and unused fonts.
Sorry for my english
Edit:
I have VK ICS rom and installed S-Voice (~100MB). I have 54,3MB free on system.
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.