FORUMS
Remove All Ads from XDA

CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report

3,143 posts
Thanks Meter: 3,276
 
By arsradu, Senior Member on 11th March 2013, 01:05 AM
Post Reply Email Thread



Opening this thread in order for the users to post their issues here instead of the development section or CM10 bug report thread.

This thread refers to discussions/bug reports for CM10.1 (Android 4.2.2) released by arco68 here.
As usual, it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.

On behalf of the SGW users, big thanks to arco68 and the CyanogenMod Team!

Great job, guys!

Note: bugs concerning custom kernels are to be reported into the corresponding threads! Please, don't post them here.


In order to avoid posting bugs that are not actually bugs, please, make sure you follow this little tutorial before upgrading/installing CM10.1:


For installation, first, make sure you got CM10.1 ROM and the correct Gapps on your External SD Card. Both can be found in the Mirrors section below.

After that, enter CWM and:
  • select "wipe data / factory reset"
  • go to "mounts & storage" and format /system. This is extremely important!
  • under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
  • install CM10.1 (from the external sd)
  • install Gapps for JB+ (from the external sd)
  • reboot your phone

    * On newer CWM Recovery versions, you might find the internal memory mounted as /sdcard0 and the external one as /sdcard1. For this case, make sure you don't format /sdcard1 by mistake.
Please, note that every step of this tutorial is mandatory!


For apps backup & restore using Go Backup Pro, please, follow the tutorial below, step by step:

For Backup

1. Make sure you have an external SD card inserted
2. Download Go Backup Pro (of course)
3. Enter the app and go to Settings (from the 3 vertical dots on the right side of the screen)
4. Make sure that for the Backup Path, you have selected External storage (if I'm not mistaken, this is the default setting anyway, but it's good to confirm, just in case)
5. Go back and go to New/Restore Backup section
6. Click Batch Backup (bottom left of the screen)
7. Select what you want to backup*
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts.
8. Click Start Backup
9. Wait for it to finish and click Finish

For Restore

1. Assuming that by now you already have a backup to restore, go to New/Restore Backup section again
2. Click Batch Restore
3. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
4. Click on "APK + Data" from Restore Content and select "Restore app only". Now the Restore Content section will show only APK.
5. Uncheck the apps for which you need app data. Those apps won't be restored, for now. Please, go on with the tutorial.
5. Click Start Restore
6. Wait for it to finish and click Finish

7. Now that we chose what apps we want to be restored without app data, let's go back and enter New/Restore Backup section (yeah, again :P).
8. Click Batch Restore
9. Uncheck everything*.
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts
10. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
11. Click on "APK" from Restore Content and select "Restore app and data". Now the Restore Content section will show APK+ Data.
10. Check only the apps for which you DO need app data to be restored (the ones that were left unrestored from last time :P).
11. Click Start Restore
12. Wait for it to finish and click Finish.

How to post a bug report:

Copy-paste the lines below in your post, filling up the required information:

HTML Code:
[B]Version:[/B] CM10.1 - Beta 4
[B]App/Game/Subject:[/B] WRITE HERE SUBJECT
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Probability of occurrence:[/B] WRITE HERE "LOW/MEDIUM/HIGH" (depending on how often the bug occurs)
[B]Description:[/B] WRITE HERE DESCRIPTION


Mirrors:

CM10.1 Beta 4 (Google Drive): here
CM10.1 Beta 4 (MEGA): here
CM10.1 Beta 4 (Devhost): here
md5sum: c7e9114d760c0e924919b1be95425048

Gapps 20140507 JB+ (Google Drive): here
md5sum: b0d6e6b62cb9149aea5de2531026f33a

Changelog Gapps:

Changelog Gapps 20140507:
* Google Search v3.4.16.1149292.arm
* Google Maps v8.0.0
* Hangouts v2.1.100(1151589-30)
* Google Play Services v4.3.25(1117461-034)
* Google Play Store v4.6.17
* Google Text-to-Speech Engine v3.0.11.1070024

Changelog Gapps 20140209:
* Google Maps v7.6.0
* Hangouts v2.0.303 (1004807-30)
* Google Play Services v4.1.32 (978161-34)
* Google Search v3.2.17.1009776.arm

Changelog Gapps 20131214:
* Google Maps v7.5.0
* Gmail v4.7.1 (946962)
* Google Play Services v4.0.34 (924341-34)
* Google Play Store v4.5.10
* Google Search v3.1.24.941712.arm
* Hangouts v2.0.217 (944332-30)
* Talkback Service v3.5.1
* Google Text-to-speech v2.4.3.864779

Changelog Gapps 20131001:
* Gmail v4.6 (836823)
* Google Search v2.8.8.849369.arm
* Google Hangouts v1.2.018 (849105-30)

Changelog Gapps 20130917:
* Google Maps v7.2.0

Changelog Gapps 20130825:
* Google Search v2.7.9.789824.arm
* Google Hangouts v1.1.2.778356

Changelog Gapps 20130817:
- Google+ (can be redownloaded from Google Play Store, if needed)
* Google Play Store v4.3.11
* Google Maps v7.1.0

Changelog Gapps 20130814:
+ Google Hangouts v1.1.1.753199**
+ Google Maps v7.0.2**
* Hangouts libs
* Google Play Services v3.2.25 (761454-34)
* Google Play Store v4.3.10
+ Google+ v4.0.2.48854689

**Re-added to the new base package from goo.im

Changelog Gapps 20130726:
* Google Hangouts v1.1.1.753199

Changelog Gapps 20130718:
* Google Play Services v3.1.59 (736673-34)
* Google Maps v7.0.2

Changelog Gapps 20130715:
* Google Talkback Service v3.4.0

Changelog Gapps 20130712:
* Google Maps v7.0.1

Changelog Gapps 20130630:
* fixed Hangouts video calling FC

Changelog Gapps 20130628:
* Google Search v2.6.7.721924.arm
* Gmail v4.5.2-714156

Changelog Gapps 20130624:
+ Google Street View (Google Maps addon) v1.8.1.2
+ minor changes

Changelog Gapps 20130612:
+ Gmail v4.5-694836 (the new, beautiful Gmail app)
+ Google Maps v6.14.4
* Google Play Services v3.1.36 (669520-34)
* Google Play Store v4.1.6 (the new Google Play Store)
* Google Search v2.5.8.675703 (the new Google Search with Google Now)
* Google Hangouts (ex Google Talk) v1.0.2.695251
* Google Talkback Service v3.3.2

+ means that the app was newly added
* means that the app was upgraded by replacing it with the newer version
- means that the app was removed



To enable Developer Options: go to Settings -> About Phone and tap the Build Number 7 times to enable Developer Options.

To enable Advanced Reboot options: go to Settings -> Developer Options and check the Advanced Reboot box.
Please, see the screens below for more information.

To swap memories (internal with external SD Cards) in Alpha 3 and above without modifying the vold.fstab file, go to /System/build.prop using any File Explorer with root privileges (recommended X-Plore) and change from 0 to 1 in the code below*:

Before
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=0
After
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
*Thanks to Madridii for this.


Videos

[YOUTUBE]R8I-BVIIgis[/YOUTUBE] [YOUTUBE]xN-R0S437YU[/YOUTUBE]


Bugs reported/still occurring so far (Beta 3):
1. Camera/Gallery (To be confirmed in Beta 4)
  • Camera/Gallery app becomes unresponsive when locking&unlocking the screen multiple times (about 4 times in my tests). After that, if the user chooses to force close the Gallery app, when entering the Camera app again, he will be prompted with the following error message: "Can't connect to the camera".
    Please, see the attached screenshot and the log below for more info.
    Code:
    [ 08-05 15:13:30.010   441:  456 W/ActivityManager ]
    Activity idle timeout for ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
    
    [ 08-05 15:13:31.521   441:  503 I/InputDispatcher ]
    Application is not responding: AppWindowToken{414fc260 token=Token{41691380 ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}}} - Window{4122f110 u0 com.android.gallery3d/com.android.camera.CameraLauncher}.  It has been 5003.1ms since event, 5001.2ms since wait started.  Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
    
    [ 08-05 15:13:31.531   441:  503 I/WindowManager ]
    Input event dispatching timed out sending to com.android.gallery3d/com.android.camera.CameraLauncher
    
    [ 08-05 15:13:31.621   441:  503 I/Process  ]
    Sending signal. PID: 5350 SIG: 3
    
    [ 08-05 15:13:31.621  5350: 5355 I/dalvikvm ]
    threadid=3: reacting to signal 3
    
    [ 08-05 15:13:31.701  5350: 5355 I/dalvikvm ]
    Wrote stack traces to '/data/anr/traces.txt'
    
    [ 08-05 15:13:31.701   441:  503 I/Process  ]
    Sending signal. PID: 441 SIG: 3
    
    [ 08-05 15:13:31.701   441:  444 I/dalvikvm ]
    threadid=3: reacting to signal 3
    
    [ 08-05 15:13:31.882   143: 5647 E/CAM_FD   ]
    cam_conf: In config thread
    
    [ 08-05 15:13:31.992   441:  503 I/Process  ]
    Sending signal. PID: 553 SIG: 3
    
    [ 08-05 15:13:31.992   553:  560 I/dalvikvm ]
    threadid=3: reacting to signal 3
    
    [ 08-05 15:13:32.002   441:  444 I/dalvikvm ]
    Wrote stack traces to '/data/anr/traces.txt'
    
    [ 08-05 15:13:32.002   441:  503 I/Process  ]
    Sending signal. PID: 656 SIG: 3
    
    [ 08-05 15:13:32.002   656:  670 I/dalvikvm ]
    threadid=3: reacting to signal 3
    
    [ 08-05 15:13:32.042   553:  560 I/dalvikvm ]
    Wrote stack traces to '/data/anr/traces.txt'
    
    [ 08-05 15:13:32.092   656:  670 I/dalvikvm ]
    Wrote stack traces to '/data/anr/traces.txt'
    
    [ 08-05 15:13:32.212   441:  443 D/dalvikvm ]
    GC_CONCURRENT freed 1916K, 21% free 10090K/12716K, paused 4ms+7ms, total 97ms
    
    [ 08-05 15:13:32.212   441:  503 D/dalvikvm ]
    WAIT_FOR_CONCURRENT_GC blocked 65ms
    
    [ 08-05 15:13:32.422   441:  503 D/dalvikvm ]
    GC_EXPLICIT freed 777K, 21% free 10132K/12716K, paused 4ms+5ms, total 91ms
    
    [ 08-05 15:13:32.632   441: 1243 E/Sensors  ]
    type : 0, deley : 66667000 
    
    [ 08-05 15:13:32.632   441: 1242 E/Sensors  ]
    type : 0, deley : 20000000 
    
    [ 08-05 15:13:33.003   441:  503 I/Process  ]
    Sending signal. PID: 1051 SIG: 3
    
    [ 08-05 15:13:33.003  1051: 1056 I/dalvikvm ]
    threadid=3: reacting to signal 3
    
    [ 08-05 15:13:33.103  1051: 1056 I/dalvikvm ]
    Wrote stack traces to '/data/anr/traces.txt'
    
    [ 08-05 15:13:33.113   441:  503 E/ActivityManager ]
    ANR in com.android.gallery3d (com.android.gallery3d/com.android.camera.CameraLauncher)
    Reason: keyDispatchingTimedOut
  • After rendering the Panorama shots, when the camera returns to the Panorama Mode for the user to take another panoramic shot, the camera preview is flickering. This happens only if the Auto-Rotate function is ON and the screen in Portrait mode. With the Auto-Rotate OFF, this bug does not occur.
    Please, see the attached screenshot for, hopefully, more info on this.
  • Camera/Gallery app becomes unresponsive when taking a picture, sliding left to see the picture and tapping on it to see it in "full screen" then locking the screen for about 10 seconds. After that, if the user chooses to force close the Gallery app, when entering the Camera app again, the user will be prompted with the following error message: "Can't connect to the camera". Please, see the attached screenshot for more info.
  • Setting the light exposure to 4 or -4, the icon on the bottom right doesn't show any number (as it does for any other value) and if slide to the left to enter the Gallery and come back to camera app, the icon appears distorted. This happens only for value "4" or "-4". Workaround: switch to any of the other values and then back to 4.
    Please, see the attached screenshot for more info.
  • Zooming in/out doesn't work in video mode. Nothing happens when using two fingers to zoom in or out. No change in the actual image.
    Please, see the log below for zooming issue.
    Code:
     E/QualcommCameraHardware(148): Failed to get maximum zoom value...setting max zoom to zero
2. Text cut off in photo editor (To be confirmed in Beta 4)
  • The text for the "straighten" option is missing the first 2-3 letters in the default photo editor (please, see the attached screenshot for more info). The options section from that screen cannot be slid more to the left to see the rest of the word.
    This happens most likely because the spaces between the icons (options) from the top row of editing options don't adjust to the new screen orientation (Portrait). They look ok in Landscape mode, but it seems that the space between the icons from that row is kept the same no matter of the screen orientation, leading to some of the options not to be completely visible.
3. cLock widget not properly resizing in landscape mode (To be confirmed in Beta 4)
  • cLock widget does not properly resize when the launcher is set to Landscape mode (launcher auto-rotate option is ON). The widget is cut off (please, see the attached screenshot for more info). The widget looks good in Portrait mode. But when turning the screen to landscape mode, it's cut.
4. Phone encryption (To be confirmed in Beta 4)
  • Enabling encryption in the Security Settings will make the PIN code for the SIM card (assuming it's set to be requested) not to be requested anymore, thus making the "phone" part of the device unusable. No calls (voice or data), no SMS, no MMS can be sent or received. Workaround: make a nandroid backup before encrypting and restore it afterwards.
  • If the user turns off the SIM card PIN code request before performing the encryption, after it's finished, the APNs previously set will disappear and there won't be any way to re-add them manually, thus making the data connection unusable. He will be able to make voice calls and send SMS though.
  • After the encryption, if SIM PIN request is OFF, in the notification drawer and quicksettings panel, the user will be informed that he has no service (please, see the attached screenshots for more info) although, by going into Settings -> About Phone -> Status, he will see that the network is successfully recognized and there is definitely some service. (please, see the attached screenshot for more info on this too).
5. Random reboots after recently closing a phone call (To be confirmed in Beta 4)
  • From time to time, but apparently more often after recently (not immediately after) closing an incoming voice call, the phone reboots.
    This does not happen with kernel 3.4.56 but it does happen with 3.4.57 so it might be because of that reverted commit.
6. Some third party camera apps don't work properly in CyanogenMod. (To be confirmed in Beta 4)
  • Some third party camera apps don't work with any CM version from CM9 to CM10.1. For example, Camera 360 Ultimate v4.5 works ok on stock Android 4.1.2 and 4.2.2 (tested on Nexus devices) but doesn't work properly with any CyanogenMod version. After taking a picture, the camera preview gets stuck. No change in preview when tilting the phone.
    Please, see the log below from the moment when taking a picture with Camera 360. Maybe it helps solve this problem.
Code:
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.getParentParam(EffectInfoFactory.java:1433)
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.search(EffectInfoFactory.java:1303)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeAbstract.setEffect(ModeAbstract.java:106)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeNormal.onCameraStartPreview(ModeNormal.java:370)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraBaseActivity.onCreate(CameraBaseActivity.java:749)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraMain.onCreate(CameraMain.java:551)
V/QualcommCameraHardware(  143): As Auto Focus is not in progress, Cancel Auto Focus is ignored
V/QualcommCameraHardware(  143): cancelAutoFocusInternal X: 0
I/QualcommCameraHardware(  143): stopPreviewInternal X: 0
V/QualcommCameraHardware(  143): initRawSnapshot E
I/QualcommCameraHardware(  143): runframethread: waiting for preview  thread to complete.
V/QualcommCameraHardware(  143): initRawSnapshot X
V/QualcommCameraHardware(  143): takePicture: X
I/ShotSingle(  143): ShotSingle::takePicture end
I/CameraHAL(  143): camera_take_picture--- rv 0
I/QualcommCameraHardware(  143): initPreview: old preview thread completed.
QualcommCameraHardware(  143): destroying MemPool record
camera_set_preview_window---: window is NULL

V/QualcommCameraHardware(  143):  Overlay object NULL. returning 
I/CameraClient(  143): Destroying camera 0
I/CameraHAL(  143): camera_device_close+++: device 0x1f68650
I/SecCameraHardwareInterface(  143): SecCameraHardwareInterface destroyed: pid=143
I/ShotSingle(  143): ShotSingle destroyed: pid=143
I/ShotCommon(  143): ShotCommon destroyed: pid=143
No JNI_OnLoad found in /data/app-lib/vStudio.Android.Camera360-1/libmp3lame.so
I/ActivityManager(  430): Process vStudio.Android.Camera360 (pid 2142) has died.

7. USB tethering does not work
8. USB OTG does not work. (To be confirmed in Beta 4)[LIST]


XDA:DevDB Information
CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report, ROM for the Samsung Galaxy W I8150

Contributors
arsradu
ROM OS Version: 4.2.x Jelly Bean

Version Information
Status: Testing

Created 2013-09-29
Last Updated 2014-05-19
Attached Thumbnails
Click image for larger version

Name:	Enable Developer Options.jpg
Views:	7465
Size:	32.5 KB
ID:	1848795   Click image for larger version

Name:	Enable Advanced Reboot options.jpg
Views:	6883
Size:	34.4 KB
ID:	1848796   Click image for larger version

Name:	partial_straighten_text_option_cut_off.jpg
Views:	6576
Size:	17.7 KB
ID:	1860151   Click image for larger version

Name:	calculator widget lockscreen bug.jpg
Views:	5936
Size:	25.8 KB
ID:	1893661   Click image for larger version

Name:	cLock Widget cut off (new).jpg
Views:	5450
Size:	39.3 KB
ID:	1937426   Click image for larger version

Name:	no service in quicksettings panel.jpg
Views:	4648
Size:	18.7 KB
ID:	1958628   Click image for larger version

Name:	no service in notification drawer.jpg
Views:	4363
Size:	14.4 KB
ID:	1958629   Click image for larger version

Name:	service ok in network status.jpg
Views:	4398
Size:	19.9 KB
ID:	1958630   Click image for larger version

Name:	error can't connect to the camera.jpg
Views:	4338
Size:	19.4 KB
ID:	1959566   Click image for larger version

Name:	Panorama preview flickering.jpg
Views:	4238
Size:	11.0 KB
ID:	1963893   Click image for larger version

Name:	Gallery app unresponsive after taking a picture.jpg
Views:	4126
Size:	13.9 KB
ID:	1968645   Click image for larger version

Name:	Icon before opening gallery.jpg
Views:	3912
Size:	12.3 KB
ID:	1983396   Click image for larger version

Name:	Icon after opening gallery.jpg
Views:	3807
Size:	12.4 KB
ID:	1983397  
The Following 74 Users Say Thank You to arsradu For This Useful Post: [ View ] Gift arsradu Ad-Free
 
 
11th March 2013, 02:12 AM |#2  
Junior Member
Thanks Meter: 0
 
More
Plug charge
Opening off the phone while charging for no reason
sorry my bad english
I got help from google translate
11th March 2013, 10:25 AM |#3  
hotheabilly's Avatar
Senior Member
Flag padang
Thanks Meter: 1,107
 
Donate to Me
More
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks

-Sent from 4.2.2 powered i8150-
11th March 2013, 03:33 PM |#4  
blackcat67's Avatar
Senior Member
Thanks Meter: 451
 
More
Quote:
Originally Posted by hotheabilly

Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks

-Sent from 4.2.2 powered i8150-

arco new bcmdhd wifi driver dont working
The Following 2 Users Say Thank You to blackcat67 For This Useful Post: [ View ] Gift blackcat67 Ad-Free
11th March 2013, 04:48 PM |#5  
Senior Member
Thanks Meter: 22
 
More
The phone had been rebooting often.
Happened occasionally it rebooted even using camera and browsing the net.
11th March 2013, 05:28 PM |#6  
Junior Member
Thanks Meter: 1
 
More
I installed this rom. But sometimes, phone is locking and freezing. I am obliged to reboot.

(Sorry for my bad English)
12th March 2013, 01:37 PM |#7  
angelo.nero2004's Avatar
Junior Member
Thanks Meter: 3
 
More
Thumbs down Please rename this rom.
I'm writing this post because I read the whole thread in the Development section and it seems to me that calling this rom CM 10.1 is a bit misleading.
Sure blackcat67 may have done a bunch of work to get this out, but I don't think he has the rights to call it CM.

So I'm asking @blackcat67...PLEASE RENAME YOUR ROM.

Call it something like... [4.2.2][Blackcat]...as Xistance did for his... [4.2.1][Rootbox Alpha 1] ...but please don't call it CyanogenMod.
The Following 2 Users Say Thank You to angelo.nero2004 For This Useful Post: [ View ] Gift angelo.nero2004 Ad-Free
12th March 2013, 02:37 PM |#8  
Bernedeboi's Avatar
Junior Member
Flag São Paulo
Thanks Meter: 1
 
More
Quote:
Originally Posted by arsradu

Opening this thread in order for the people to post their issues here instead of the development section or CM10 bug report thread.

This thread refers to discussions/bug reports for CyanogenMod 10.1 posted today by blackcat67 here.

As usual it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.

For that, please, copy-paste this in your posts, editing it accordingly:


HTML Code:
[B]Version:[/B] CM10.1 - Alpha 1
[B]App/Game/Subject:[/B] WRITE HERE APPNAME
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Description:[/B] WRITE HERE BUG DESCRIPTION

I Will wait for Arco's or Camcory's version
13th March 2013, 01:08 PM |#9  
ipromeh's Avatar
Senior Member
Flag Kuala Lumpur
Thanks Meter: 3,505
 
Donate to Me
More
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Quote:
Originally Posted by Bernedeboi

I Will wait for Arco's or Camcory's version

Do we need to close this thread?

Sent from my GT-I8150 using xda app-developers app
13th March 2013, 01:51 PM |#10  
arsradu's Avatar
OP Senior Member
Thanks Meter: 3,276
 
More
Quote:
Originally Posted by ipromeh

Do we need to close this thread?

Sent from my GT-I8150 using xda app-developers app

I don't know, man.

I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.
The Following User Says Thank You to arsradu For This Useful Post: [ View ] Gift arsradu Ad-Free
13th March 2013, 01:57 PM |#11  
hotheabilly's Avatar
Senior Member
Flag padang
Thanks Meter: 1,107
 
Donate to Me
More
Re: CyanogenMod 10.1 - Discussion thread / Bug report
Quote:
Originally Posted by arsradu

I don't know, man.

I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.

Everybody want that, just patiently waiting. . .

-Sent from 4.2.2 powered i8150-
Post Reply Subscribe to Thread

Tags
bug report, cm10.1, cyanogenmod 10.1, discussion thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes