I'm on 5/10. I guess the only thing I should mention is I have been using CM Delta - I'll try a full flash and let you know..
-EDIT- No dice I did a full 5/10 flash and it is still the same. If I don't click to focus before I take the shot gallery freezes and can't connect to camera. I did a data wipe on Gallery using TiBu, didn't help.
Last edited:
I personally haven't been able to reproduce. Can you create a logcat of the crash happening?
Once again with a cleaner state this time.
With the latest nightly 5/10, system and data wiped, no gapps, encryption still in place I'm getting general lagginess everywhere: scrolling in the browser isn't immediate and effortless, the Settings app is choppy, it was painful to see it lag while enabling adb, the Gallery choppy too etc.
Attached are logcats from 5/10 and 4/22 which is unaffected.
Is there a sane way to review change logs between the 4/22 build and the following ones?
[UPD] To be precise, the latest usable build for me is 4/23.
5/10 has a lot of these, it was reported in some other thread as related to encryption:
E/qdhwcomposer( 1147): Failed to call ioctl MSMFB_OVERLAY_SET err=Out of memory
With the latest nightly 5/10, system and data wiped, no gapps, encryption still in place I'm getting general lagginess everywhere: scrolling in the browser isn't immediate and effortless, the Settings app is choppy, it was painful to see it lag while enabling adb, the Gallery choppy too etc.
Attached are logcats from 5/10 and 4/22 which is unaffected.
Is there a sane way to review change logs between the 4/22 build and the following ones?
[UPD] To be precise, the latest usable build for me is 4/23.
5/10 has a lot of these, it was reported in some other thread as related to encryption:
E/qdhwcomposer( 1147): Failed to call ioctl MSMFB_OVERLAY_SET err=Out of memory
Last edited:
this problem still exists in RC2. i also use encryption, though i don't think that's the cause.
Did RC2 format my internal SDCard?
VZW SGS3 + cm-10.1.0-RC2-d2vzw
Did RC2 format my internal SDCard?
I can't find anything. No pics, downloads (including RC2 I just installed), or Titanium Backup files.
There's no /0 folder where I've found things moved before.
VZW SGS3 + cm-10.1.0-RC2-d2vzw
Did RC2 format my internal SDCard?
I can't find anything. No pics, downloads (including RC2 I just installed), or Titanium Backup files.
There's no /0 folder where I've found things moved before.
HypostaticOnion
Senior Member
Check /data/media
Sent from my SCH-i535 with Tapatalk 2
If I've helped, please hit the thanks button
Anyone know if there's an easy way to enable soft keys in CM10.1? My home button just stopped working (I've abused my phone a bit 
). Last I checked I needed to flash a modded system UI or something to get soft keys, is that still the case?
). Last I checked I needed to flash a modded system UI or something to get soft keys, is that still the case?
Anyone know if there's an easy way to enable soft keys in CM10.1? My home button just stopped working (I've abused my phone a bit
Is this what you are talking about? The PIE control?
http://xdaforums.com/showpost.php?p=40758091&postcount=1467
It says it should of been merged as of 4/26...not that I've extensively tried it, but I can't figure it out as of now. If I'm reading it right, it appears as you have to flash that zip if's not merged like he said it "should" be.
Last edited:
Oh no, I meant onscreen keys like the Nexus devices have but PIE is a good stopgap, thanks! Actually I already had it enabled using LMT launcher but I rarely use it so I forgot about it.
Anyone know if there's an easy way to enable soft keys in CM10.1? My home button just stopped working (I've abused my phone a bit
I managed to get software buttons on my S3 running CM 10.1 without any issues. Check out this thread:
http://xdaforums.com/showthread.php?t=1918166
It's pretty simple, all you do is flash the zip in recovery. There's an installer that lets you choose exactly the way you want it. If you choose the option to leave the hardware buttons working you can shut off the software buttons at any time by enabling expanded desktop in the system settings.
Anyone know if there's an easy way to enable soft keys in CM10.1? My home button just stopped working (I've abused my phone a bit
Once you mod the build.prop then the pie in cm10.1 shows up after reboot.
Just by adding: qemu.hw.mainkeys=0 at the end of the build.prop? Then just reboot?
Like the link I posted? http://xdaforums.com/showpost.php?p=40758091&postcount=1467
Like the link I posted? http://xdaforums.com/showpost.php?p=40758091&postcount=1467
That's it. If you don't want it anymore restore old build prop or just change 0 to 1 and reboot. You can also kill the stock menu and back button if you want
HypostaticOnion
Senior Member
I'm talking data in the root not the sdcard
Sent from my SCH-i535 with Tapatalk 2
If I've helped, please hit the thanks button
Anyone know if there's an easy way to enable soft keys in CM10.1? My home button just stopped working (I've abused my phone a bit
Softkey enabler in the play store, doesn't get easier than that.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
Your data goes into a /0 folder in the sdcard. When you go back to TW, your data will go back to the /sdcard partition. You only have to do a factory reset, don't delete everything on the sdcard as all of that data will still be accessible in /sdcard/0. You can pull anything you want out of that folder once your back on TW. Factory resetting and fixing permissions are definitely required though.
[Workaround] Failed to call ioctl MSMFB_OVERLAY_SET err=Out of memory
During boot a minimal environment which allows to enter the encryption password aquires a kernel resource and doesn't release it before resuming. When the real system comes up it tries to aquire the resource over and over in vain and we see
A workaround that mitigates the issue for me: don't let the affected resource be acquired for 60 seconds, so the minimal system won't grab it.
This is triggered by encryption but has nothing to do with it.
During boot a minimal environment which allows to enter the encryption password aquires a kernel resource and doesn't release it before resuming. When the real system comes up it tries to aquire the resource over and over in vain and we see
in logcat and
in kmsg.
A workaround that mitigates the issue for me: don't let the affected resource be acquired for 60 seconds, so the minimal system won't grab it.
Code:
diff --git a/drivers/video/msm/mdp4_overlay.c b/drivers/video/msm/mdp4_overlay.c
index 8e84146..83d0717 100644
--- a/drivers/video/msm/mdp4_overlay.c
+++ b/drivers/video/msm/mdp4_overlay.c
@@ -2394,12 +2394,19 @@ struct mdp4_overlay_pipe *mdp4_overlay_pipe_alloc(int ptype, int mixer)
{
int i;
struct mdp4_overlay_pipe *pipe;
+ unsigned long long cl;
if (ptype == OVERLAY_TYPE_BF) {
if (!mdp4_overlay_borderfill_supported())
return NULL;
}
+ cl = cpu_clock(0);
+ do_div(cl, 1000000000);
+
+ if (cl < 60 && ptype == 2)
+ return NULL;
+
for (i = 0; i < OVERLAY_PIPE_MAX; i++) {
pipe = &ctrl->plist[i];
if ((pipe->pipe_used == 0) && ((pipe->pipe_type == ptype) ||Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13Post development questions/logcats etc in the development thread. Post "my data doesn't work" here (after reading the OP). The mods don't like the developers thread being filled with these questions, and it's contrary to the goal of that board. I'll keep both OPs updated.
Development thread: http://xdaforums.com/showthread.php?t=2053799
10.1.3 has been released.
As for all recent releases, please make sure you are on the MF1 modem
Cyanogen Mod 10.1.0 Release is now available:
http://get.cm/?device=d2vzw
Huge thanks to the CM devs! Pop on over to http://www.cyanogenmod.org/ and make a donation (mouse over "Community" at the top right then select "Donate to us") if you'd like to help support the CM project!
Anyone looking for mastamoon's build with his tweaks, reverts, and cherrypicks - it was moved to Android Development. Here is the link! http://xdaforums.com/showthread.php?t=2094251
Rooting, flashing, installing roms, following any instructions below, will void your phone's warranty and there is a chance (however small) that you'll screw up and permanently break your phone. Anything you do to your phone in violation of the warranty, insurance, or anything else is at your own risk!
-+-+-+-+-+-+-+-+ OFFICIAL DOWNLOAD LINK -+-+-+-+-+-+-+-+
http://get.cm/?device=d2vzw
-+-+-+-+-+-+-+-+ NIGHTLY CHANGE LOG -+-+-+-+-+-+-+-+
App from invisiblek: https://play.google.com/store/apps/details?id=com.invisiblek.cm.nightlies
Or: http://10.1.cmxlog.com/?device=d2vzw
-+-+-+-+-+-+-+-+ GUIDE ON HOW TO ROOT AND FLASH -+-+-+-+-+-+-+-+
http://xdaforums.com/showthread.php?t=2046439
-+-+-+-+-+-+-+-+ HOW TO BACKUP AND RESTORE YOUR IMEI -+-+-+-+-+-+-+-+
http://xdaforums.com/showthread.php?t=1852255&highlight=nvbackup
-+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ -+-+-+-+-+-+-+-+
https://plus.google.com/+CyanogenMod/posts
-+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ COMMUNITY -+-+-+-+-+-+-+-+
https://plus.google.com/communities/107373456059326217974
-+-+-+-+-+-+-+-+ KNOWN / REPORTED ISSUES -+-+-+-+-+-+-+-+
On the 10.1.3 RC: (updated 7/18)
1: Only use the MF1 AIO file available here.
2: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.
3: Verizon FIOS app crashes
4: BT headsets don't work with the Skype app
5: One channel audio on headphones.
6: Low recording volume using the camcorder.
7: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.
On the latest nightlies: (updated 7/18)
1: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.
2: Verizon FIOS app crashes
3: BT headsets don't work with the Skype app
4: Low recording volume using the camcorder.
5: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.
Many other problems are fixed by simply re-flashing the same rom file over itself.
Please PM repeatable issues from the release to me. Post a logcat in the developer thread or a JIRA ticket if you expect it to get fixed.
-+-+-+-+-+-+-+-+ SPECIAL NOTES -+-+-+-+-+-+-+-+
1. To enable Developer Options: Menu > Settings > About Phone. Tap build number 7 times to unlock Developer Options
2. Photosphere: This feature is not offered on non-nexus devices
3. There are a lot of questions about how CM10.1 moves your files to sdcard/0/ folder. This is to support multi-users. If you flash back and forth between a non-4.2 ROM and CM10.1 (which is 4.2) you'll end up with sdcard/0/0/..etc since the upgrade to 10.1 moves your folders into a new /0/. You can safely move your files out of /0/ back to your sdcard if you're on CM10, or back to the first /0 folder if you're on CM10.1.
4. Don't update from CM10 to CM10.1 using the built-in cmupdater. Update in recovery for the first flash from CM10 to 10.1. Once on 10.1 you can use cmupdater.
-+-+-+-+-+-+-+-+ INSTALLATION NOTES -+-+-+-+-+-+-+-+
- CM can be flashed using CWM or TWRP. Only use the latest TWRP or CWM!
- When you install CM10.1 your data will be moved to a new folder /0/ (this is to support multi-users).
- Make sure you have the latest CWM or TWRP installed so that your recovery isn't confused by the new location of your backups. Official TWRP d2vzw or Latest CWM (scroll down to Samsung Galaxy S3 (Verizon))
- GAPPS is not included in any CM download. You must flash a gapps zip if coming from another rom or when starting with a clean install. You do not need to flash gapps when 'dirty flashing' over a previous CM install. Download gapps here.
- According to Cyanogen it is possible to flash CM10.1 over top of an existing CM10 installation. It is generally recommended to do a clean install if you run into any issues.
- Always make a backup before you try a dirty flash or upgrade to CM10.1.
-+-+-+-+-+-+-+-+ HOW TO INSTALL OVER CM10 -+-+-+-+-+-+-+-+
- Consider backing up your IMEI if you haven't already (link)
- If you use a lockscreen pattern disable it
- Flash the latest CWM or Official TWRP d2vzw
- Download a CM10.1 rom (nightly or unofficial) to your sd card
- Download the latest gapps from goo to your sd card
- Reboot into recovery
- Make a backup
- Wipe cache and dalvik (if you want)
- Install CM10.1 zip
- Install gapps
- Reboot
- After your phone boots go into Menu > Settings > Apps. Under "All" find "Clock", open it, and click "Clear Data"
-+-+-+-+-+-+-+-+ HOW TO INSTALL FROM ANY ROM OTHER THAN CM -+-+-+-+-+-+-+-+
- Consider backing up your IMEI if you haven't already (link)
- Flash the latest CWM or Official TWRP d2vzw
- Download a CM10.1 rom (nightly or unofficial) to your sd card
- Download the latest gapps from goo to your sd card
- Use an app like Titanium Backup or Mybackup Pro to backup your apps (if you want)
- Use an app like SMS Backup+ to backup your text messages and call log (if you want)
- Reboot into recovery
- Make a backup
- Wipe cache and dalvik (if you want)
- Wipe Data/Factory Reset/System
- Install CM10.1 zip
- Install gapps
- Reboot
- Reinstall Titanium Backup/Mybackup Pro/SMS Backup+ and restore the stuff you have to have, but its better to reinstall things from the market if possible (keep in mind your backups will be located in sdcard/0/) (if you want)
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I am not a developer, I have no direct association with the CM project, I am just a community member. I will do my best to maintain this thread. Please PM me with any OP suggestions!10
I'm starting a petition for you to write your own animation. If I get 2 more signatures, you have to do it. +1's and Thanks to this post count as signatures. Contract is binding and non-negotiable. You are as obligated to perform your end as the CM10.1 devs are to listen to your petition. Petition open.5
Actually, I'm not sure if this is fixed in 3.4 or not. I usually reboot too often to see this (for me it would take like a day for the problem to surface)
It's most definitely on the radar, just not high priority. I'll try to keep it running for an extended period of time and see if this problem comes up. (But the weekend might be a bad time to make a promise like this =P)
The problem with 90% of these "one-off" issues that people have is that there are too many variables. My suggestion, if you are running into an unreported or obscure problem, is to wipe data/factory reset, reflash your rom and official gapps only. No custom stuff (inverted gapps, custom kernels, etc) and boot up, don't install any apps, and see if the problem is still there. When you start replacing system files with "unofficial" ones (gapps, kernel/modules) many different things can happen that are tough to account for. This goes for installing root apps too, or apps designed to "monitor" your device for certain things. Who knows WTF a root app is doing mucking around on your device, and these battery monitor, tasker, etc apps can cause wakelocks and other unintentional problems. Especially since you don't know how an app for say, ICS, would play with JB 4.2.2, and who knows if the app dev has updated to account for any changes to JB. I don't mean to bash anyone's app or kernel, I'm sure most of them run perfectly fine, but getting to the root cause of a problem has to start with eliminating all external variables.
Ok, enough of my long-winded rants.
Regardless of what you have running/flashed/etc, make sure you are posting relevant logcats and dmesgs, especially on these odd problems that nobody else seems to have. If you don't, your post isn't much help to anyone. (Hint: use pastebin!)5http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20121229-UNOFFICIAL-d2vzw.zip
Has LockClock included:
https://plus.google.com/105849811393167071979/posts/KBHPeMRXpGo
Also the gps squash from caf:
http://review.cyanogenmod.org/#/c/29349/
Sync'd about 15-20 minutes ago4For those of you having trouble with the Lock Screen Clock, here is what works to get it up and running. First you go into system settings (settings), then under the "interface" section you will hit "system". There you will find the settings for "Lock clock widget". After you have set up all the preferences, get your phone back to the lock screen (I found that going to your home screen and then hitting the power button is the easiest way). Now that you are sitting at a black screen, hit the power button, or home button, to wake the screen. Immediately upon doing that, you will see the two big gridlines appear on each side of the screen, the subtle prompt to show you there are screens to each side you can swipe. Swipe the screen from left to right. You will see a big "+" in the middle of the screen. Now, while at that screen with the "+", swipe back from right to left and it will take you back to the main lock screen. As soon as you hit the main lock screen, long press the screen and drag it up into the garbage can. If you correctly deleted the home lock screen, it will now automatically advance you back to the big "+" screen. Hit the big "+". You will now see you have a few options. The third one down will be "Lock Clock". Hit that and you will now have it as your lock screen. I will however say that it is a little bit buggy right now, especially if you are trying to get appointments to show, but it does work!
I am on the latest OFFICIAL 10.1-20121231-NIGHTLY, flashed dirty from yesterdays nightly. I will be doing a full wipe and clean install later today to see if the anomalies with the new lock screen widget persist or go away. What I am seeing is that when you add the lock screen widget, it will show your calendar event, but after the screen goes to sleep, the appointments are no longer on the widget when you wake the screen back up. The weather is there, and the battery state is there right below the weather, but no appointments. If I swipe that screen showing weather and battery state back and forth from the "+" screen, the appointments show back up, but the battery state is missing. Also, turning the battery status off on the lock screen doesn't change it from not showing the appointments. I think that should be enough info to point someone to a fix.
I hope that helps!
Scott
New posts
-
Development [ROM][14][STABLE][UNOFFICIAL] Lineage OS 21 for Xiaomi 13 Fuxi- Latest: nguyenhung9x2018
-
