It's a problem with Alpha 1. Some apps cannot be downloaded to the sdcard. It will be fixed in Alpha 2.
Sent from my Nexus 7 using XDA Premium HD app
[ROM][ALPHA][JB]CyanogenMod 10 Alpha 3 [UPDATED 1/13]
- Thread starter dragonzkiller
- Start date
-
- Tags
- development
It's a problem with Alpha 1. Some apps cannot be downloaded to the sdcard. It will be fixed in Alpha 2.
Sent from my Nexus 7 using XDA Premium HD app
Ok thanks, i understand that. So there is no way to change storage locations is what i'm getting at? all the apps i can't use until the A2 is released? Can't install my pro keys for anything, or most of my apps. Strange.
Last edited:
OK. I'm pretty sure the problem is the SD flip flop mod. At least part of the problem. Everyone's been using 8+ gigs for their internal and now we only have 4. I can download some apps depending on their size. My SD card is full so apps won't install. Not saying ext4 isn't a problem but I've been Able to install some apps after uninstalling others.
This is really smooth, even landscape mode is working in the stock browser. Once again, amazing work.
At some point we need to do an IAMA Dragonzkiller, I for one need to confirm he's human and not some futuristic robohumanoidbot.
At some point we need to do an IAMA Dragonzkiller, I for one need to confirm he's human and not some futuristic robohumanoidbot.
Lol. I agree. We think he's some technological advanced human but he's just like one of us. Only smarter. lol. Thanks DK
I am going to try my best tomorrow to get charge mode working. Idk how JB changed it, but it's not working like it should. That being said, alpha 2 will have it fixed.
Also as a side note: JB integrates it's camera into the same apk as the gallery. After some work, I managed to update the camera side of it to work. After some more work I managed to get panorama working as well. As of now (alpha 2 that is) the camera works the same as it does in ICS.
It is how Android mounts partitions, not so much with the storage flip flop. DZK updated the framework to force FAT instead of EXT4 and he reports that it works and will be fixed in A2. You can browse the drive because it is mounted to read a FAT partition.
At least that is my understanding from the IRC today.
Working well so far. Very fast and smooth out of the box.
Issues so far:
The aforementioned SD issues, though I was able to work around a few of them (namely TiBU Pro Key) by installing apps individually using the free version of TiBU.
Facebook App seemingly runs out of memory after scrolling down my news feed after only a few lines. No FC error, just shuts down with no message.
I appear to be having the MMS issue that some have mentioned, which wouldn't be a big deal except messages over 160 characters seem to be converting to MMS automatically. Maybe I'm crazy but I can't seem to find the option to split SMS instead of converting. Am I missing something?
Otherwise very pleased with overall stability and battery life. I was thrilled with Google Now on my Nexus 7, but it's way cooler on a data-enabled device. Well done as always DZK.
Issues so far:
The aforementioned SD issues, though I was able to work around a few of them (namely TiBU Pro Key) by installing apps individually using the free version of TiBU.
Facebook App seemingly runs out of memory after scrolling down my news feed after only a few lines. No FC error, just shuts down with no message.
I appear to be having the MMS issue that some have mentioned, which wouldn't be a big deal except messages over 160 characters seem to be converting to MMS automatically. Maybe I'm crazy but I can't seem to find the option to split SMS instead of converting. Am I missing something?
Otherwise very pleased with overall stability and battery life. I was thrilled with Google Now on my Nexus 7, but it's way cooler on a data-enabled device. Well done as always DZK.
Huh how can you tell how good thee battery life is without playing with it fora few days 0.o??
The Android Facebook app is a horrible one still running on HTML5 and not the native APIs. They've apologized for it and hopefully will have one out soon enough.
The splitting of text messages hasn't been committed into the repos yet. Basically until the code for the SMS split gets updated anything over 160 characters will convert into MMS. I don't exactly like it either, but that's what we have to deal with right now.
Random reboots at all anyone? That's all I'm really hesitant about... 
Sent from my MB870 using xda app-developers app
Sent from my MB870 using xda app-developers app
no reboots here
Have not had any reboots and reboot time seems alot faster with jb.
mms all of a sudden started working so all is good happy I did not have to sbf.
Random reboots at all anyone? That's all I'm really hesitant about...
Sent from my MB870 using xda app-developers app
Have not had any reboots and reboot time seems alot faster with jb.
mms all of a sudden started working so all is good happy I did not have to sbf.
Last edited:
I have an mx2 on aokp cm9. I'm guessing I'll have to remove the kernel check or wait on an mx2 release. No big deal though. Its awesome what development is being done without kexec or unlocked boot loaders. If all I have to do is remove the kernel check I'll try to later today.
Sent from my MB870 using xda premium
Sent from my MB870 using xda premium
One of the features in JB is the "buttery smooth" interface. Anyone confirm that compared to CM7 & 9?
Sent from my DROID X2 using xda app-developers app
Sent from my DROID X2 using xda app-developers app
There is most definitely a noticeable difference in how this operates compared to CM9. App drawer side-swiping and screen rotation are the two easiest tests for me to try, and there isn't any other word to describe it except "buttery." Very pleased. I put it through its paces last night (ran down about 50% battery) and no random reboots or SODs so far.
My only question is why our device was passed over for an OEM upgrade to JB. If a ported version runs so well on a garbage kernel, I can only imagine how well an official version would work on our hardware. Ah well, such is life, and this is the reason we have crazy awesome devs like DZK. Hope your upgrade doesn't come any time soon man.
There is most definitely a noticeable difference in how this operates compared to CM9. App drawer side-swiping and screen rotation are the two easiest tests for me to try, and there isn't any other word to describe it except "buttery." Very pleased. I put it through its paces last night (ran down about 50% battery) and no random reboots or SODs so far.
My only question is why our device was passed over for an OEM upgrade to JB. If a ported version runs so well on a garbage kernel, I can only imagine how well an official version would work on our hardware. Ah well, such is life, and this is the reason we have crazy awesome devs like DZK. Hope your upgrade doesn't come any time soon man.
I bet he'd love a GS3
Sent from my MB870 using xda app-developers app
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
152dragonzkiller presents:
CyanogenMod 10.0.0-RC0 For the Droid X2
An Android 4.1.2 Jellybean Experience
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).
- READ THE ENTIRE POST
- Download the links provided below and put it on the External SD Card
- Install the BSR (patched if on an AOSP based ROM, unpatched if on BLUR)
- Reboot into the BSR
- NANDROID
- Install the CM10 zip from the SD Card
- Install the GAPPS from the SD Card
- MILESTONE X2 USERS ONLY: Install the WiFi patch from the SD Card
- Wipe both DATA and CACHE if coming from BLUR or CM7 (no need to wipe Dalvik if you wipe both of these)
- Reboot your phone
- 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/7y522Hey 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.1918Charge 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:
- 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")
- Plug your phone into your computer with the USB cable
- If on Windows, you might have to download the appropriate drivers in order for it to find all of the necessary devices.
- 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.)
- Once you have the computer set up, on your phone go to "Settings > Developer Options > Root Access" and enable "Apps and ADB"
- 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).
- Change your current working directory to be the location where ADB is installed by typing
(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.)Code:
cd PATH/TO/ADB - To gain root access to your phone with ADB type:
(It should say "restarting ADB as root".) If it hangs, unplug your phone and plug it back in.Code:
adb root - Next type
to remount the system directory as Read-Write. If it says something about being root, then make sure you ran the root command above.Code:
adb remount - This is a critical step. Now it's time to copy over the new hijack-boot.zip. Type
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.Code:
adb push PATH/TO/DOWNLOAD/hijack-boot.zip /system/etc/hijack-boot.zip - Next reboot your phone by the Power Menu or by typing
Code:
adb reboot
Using Root Explorer or Other Root-Access File Managers:
- Copy the download to either SD card.
- Open up your File Manager and navigate to the appropriate SD card. (Internal is /storage/sdcard0, External is /storage/sdcard1)
- 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)
- COPY The new hijack-boot.zip file to /system/etc and overwrite the one currently there.
- Reboot you phone using the power menu.
Using Terminal Emulator:
- Copy the download to either SD card.
- Open up the included Terminal Emulator app.
- Type
to switch to root and confirm the access if you haven't already.Code:
su - Type
to remount the system directory as Read-WriteCode:
mount -o rw,remount /system - Copy over the download by typing:
This must be EXACT or it will not work.Code:
cp /storage/sdcard[B]#[/B]/hijack-boot.zip /system/etc/hijack-boot.zip - 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: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.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>"
DOWNLOAD:
Fix for charge mode and recovery in Alpha 1: http://d-h.st/1jF11I 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.
