Yeah, I am doing the same thing for now. Another friend of mine just did his and isn't getting the flickering or the recent apps problem so I wanted to see if anyone else had this issue.
Sent from my Transformer using Tapatalk 2
Yeah, I am doing the same thing for now. Another friend of mine just did his and isn't getting the flickering or the recent apps problem so I wanted to see if anyone else had this issue.
Sent from my Transformer using Tapatalk 2
Not having that issue and am on today's build. Check USB settings under storage menu and confirm debugging.
Sent from my SCH-I535 using Tapatalk 2
I highly recommend that anybody thats having problems with the recent apps Window do a factory reset in recovery.
Doing this fixed my recent apps Window issue, and fixed a few graphical things that obviously didn't get cleared with the usual wipes.
Blasted from my Samsung Galaxy SIII (CM10).
---------- Post added at 11:58 PM ---------- Previous post was at 11:45 PM ----------
And never mind, recent apps issue is back.
Blasted from my Samsung Galaxy SIII (CM10.1).
Doing this fixed my recent apps Window issue, and fixed a few graphical things that obviously didn't get cleared with the usual wipes.
Blasted from my Samsung Galaxy SIII (CM10).
---------- Post added at 11:58 PM ---------- Previous post was at 11:45 PM ----------
And never mind, recent apps issue is back.
Blasted from my Samsung Galaxy SIII (CM10.1).
No dice. My USB settings are set to MTP and debugging is on. There is no connection detected by the phone or the computer (other than charging, that is). I've tried two different cables as well.
And you cold rebooted naturally? Just because I had that issue and a power down, restart fixed it.
---------- Post added at 06:45 AM ---------- Previous post was at 06:44 AM ----------
Which begs the question, what changed from 12-27 (last known working build without the work around) to a later build and what value did it give us in return?
its supposed to be broken right now, its being worked on
battery drain
I have been having horrible battery drain on the 27th nightly. Yesterday media server ate like half my battery, so I got rid of music off my sd card. Today I have barely used my phone and it is at 40% with only 30 minutes of screen time. Any ideas? I did a clean install, I completely wiped my internal sd card before install and cleared user data and cache. And last night I let my phone die completely before charging.
Edit: added better battery screen shot.
I have been having horrible battery drain on the 27th nightly. Yesterday media server ate like half my battery, so I got rid of music off my sd card. Today I have barely used my phone and it is at 40% with only 30 minutes of screen time. Any ideas? I did a clean install, I completely wiped my internal sd card before install and cleared user data and cache. And last night I let my phone die completely before charging.
Edit: added better battery screen shot.
Attachments
Last edited:
Well, I tried that last night with no results. But now it's suddenly decided to work again. Problem solved, I guess...
Looks like the audio lockup is still present in 12/30 flashed back to 12/27 (last working build)
The time is like that every time I reboot. I get the error message from whatsapp too. It's cause the phone takes longer to get signal and doesn't have the time from the network before whatsapp stays up.
The messed up time in recovery is a known issue for quite some time I believe
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 11:37 AM ---------- Previous post was at 11:36 AM ----------
You just need to edit the build.prop line that says lpa.decode to false and then reboot. Audio should work fine after
Sent from my SCH-I535 using Tapatalk 2
this question just begs flames, but i'll be, polite. can't fix what you don't list, and no one here is a mind reader, so we don't know what "problems" you're having so we can help.
go to system, more, mobile network settings, and cdma subscriptions, and make sure you change it from nv to ruim/sim. should fix your roaming problems.
which has been addressed here a number of times, may even be in the OP
I have been having this problem since the first 10.1 nightly and have yet to come up with a solution for it, this has become increasingly annoying as i have been having to build APK files and then use dropbox to send them to my phone rather than using ADB or push through eclipse for development.
I had this issue and fixed it by:
1. Reboot into download mode. Plug phone into PC. Driver should install.
2. Unplug phone then pull battery to get out of download mode.
3. Boot phone then plug phone into pc. Pc should now see the phone.
Hope this works for you.
Sent from my SCH-I535 using Tapatalk 2
1. Reboot into download mode. Plug phone into PC. Driver should install.
2. Unplug phone then pull battery to get out of download mode.
3. Boot phone then plug phone into pc. Pc should now see the phone.
Hope this works for you.
Sent from my SCH-I535 using Tapatalk 2
For those of you who have the phone.apk force closing, and don't have call audio coming out of the headphones, here's what I posted yesterday on the developer's thread:
It would be nice if someone else could confirm this fix.
Sent from my SCH-I535 using Tapatalk 2
It would be nice if someone else could confirm this fix.
Sent from my SCH-I535 using Tapatalk 2
Last edited:
Anyone else having problems seeing icon labels on your home screen after expanding the grid size from the stock 5x5? I am on Trebuchet.
any input would be greatly thanked!
any input would be greatly thanked!
My computer will see my phone, but can't find at files. Would this work, or is there another fix? Phone shows USB debugging and mtp, just no fls when I plug in
Sent from my SCH-I535 using xda app-developers app
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
