[ROM][ALPHA][JB]CyanogenMod 10 Alpha 3 [UPDATED 1/13]

Search This thread
By:
Advanced…
D

dragonzkiller

Inactive Recognized Developer
Jun 29, 2011
267
1,367
Wouldn't You Like To Know?
goo.im is slow. it's unfortunate that it's the "official" source for the gapps.

As far as MMS, I can send and receive MMS perfectly fine. Without any more information, I can't help you very much.
 
jsgraphicart

jsgraphicart

Senior Member
Nov 25, 2011
6,295
1,884
OnePlus 7T
Google Pixel 7 Pro
Anyone having trouble installing things from the play store? I installed one thing. Titanium backup. Then I tried downloading another and I get an error saying can't install to SD card or internal. I can see photos on my SD card so I have it mounted. Settings also see it.

Other than that, everything is FAST
 
A

apacseven

Senior Member
Aug 10, 2011
499
163
jsgraphicart said:
Anyone having trouble installing things from the play store? I installed one thing. Titanium backup. Then I tried downloading another and I get an error saying can't install to SD card or internal. I can see photos on my SD card so I have it mounted. Settings also see it.

Other than that, everything is FAST
Click to expand...
Click to collapse

He has a fix for it coming in alpha 2.
 
Q

qixiixiq

Senior Member
Aug 4, 2008
67
4
Passaic
DKZ is the man!

Long live the king!

I thought twitter would go down just from the number of times i was hittings DKZs page waiting for updates for my DX2...

I hope the 2 pages of posts dont reflect the last of the mohicans :crying:
 
B

bregga

Senior Member
Dec 23, 2011
85
3
what kinda info do you need for my mms

Tried rebooting a couple time but when i send a photo from my other phone it just doesn't come through ill try my wifes phone see if it works
 
maggard5

maggard5

Senior Member
Dec 24, 2011
240
71
It is a problem with the framework.

Sent from my Nexus 7 using XDA Premium HD app
 
B

bregga

Senior Member
Dec 23, 2011
85
3
mms

well my wifes box stock blaze 4 g just sits on sending to my phone not sure what it is I may sbf and reinstall it again and see if that clears it. just tried sending one but no go I'll sbf tomorrow and re install.
 
Last edited:
D

Deleted member 4177996

Guest
Anyone try videocam illusions app to see if we got lucky?

Sent from my MB870 using xda app-developers app
 
GoClifGo05

GoClifGo05

Senior Member
Jul 1, 2012
1,524
366
Maryland
DZK updated something just recently right? I downloaded the ROM and just installed it without looking back lol. Do i have to redownload it to get the sd card thing he fixed?
 
Tomsgt

Tomsgt

Senior Member
Sep 5, 2011
2,741
3,257
IN
www.rootjunky.com
Amazon 7" Kindle Fire HD
LG G8
redwingfaninnc said:
Anyone try videocam illusions app to see if we got lucky?

Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse

Videocam illusions work and if you install ICS camera app then camera also works

Sent from my Galaxy Nexus using Tapatalk 2

---------- Post added at 10:29 PM ---------- Previous post was at 10:28 PM ----------
GoClifGo05 said:
DZK updated something just recently right? I downloaded the ROM and just installed it without looking back lol. Do i have to redownload it to get the sd card thing he fixed?
Click to expand...
Click to collapse

SD card fix will be in alpha 2 the next release.

Sent from my Galaxy Nexus using Tapatalk 2
 
GoClifGo05

GoClifGo05

Senior Member
Jul 1, 2012
1,524
366
Maryland
Crap. Downloaded Titanium with no problems. Trying to redownload the pro key and "couldn't install on USB storage or SD card..." how do i get my pro key back?

Ok sorry for being so noobish.. Im in storage settings but how do you change storage locations? Im trying to install apps but all fail because of previously stated problem.

Just a side note, my MMS isnt working either. Not a huge issue for me.
 
Last edited:
You must log in or register to reply here.

Similar threads

D
[ROM][BETA][ICS]CyanogenMod 9 "Stable" BETA1[UPDATED 8/13]
Replies
2K
Views
389K
C
ctmax45
D
[UPDATED 4/20][ROM]CyanogenMod 7.2.0-RC1 X2 [BETA]
Replies
3K
Views
487K
P
Paul.ryan
nitroglycerine33
[ROM] Eclipse v2.3 (7/25/12)
Replies
6K
Views
820K
DQEight
DQEight
Lrs121
  • Poll
[ROM]{Alpha}(JB) Cyanogen Mod 10 MX2 Alpha-3 updated 1/12/2013
Replies
150
Views
42K
Lrs121
Lrs121
navenedrob
  • Poll
[POLL][ROM]Atrix 4G Stock 2.3.4 ROM + Ports and Development Thread
Replies
745
Views
133K
Sandso9
Sandso9

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 152
    D
    dragonzkiller
    dragonzkiller presents:
    CyanogenMod 10.0.0-RC0 For the Droid X2
    An Android 4.1.2 Jellybean Experience
    E1lOV.png
    0YBTP.png
    YLDMh.png

    HVbD4.png
    RyK9S.png
    0h4W9.png

    Features:
    • Pop-up Text Message Notifications
    • Lockscreen Customization
    • Status Bar/Pulldown Customization
    • Homescreen/Drawer Customization
    • Themes
    • Profiles
    • Hard Button Key Remapping
    • Quiet Hours
    • And ALL the Jellybean Featues: Google Now, Smarter Keyboard, Notifications Overhaul, and much much more!

    Working:
    • WiFi
    • Bluetooth (see known issues)
    • 3G
    • Calling
    • GPS
    • Google Now
    • Audio System! (This was the biggest thing keeping me from releasing CM10.)
    • Camera..... ish (See known issues)
    • Maps (You won't end up in a lake in Norway on your trip to the movie theater)

    New to Alpha 3:
    • Not much: that's about it. Few added features that were added from October until January, but not much has really changed.

    Known Issues:
    • Recovery: Recovery has been fixed since Alpha 2, but flashing ROMs doesn't work. Restoring nandroids will work fine however.
    • Bluesleep/Deep Sleep: at it's current state, Alpha 2 doesn't have the bluesleep fix in it. This is because when it is enabled the proximity sensor doesn't turn the screen back on when it's supposed to also causing the phone call to kill audio. This problem can also occur by toggling bluetooth ("fixing the bluesleep"). The only known work around is to press the home button and swipe your finger across the sensor. Thanks to 32BitWhore for the help.
    • Stability: While not exactly an issue as CM10 is INCREDIBLY more stable than CM9, that doesn't mean that it's 100% yet. As of now, I've only had the broswer crash twice and the notification drawer flicker once. Your milage will vary.
    • Camera: At it's current state, the camcorder will not work like in CM9. I can't really do much about that for the moment or at all.
    • Some ICS/JB Apps Will Crash: This is noticeable on Chrome for example. This is because our drivers don't have External OES Textures. Basically that means when the apps want to draw using them (such as with Chrome's tab preview) the app will crash. This is the same problem on CM9/ICS. There is nothing we can do.
    • Data usage: Just don't ask me. I might get to it again one day. We'll see.

    Installation:
    This can be installed over CM7/CM9 or BLUR but you MUST wipe data and cache if from CM7/BLUR. (CM9 should work w/o wipe, but it's untested).
    1. READ THE ENTIRE POST
    2. Download the links provided below and put it on the External SD Card
    3. Install the BSR (patched if on an AOSP based ROM, unpatched if on BLUR)
    4. Reboot into the BSR
    5. NANDROID
    6. Install the CM10 zip from the SD Card
    7. Install the GAPPS from the SD Card
    8. MILESTONE X2 USERS ONLY: Install the WiFi patch from the SD Card
    9. Wipe both DATA and CACHE if coming from BLUR or CM7 (no need to wipe Dalvik if you wipe both of these)
    10. Reboot your phone
    11. Enjoy a better phone experience

    Downloads:
    Also, if you would like (but not needed) to donate, see the donate button by my name. Gas/food money goes a long way :)
    I am not responsible for what you do to your phone. Flash at your own risk.
    REQUIRED Google Apps (GAPPS): http://goo-inside.me/google-apps. Download the latest Jellybean version (for 4.1.x) of them for here and check the MD5 sums from there also.

    MUST SBF IF COMING FROM A1.
    CyanogenMod 10-20130113-Daytona Alpha 3: http://d-h.st/82g

    Milestone X2 WiFi Patch (for all versions of 10): http://d-h.st/Pdy

    Changelog:
    Alpha 3:
    New CM10 Features added since October

    Alpha 2.999999999999:
    Update to 4.1.2
    Fix rebooting problem with SD Card apps
    Fixed internal/external swapping
    Performance updates via libc enhancements
    Some others, it's been a while
    CyanogenMod 10-20121028-Daytona Alpha 2.99999999: http://d-h.st/QcA

    Alpha 2:
    Fix SD Card apps
    Fixed camera app
    Added Advanced Settings (only HWA working)
    New WIFI Module (DX2 only)
    mediaserver (apparently) fixed
    CyanogenMod 10-20121007-Daytona Alpha 2: http://d-h.st/9J6

    Alpha 1:
    First Public Release
    Download: CyanogenMod 10-20120928-Daytona Alpha1: http://d-h.st/7y5
    View
    22
    D
    dragonzkiller
    Hey guys it's me. I've decided to spend time actually updating everything tonight. It's going to take FOREVER to get all the code updated (especially to 4.2). Also I'll work on getting the current sound drivers in that build working and release it tonight.
    View
    19
    D
    dragonzkiller
    Well... I'm still here. Even if I'm busy. And I'm working on 4.2.2 right now.
    View
    18
    D
    dragonzkiller
    Charge Mode/Recovery Fix for Alpha 1

    OK guys I have the fix for Alpha 1's charge mode and recovery please follow the steps carefully as I make sure everything is covered and that there are no questions to ask as long as you have read them and followed them properly. In my opinion if you already have ADB working, it is the easiest. It only looks long because it explains how to set EVERYTHING up if you don't have it. it is also VERY WISE to check the md5sum of the download to make sure it is correct and then checking the md5sum of the file once it is on the phone. This is easily done in Linux based distros (and on the phone in Terminal Emulator) as "md5sum hijack-boot.zip" (assuming you're in the same directory as it)

    Pushing the new file using ADB:
    1. Download the Android SDK OR any of the One-Click Roots. This has ADB which is required to push the files on the device. (Note: For the SDK, you'll have to start it up and then download "platform tools")
    2. Plug your phone into your computer with the USB cable
    3. If on Windows, you might have to download the appropriate drivers in order for it to find all of the necessary devices.
    4. If on Ubuntu based distros (and some other distros) of Linux, you'll have to add device permissions to allow your user to access the phone through the USB. (This is covered below.)
    5. Once you have the computer set up, on your phone go to "Settings > Developer Options > Root Access" and enable "Apps and ADB"
    6. Once everything is done loading open up a command prompt if in Windows (Press Win-R, then type "cmd") or a terminal in Linux (this varies by distro).
    7. Change your current working directory to be the location where ADB is installed by typing
      Code: 
      cd PATH/TO/ADB
      (For SDK users it's in the "platform-tools" folder under the SDK folder. OCRs are usually under a "files" folder in the root of the OCR.)
    8. To gain root access to your phone with ADB type:
      Code: 
      adb root
      (It should say "restarting ADB as root".) If it hangs, unplug your phone and plug it back in.
    9. Next type
      Code: 
      adb remount
      to remount the system directory as Read-Write. If it says something about being root, then make sure you ran the root command above.
    10. This is a critical step. Now it's time to copy over the new hijack-boot.zip. Type
      Code: 
      adb push PATH/TO/DOWNLOAD/hijack-boot.zip /system/etc/hijack-boot.zip
      This MUST be named this or it will not work. If the push succeeded it'll list some stats about the push and will end nicely. If it says "Read only file system" then you didn't run the remount command.
    11. Next reboot your phone by the Power Menu or by typing
      Code: 
      adb reboot

    Using Root Explorer or Other Root-Access File Managers:
    1. Copy the download to either SD card.
    2. Open up your File Manager and navigate to the appropriate SD card. (Internal is /storage/sdcard0, External is /storage/sdcard1)
    3. Remount the system directory as Read-Write. (Most File Managers have an option to do that, if not follow the steps above up to and including the remount command)
    4. COPY The new hijack-boot.zip file to /system/etc and overwrite the one currently there.
    5. Reboot you phone using the power menu.

    Using Terminal Emulator:
    1. Copy the download to either SD card.
    2. Open up the included Terminal Emulator app.
    3. Type
      Code: 
      su
      to switch to root and confirm the access if you haven't already.
    4. Type
      Code: 
      mount -o rw,remount /system
      to remount the system directory as Read-Write
    5. Copy over the download by typing:
      Code: 
      cp /storage/sdcard[B]#[/B]/hijack-boot.zip /system/etc/hijack-boot.zip
      This must be EXACT or it will not work.
    6. Reboot by typing "reboot" or by using the Power Menu.

    FIRST TIME ADB UBUNTU-BASED (RARELY OTHERS) USERS ONLY:
    Some GNU/Linux distros have a security "feature" that keeps users from directly accessing any USB device that pretty much isn't an HID device or a Mass Storage one. To get around this go here and follow only the Configuring USB Access section adding the following lines to the end of your rules:
    Code: 
    # adb protocol on daytona (Droid X2) on CM9
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70c9", MODE="0600", OWNER="<username>"
# adb protocol on daytona (Droid X2) on CM10
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70c7", MODE="0600", OWNER="<username>"
    It is recommended to go ahead and allow the AOSP rules to be there as well. It doesn't hurt anything. But make sure you replace <username> with your username you log in with.

    DOWNLOAD:
    Fix for charge mode and recovery in Alpha 1: http://d-h.st/1jF
    View
    11
    D
    dragonzkiller
    I had received 32BitWhore's PM also and I figured I might as well tell everyone that the bug has been confirmed and I will update the OP accordingly. The problem appears to be surfaceflinger not reporting the correct display to start drawing to again. This prevents the system from turning the screen back on and drawing what it needs to. I will do a more in depth study when I get the time. How the bluesleep fix is responsible, I'm not sure yet and because of that I didn't put it in A2.
    View

New posts