Related
Finally here it is, the long awaited CM10 for Nook HD+ (early snapshot, anyway).
This codebase is currently hardcoded to work from sdcard only.
How to build from source (you need to meet all the usual cm10 build prerequirements),
Get the source:
Code:
mkdir android/system
cd android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/ovation-jb/local_manifest.xml
repo sync -j16
(device repo on github)
(temp kludge for source kernel build: get my kernel from https://github.com/verygreen/green_kernel_omap and put it to kernel/bn/ovation (use ovation-3.0 branch for 3.0.31 kernel or ovation-aosp-kernel for 3.0.50), then put B&N source distro copies of wlan and wpan kernel dirs to external inside of kernel dir, and also desired version of sgx proprietary-open tar file into external/sgx)
Build:
Code:
. build/envsetup.sh
lunch cm_ovation-userdebug
. vendor/cm/get-prebuilts
mka bacon
In the out/target/product/ovation output dir you'll have the update file generated: cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip
If you do not want to build from source, here's my current (as of this post, see bottom for newer versions) binary snapshot: cm-10-20130511-UNOFFICIAL-ovation-sdcard.zip
(additionally there's emmc version, follow installation instructions here, but use this install file: cm-10-20130511-UNOFFICIAL-ovation-emmc.zip)
You will also need updated cwm image: sdcard-cwm-early4.img.gz
For first time install only (you will need 4G or bigger sdcard, smaller ones are not supported and not tested):
gunzip cwm image and write it to your sdcard (entire sdcard not just one partition of it), use either dd on Linux/MacOS or Win32 Image Writer for those impaired by Windows. Make sure to use sdcard rated for fast small IO for best results.
(Note: There is now experimental recovery image that does not require adb that's currently documented in this post)
Insert the card into the Nook and reboot the nook, CWM should start.
(This will also automatically repartition the card into a correct layout no matter the size (but no smaller than 4G).
In the CWM:
Go to "mounts and storage", choose "mount /sdcard".
Press power button to go back to the main menu.
Now do
Code:
adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard
Also push whatever other zip files you want to install to /sdcard too.
(if you don't have operational adb, you can also just turn off the nook at this stage, put zip files to volume named "CM10SDCARD" (not "boot"), then put sdcard back into nook and start it again)
Next, choose "install zip from sdcard", and then "Choose zip from sdcard" and first cm-...zip, and then whatever other packages you have the need to install.
When done installing, press the power button to go one level up in the menu and then choose reboot.
This will reboot you into CM10.
If you ever need to get back to CWM later, use either "reboot to recovery" power menu, or reboot, and once B&N nook logo shows up, press and hold power and home keys together for about 4 seconds.
To reboot into stock nook software, just poweroff, remove sdcard, then poweron.
Caveats:
- Current sdcard layout is ~800M system and ~900M data for less than 16G and 2G data for 16G+ cards, the rest is a separate sdcard (because having sdcard to live on data is kind of dangerous). I am still taking feedback on these sizes better to change these early on while there are not a lot of users.
- This snapshot uses B&N binary kernel from 2.0, it happens to oops in mtp_open if you have mtp storage mode enabled and plug into a computer, so steer clear of it for now I guess, this will be fixed later. (if your nook reboots when plugged into computer or right on boot while plugged - this is it, likely to happen after first install).
- /cache is shared with stock ROM, helps for slower sdcards at the expense of slower boots when you switch your OS from stock to CM10 or back.
- Upgrade from 20121209 snapshot note: that snapshot had bad kernel that had problems with sdcards. Most advisable thing is to redo entire install (after downloading new, cwm-early3 image first). You might also be able to just install kernel from the update.zip and write it to the first partition on the sdcard, that shuld also fix all issues and will let your existing cwm to work to flash this new image.
Things that I know are not working:
- Coming out of sleep sometimes there's a crash (this is related to wifi, the workaround is to disable wifi while sleeping in the options).
- Rebooting to stock with sdcard still in causes stock to hang at 99% booting and sit there, simply pop out the sdcard and it will finish booting.
- on-headphones microphone is not currently used even if present (I now believe this is actually not a bug, and stock has the same behavior).
- Bluetooth signal strength is very low
- Hulu+ and other such things requiring DRM do not work.
This is now at feature-parity with stock B&N ROM, I believe (other than DRM).
Experimental versions:
Other than the stable version above, there are some experimental versions below that are tested before (hopefully) being promoted to the stable status.
01/07 version with a different kernel, otherwise same as 12/31
01/08 version with a recompiled B&N kernel, otherwise same as 12/31
01/19 version with a yet another different kernel, updated CM10 base and default dpi/screen size changes
02/12 Some CM10 changes from upstream and updated wifi drivers from B&N 2.0.6 code drop (hoping that it will fix the annoying coming out of suspend crash - nope, it did not.)
02/20 Don't reboot into emmc stock on crash, it does us no good. Revert Z-axis in accelerometer for hopefully better responsiveness.
wifi should no longer drain battery when sleeping, cover close will blank screen, gfx issues hopefully fixed
Enjoy.
Finally, a major step in the right direction. Thank you very much for your efforts.
Thanks for that.
One question before try it:
formating /sdcard from CWM will not format the internal "sdcard" directory of the Nook?
Thank you very much. Your work is always appreciated.
The ability to mount and use the internal storage would be great.
Many thanks for this, got it working for some reason the format sdcard step seemed to fail - but got it working by manual format under linux.
Now have gapps and everything else I need installed - so will play with it later but so far seems to run very smooth.
Agree that seeing nook internal storage would be good
Wow, fantastic, will try it tonight. Just checking, no problem using 64G card? Also, I'm assuming for the moment it leaves the complete data structure in tact on the B&N internal memory? Just mostly not mounted? Reason I ask is its a shortcut to get the apps that are already installed there, especially the B&N specific ones. Otherwise I could pull with ADB.
Thanks again!
verygreen said:
Caveats:
- Current sdcard layout is ~800M system and ~900M data, the rest is a separate sdcard (because having sdcard to live on data is kind of dangerous). I am taking feedback on these sizesm better to change these early on while there are not a lot of users.
- There's no access to "sdcard" on internal nook drive, though this could be organized if people think that's useful.
- This snapshot uses B&N binary kernel from 2.0, it happens to oops in mtp_open if you have mtp storage mode enabled and plug into a computer, so steer clear of it for now I guess, this will be fixed later. (if your nook reboots when plugged into computer or right on boot while plugged - this is it).
- /cache is shared with stock ROM, helps for slower sdcards at the expense of slower boots when you switch your OS from stock to CM10 or back.
Click to expand...
Click to collapse
Nice, just some quick questions here.
when you said build, I assume you means cross-compile, right? I know most people are not gonna compile stuff themself, and just use the binary. But so people know if they wanna learn since x86 and arm are different architecture. Just compiling from x86 isn't gonna work.
I agree the size is a bit bloated ATM. Even the gigantic Galaxy Note 2 is about that size also.
The access to internal SD can be useful. Assuming you brought 32GB version of Nook, then you have like 25GB+ worth of storage sitting there. If possible it should be mounted(only old /mnt/sdcard area), whether that be to /mnt/sdcard or /mnt/int_sdcard
I notice you build this based on JB version of android, which is what 4.1 or 4.2? But still using the B&N kernel which is 4.0.4? I'm sure some of the stuff works. I made that mistake as well when attempt to put Play market on the nook earlier.
Thanks for your hardwork.
someone0 said:
Nice, just some quick questions here.
when you said build, I assume you means cross-compile, right? I know most people are not gonna compile stuff themself, and just use the binary. But so people know if they wanna learn since x86 and arm are different architecture. Just compiling from x86 isn't gonna work.
Click to expand...
Click to collapse
Yes, it's cross-compiling, which is still building.
The cm repos provide necessay cross-compilers and all that stuff, though.
I agree the size is a bit bloated ATM. Even the gigantic Galaxy Note 2 is about that size also.
Click to expand...
Click to collapse
So the better sizes are?
I notice you build this based on JB version of android, which is what 4.1 or 4.2? But still using the B&N kernel which is 4.0.4? I'm sure some of the stuff works. I made that mistake as well when attempt to put Play market on the nook earlier.
Click to expand...
Click to collapse
build is based around 4.1.2.
B&N kernel is pretty much inline with JB (3.0.31), so it works pretty well (other than the mtp_open oops). I'll switch to building it from source anyway, but this will take some time.
dbh369 said:
Wow, fantastic, will try it tonight. Just checking, no problem using 64G card?
Click to expand...
Click to collapse
I don't have anything this big, so only tried 16G.
Also, I'm assuming for the moment it leaves the complete data structure in tact on the B&N internal memory? Just mostly not mounted?
Click to expand...
Click to collapse
Mostly. /cache is shared so this one is modified.
Also to get recovery we are reusing stuff in /bootdata (BCB and boot counter).
Reason I ask is its a shortcut to get the apps that are already installed there, especially the B&N specific ones. Otherwise I could pull with ADB.
Click to expand...
Click to collapse
You should not be sharing apps between the two, they might be different version too, anyway.
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Verygreen, thank you for all your continued hard work with the CM/NOOK bases.
Thanks for this.
A few things , you are maybe already thinking of implementing these:
1. It would be good if you could dual boot both systems with a menu or holding a volume button to boot to stock nook os, instead of having to take out the sd card, save a bit of time and ease (the slot is quite hard to open )
2. Access to internal storage would be good. I have 32gb nook, so not being able to use 25gb of free space on the internal storage is not great, but I'm sure its quite easy to fix. Is it just a matter of mounting it correctly ?
Everything seems great, with the tearing issue do you know what the problem is ?
jay_ntwr said:
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Verygreen, thank you for all your continued hard work with the CM/NOOK bases.
Click to expand...
Click to collapse
I could be proved wrong but I don't think it will work for you on a HD. It doesn't work on a HD for me....
With Nook HD, try rebooting a few times with card installed see if it goes to cwm,
tried on HD
CelticWebSolutions said:
I could be proved wrong but I don't think it will work for you on a HD. It doesn't work on a HD for me....
Click to expand...
Click to collapse
I tried the CWM card in my HD. I can concur that the HD doesn't boot from the card, it just goes to rooted stock.
ArcSmurf said:
Many thanks for this, got it working for some reason the format sdcard step seemed to fail - but got it working by manual format under linux.
Now have gapps and everything else I need installed - so will play with it later but so far seems to run very smooth.
Agree that seeing nook internal storage would be good
Click to expand...
Click to collapse
I got this problem too, format sdcard from cwm doesn't work.
It says Failed to mount /sdcard ... Skipping format ..
How did you fix ?
Really loving your efforts! Damn, thank you very much! I'll see if I can contribute soon, after I get my new computer. Can't wait for CM10 on HD+, it'll actually utilise the Nook HD+'s potential. It's dual-core, it can playback full HD, but it's limited by software.
Managed to get it to format sd card after I messed about formatting the sd card completely again and writing the cwm image
HiddenG said:
Really loving your efforts! Damn, thank you very much! I'll see if I can contribute soon, after I get my new computer. Can't wait for CM10 on HD+, it'll actually utilise the Nook HD+'s potential. It's dual-core, it can playback full HD, but it's limited by software.
Click to expand...
Click to collapse
quadcore.
jay_ntwr said:
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Click to expand...
Click to collapse
Yes, this will not work on the nook HD directly, that has different uboot, different kernel and different SoC (not to mention different display).
I can't get /sdcard to mount or format no matter what I do. I'm using Windows, which seems to always be a hindrance in the root community.
Also, I'm fairly certain the the Nook HD+ processor (OMAP 4470) is a dual-core. Besides the main cores it has the two ARM Cortex-M3 cores, but it is still technically a dual-core processor.
PS- I'm running the Nook HD+ 16GB. Could the 16GB vs. 32GB cause any issues? Just wondering.
By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution as before, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Simplified instructions if instructions below don't work for you or you cannot follow them.
Get emmc-cwm-early2.1.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost).
Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need ONE of these).
Also download latest binary zip from CM nightlies: http://download.cyanogenmod.com/?device=ovation
Add all these files + whatever other packages you might need right away on to the sdcard.
Boot from that sdcard, and install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Erase /data (During initial install only. this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there).
unmount /sdcard and remove the card from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD+.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up). (QS controls are not available in CM nightly builds so you'll need to install the switcher app for now if you need it).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - This is because they specifically blacklist Nooks! Note that workaround #2 will actually kill your sound, so revert back when you are done.
- Certain sdcards still remain unstable.
- Google Earth crashes when pressing "my location" button (but works fine otherwise).
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (not really needed, as you can use Quick Settings panel): USBHostSwitcher.apk
Changelog:
13/08/09 - We are official part of CM now, yay! Further updates will be at http://download.cyanogenmod.com/?device=ovation
13/08/01 - cm-10.1-20130801-UNOFFICIAL-ovation-emmc.zip
- Data usage display should work now
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
13/07/16 - cm-10.1-20130716-UNOFFICIAL-ovation-emmc.zip *Experimental*
- Update wifi drivers to R5.SP3.06
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip
- Updated to CM-10.1.1 for security fixes
13/07/08 - cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip
- NTFS and ExFAT support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip
- redone touchscreen sensitivity changing mechanism. (app to control touchscreen sensitivity NookTouchscreenSensitivityAdjuster-4.apk)
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip Experimental
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip
- in-kernel bluetooth
13/06/26 - cm-10.1-20130626-UNOFFICIAL-ovation-emmc.zip Experimental
- cpu frequency changes for screen on scenario, new sgx binary blobs.
13/06/24 - cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-emmc.zip
- Boosted speaker volume. If you do not like new loud volume, flash this reversal zip after every ROM update: quietvolume-2.zip
- zinio now should work out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-emmc.zip
- Fixed HDMI audio
- Added USB audio support
13/06/08 - cm-10.1-20130608-UNOFFICIAL-ovation-emmc.zip
- Fixed nav bar settings crash
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-emmc.zip
- USBHost access is now conveniently located in QuickSettings. (IF you use some mod that disables quick settings, you still need my old ugly USBHost switcher app, just sideload it).
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-emmc.zip
- Forced USB Host support.
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-emmc.zip
- No Nook-specific changes, based on CM10.1-RC3
13/05/27 - cm-10.1-20130527-UNOFFICIAL-ovation-emmc.zip
- Fixed microphone input volume
- Kernel change to hopefully better work with some sdcards.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip
- Fixed A2DP audio
- Fixed booting when not connected to PC/charger.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-emmc.zip
- Should fix sgx crash on startup for those affected -- not.
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
13/05/10 - cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip
- Wifi battery drain should be gone now.
13/05/05 - cm-10.1-20130505-UNOFFICIAL-ovation-emmc.zip
- Fixed mmc presentation, BT, sdcard mounting.
13/05/04 - cm-10.1-20130504-UNOFFICIAL-ovation-emmc.zip initial release.
Thanks for this though.
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Also I don't think cm10 is needed really.
I think its best to put the work into cm10.1 as its the latest platform and try bring that up to the same stage as cm10.
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
HiddenG said:
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
Click to expand...
Click to collapse
Is the reboot to 99% problem solved ? This is the biggest issue to me.
sorrowuk said:
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Click to expand...
Click to collapse
Same method as Bauwks, B&N forgot to fix it, they fixed some other possible vectors only.
I was holding to this knowledge hoping that it would be useful on next B&N reader, but it does not look like they'll release another omap-based one, so no need to keep suffering anymore.
So here's hope whatever they release next, the debugging code will remain in place
HiddenG said:
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Click to expand...
Click to collapse
Yes, this does overwrite stock ROM, so no dualboot.
While it's possible to perform some hair-splitting by putting multiple kernels into boot partition, that's quite a bit of hassle + all the /data splitting, so I decided to not go that way, at least yet.
There are performance differences. I did not perform any real studies, but I was shocked at how fast the install phase in cwm works compared to sdcard.
lchen5 said:
Is the reboot to 99% problem solved ? This is the biggest issue to me.
Click to expand...
Click to collapse
Yes, it is solved by removing the ROM, so nothing is left there that could complain about cards with too many partitions
Awesome
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
aszid said:
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
Click to expand...
Click to collapse
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Click to expand...
Click to collapse
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Follow up question
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
For restore (note, I did not really test any of these steps, but that's how it should unfold):
boot into recovery image from sdcard you made at the beginning.
Upload the backup boot image there (adb push mmcblk0p4 /tmp)
then do adb shell and in there write the image in place:
dd if=/tmp/mmcblk0p4 of=/dev/block/mmcblk0p4 bs=1048576
then do:
mount /bootdata ; rm /bootdata/BootCnt
The removal of BootCnt will tell stock u-boot to force factory restore.
now remove sdcard and reboot, the Nook will do factory restore and you are back to some sort of early 2.0.0 B&N release.
verygreen said:
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Click to expand...
Click to collapse
I've been trying to examine what you have done here, and have most of it figured.
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
A suggestion on the CWM recovery.fstab. Change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
Click to expand...
Click to collapse
Yes, it's pretty straight-forward, and that was one of the goals. Unlike Kindle where you need to jump through some crazy hoops due to Amazon design decisions, Nook is significantly more relaxed.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
Click to expand...
Click to collapse
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
The only difference between this CWM and sdcard cwm for sdcard installs are: removed repartitioning code in postboot script and updated fstab to point back at emmc.
A suggestion on the CWM recovery.fstab, change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Click to expand...
Click to collapse
Aha, thanks. I'll try this and it'll probably solve the remaining CWM problems for me.
Also need to do twrp image, I guess.
verygreen said:
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
Click to expand...
Click to collapse
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
And if you make those mods to the recovery.fstab, then users can use that CWM to reflash back to stock using the B&N zips.
leapinlar said:
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
Click to expand...
Click to collapse
Whoops, forgot to remove.
This is how I zero out sdcard content so it better compresses before uploading it somewhere.
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Got it going
Thanks Verygreen and Leapinlar.
I got it installed and I saved the boot partition just in case. I hopefully will not be needing to restore, but it is nice to know that I can.
The installed ROM appears snappy and I will report back any issues I discover.
my sdcard is working great after updating the mount. Thanks!
leapinlar said:
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
Click to expand...
Click to collapse
verygreen said:
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Click to expand...
Click to collapse
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Thanks for all the great work!
aszid said:
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Click to expand...
Click to collapse
There's no great logic in my recovery, just an image I use to test-drive my installs for now.
So you can use whatever other recovery you like.
ROM:
http://www.mediafire.com/download/8...-4.4.4.build.8.1-UNOFFICIAL-20141001-2013.zip
MD5
http://www.mediafire.com/download/o...build.8.1-UNOFFICIAL-20141001-2013.zip.md5sum
***********SOURCE************
Kernel:
http://www.mediafire.com/download/oc2b51rpgblasbd/linux_omap_ovation.tar.gz
(Yellow Kernel v14 + exfat filesystem added)
Miscellaneous build files:
http://www.mediafire.com/download/0oszo0esv70xig0/slim.tar.gz
Known Issues:
Hardware 'n' key isn't mapped to do anything.
Although kernel supports f2fs, I haven't found a good way to incorporate f2fs into the ramdisk/init files to actually support mounting of f2fs filesystems yet (I'll have to take a look at how other slim devices do it).
I believe quake is broken (easy to remove under slimcenter).
Exfat fs remains untested (If anyone has a large sdcard...)
None of these issues have I spent much time on...
Only lightly tested. No warranties or guarantees.
A terminal app can be found in /system/addon.d/app
Thanks for building this for Ovation. I'll try it over the weekend.
Sent from my CM11 Ovation on Tapatalk
OMGOMGOMGOMG. i am so glad to see this. i run slim on all my devices, and now the nook? hell yeah
thanks jon
Could someone post the zip download caption? Something like Slim-ovation-4.4.4.build.8.1-UNO..."
I won't be testing this at this stage, but I wanted to thank you for working on it. There's a good chance I will switch to it when it is more polished and stable, especially with f2fs support.
I have it up and running. All appears well thus far. Pretty snappy
Lookin good here (FYI I'm using TWRP 2.8). One question, I can't find where to turn on Advanced Power Menu features, like Reboot to Recovery. Yes, I activated Dev Options.
sent from my SlimKat Ovation on Tapatalk
neutronjeff said:
Lookin good here (FYI I'm using TWRP 2.8). One question, I can't find where to turn on Advanced Power Menu features, like Reboot to Recovery. Yes, I activated Dev Options.
sent from my SlimKat Ovation on Tapatalk
Click to expand...
Click to collapse
Go to settings/security/device administration/advanced reboot and choose either hide on lockscreen or show always. However, rebooting to recovery does not seem to work. When selecting it from the power menu, it just performs a regular device reboot.
Haven't tested everything but other than the reboot to recovery not working, the build seems pretty solid. Will continue to test further. I installed using TWRP 2.7.1, also flashed slim gapps 4.4.4 for build 8, which Slim team recommends. I used the mini gapps as opposed to full, I'd rather download the specific apps from PS as I need them.
OP, thanks again for giving us a new rom for a device where unfortunately, there are very few choices. :good: :good:
Mike T
How does this ROM compare to Succulent's or 10.2 roms? I've kept my wife's Nook on 10.2 since it's been the most stable ROM I've found. Tried CM11 several times with her hating the builds due to FC and reboots. I've always reverted back to backup of 10.2 rom.
webdroidmt said:
Go to settings/security/device administration/advanced reboot and choose either hide on lockscreen or show always. However, rebooting to recovery does not seem to work. When selecting it from the power menu, it just performs a regular device reboot.
Haven't tested everything but other than the reboot to recovery not working, the build seems pretty solid. Will continue to test further. I installed using TWRP 2.7.1, also flashed slim gapps 4.4.4 for build 8, which Slim team recommends. I used the mini gapps as opposed to full, I'd rather download the specific apps from PS as I need them.
OP, thanks again for giving us a new rom for a device where unfortunately, there are very few choices. :good: :good:
Mike T
Click to expand...
Click to collapse
I haven't had any reboots so far, just the browser FC's which seem to be pretty universal across every rom i've tried. I'm going to play around some more...
Have been using it for a few hours, looks really good. Exfat is working for me too. Will take a look at the sources later, might try f2fs at some point. Have you thought about setting up a github ?
Happy to NOT see the theme engine in the list of running apps ! This is awesome !
Sent from my BN NookHD+ using XDA Premium HD app
Exfat support lost after unmount
I unmounted my 64 Gb microSD (exFat format) to copy some videos onto it (physically removed the card so I could put it in my PC's card reader). When I re-inserted the card, the nook couldn't mount it, saying the filesystem was unsupported. No problem mounting & reading the card after reboot. I suspect it's just something in the rc.init ? Will look into it later...
How would one map that hardware button?
Great rom, but force of habit to hit N instead of soft keys.
Also, I just like hardware, too.
Volume buttons are switched currently, too. Mapping them to the normal up/down and a working N will make this amazing.
---------- Post added at 05:14 PM ---------- Previous post was at 05:09 PM ----------
I knew I was forgetting something!
Battery status says discharging (settings and qs tile), but the charging animation is working properly.
angelofmenoth said:
Battery status says discharging (settings and qs tile), but the charging animation is working properly.
Click to expand...
Click to collapse
The charging indicators and animations seem to be fine for me...and my volume is as expected in landscape mode. Wierd. I'm using Nova, are you?
sent from my SlimKat Ovation on Tapatalk
Charging indicator working after restart.
Weirdest thing is... the N key is mapped to home in the keylayout. Why does the kernel not read it?
And also, it can wake the device.
Probably the easiest way to fix the 'n' key mapping would be to do a diff between /system/usr/keylayout between this rom and say, the 4.4.3 build. Or just change the files out altogether.
I believe I gave all the necessary source files to recreate the build as I had it, if anyone wants to work on it further. I could have spent an extra day and made it build 8.2, but I wanted to work on other things (changed out my harddrive immediately after posting the rom). In the next upcoming weeks I'll be experimenting with building several other rom flavors and perhaps do a little more kernel work as well.
Hey, wherever the muse leads...
sent from my SlimKat Ovation on Tapatalk
I just tried replacing both keylayouts and keychars and it didn't seem to help the button mapping.
Hi guys,
for those of us who are waiting for at least the M1 of CM12 before switching lanes, I did a build of Carbon (and a few of CM11, previously) for our Photons.
This is an odexed ("user", not "userdbg") build, running on the cm-12.1 kernel branch and using the latest available f2fs_tools. It also features a modified init which can use either f2fs or ext4 for /cache and /data - so switching to f2fs is highly recommended, but not mandatory. Superuser is included.
This is esentially for those who switched to CM12 just for f2fs; it's miles faster than cm12, and a bit more responsive that the old official cm11 nightlies.
A word of warning. TWRP's "change filesystem" function formats the partition (PhilZ does too, but at least it makes that explicit).
So what you want to do when switching from an ext4 ROM is,
before you begin: copy everything in the internal sdcard somewhere on the external sdcard; this is needed, since the "internal sdcard" is actually a folder in /data;
in TWRP, begin by creating a backup of /data (that saves everything except the "internal sdcard" and /cache - that's why you need step #1);
do the FS change for both /data and /cache
restore the /data backup, on the freshly formatted /data partition; ignore the "different filesystem" warning, it's inconsequential;
install the ROM;
once you booted the phone, copy back the old contents of the internal sdcard
You only need to do this when you change filesystems, which will be exactly once if you like my ROMs And obviously, if you don't, you have to use the exact same procedure before flashing an ext4 ROM, if you don't want to lose data.
Though, in all fairness, I'd recommend flashing this cleanly - unless you're upgrading from an ext4 Carbon build.
A note on the radio
I have included a tool called radio-tool (of my own design) that allows people to enable/disable the US GSM lock and individual network bands;
if you're having the SIM mod, and are from, or have business in, the US, you can use it to kill the CDMA and Sprint LTE bands altogether, as well as to enable US GSM bands and disable the US GSM lock;
the source code is here
Use (as superuser)
Code:
radio-tool [dbg] [{+|-}opt [...]]
where opt is one of
uslock - US GSM lockout
cdma - CDMA bands (CDMA800 / CDMA1800 / CDMA2000 1xEV-DO)
usgsm - US GSM/HSPA bands (GSM850, GSM1900, WCDMA850, WCDMA1900)
eugsm - EU GSM/HSPA bands (GSM900, GSM1800, WCDMA900, WCDMA2100)
sprlte - Sprint LTE (LTE25, 1900)
vzwlte - Verizon LTE (LTE13, 700)
Download:
ROM: CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960.zip
Recoveries: TWRP-2.8.6.0-20150526-f2fs-moto_msm8960_jbbl-xt897.img, PhilZ-6.59.0-20150520-crkk_f2fs-moto_msm8960_jbbl-xt897.
You do not need to use a su app with this; but if you want to, please use the latest SuperSU. Attempting to use a different, or older, su app could result in no radio.
Changes from stock Carbon:
alternative mount points support - this enables the ROM to work with either f2fs or ext4 for /data and /cache
tuned mount settings - kickass speed with both ext4 and f2fs
256MB of lz4-compressed swap space (zram0)
built on gcc-4.8-sabermod
build.prop tweaks - this defaults to GSM/WCDMA - plus a few radio and network tweaks;
added a few goodies that are present in CM builds (Term, Apollo, Calendar, CMWallpapers, VideoEditor, plus the cmdline utils);
removed the stats and the update apps (for obvious reasons)
added Romanian (programmers) keyboard support in Asanti Keypad
built with: twrp 2.8.6.0, cm12.1 kernel, cm12.1 f2fs-tools, cm12.1 e2fsprogs, cm12.1 exfat, cm12.1 fuse.
(this will allow me to pick up any improvements in kernel, file systems, and recovery, with great ease )
Quirks:
MTP doesn't start by default in TWRP, despite the fact that it claims to be enabled; disable and re-enable MTP, and it will work
in PhilZ' mount menu, entries for cache and data are duplicated; this is cosmetic - mounting and umounting works just fine, regarless which of the two entries for each partition you choose
.
Older, CM11 vanilla builds:
Download:
cm-11-20150427-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip - repo syncs, builds with TWRP, uses branch cm-12.1 of the kernel, uses latest available f2fs-tools
Use latest SuperSU with any of the CM ROMs - older, or different, su apps might make the radio not work.
NOTE. These ROMs are actually moto_msm8960_jbbl, so they should work on all devices for which official moto_msm8960_jbbl builds did, as long as they're still on the JB bootloader (jbbl) and you have a device-specific recovery that supports f2fs. A suitable PhilZ touch for non-xt897's can be found on the AtrixHD thread, courtesy of @palmbeach05, or you could use PhilZ-6.59.0-20150506-crkk_f2fs-moto_msm8960_jbbl-mb866 (note, despite the -mb866 suffix, it should work on any moto_msm8960_jbbl device except xt897).
The current repo is available here. To use,
repo init -u https://github.com/mionica/android.git -b cr_kk_gcc-4.8
repo sync
. build/envsetup.sh
breakfast carbon_moto_msm8960_jbbl
edit the .repo/local_manifests/roomservice.xml, changing the device project for android_device_motorola_moto_msm8960_jbbl to
Code:
<project path="android" name="mionica/android_device_motorola_moto_msm8960_jbbl" remote="mionica" revision="cr_kk_xt897" />
repo sync again
finally, (cd vendor/carbon && ./get-prebuilts).
After you do that, you're good to go - (optional) configure ccache (if it's your first build), (optional) enable ccache, choosecombo, then mka carbon 2>&1 | tee BUILD.LOG.
If you're not sure how to do any of these, either just use the provided ROM, or search on youtube for "building CyanogenMod" - that should help, I know it helped me Anyway, this thread is not the right place for learning how to build Android.
Mirrored for archival purposes.
This server WILL BE SLOW. You've been warned.
http://lionspaws.net/cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl/
98e652a97965ba5d88cb9068fe7d4dbe *cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
Using it for the last few days, seems good so far. Thanks
taking a break
Quick one. I'll take a break from this for now - my little sister's phone broke down, so she got my Photon. I just ordered one from the States today, but between that arriving and cornholiogsm doing the SIM mod, it might take a while (US to Ireland to Czech Republic to Ireland - and Tomas is pretty busy in my experience).
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Wait what wiki told you to use CWM for xt926!? CM's wiki?
enigma9o7 said:
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Click to expand...
Click to collapse
I agree with @arrrghhh you should use what your device maintainers recommend you use. I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section. Odexed is like what you get from the manufacturer. It has .apk and odex files in it. odex assist the apk files. 6.0.4.4 is outdated, as 6.0.5.1 is the most recent. The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well. Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore. Lollipop is able to be used on your device, as it currently has official builds. 5.0 had issues, 5.1 just got its official release yesterday. As far as unofficial builds go, I refer you to epinter and krystianp who both took an older device and provided unofficial updates that were very stable, despite the neverending work on a custom kernel. Furthermore, you can go talk to Quarx about unofficial builds, since his builds has been running the Defy for years. So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item. Battery life will always be an issue if you have a bad setup (wifi and bt on all the time, max bright screen, hrs of listening to music or streaming, etc.)
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
mionica said:
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
Click to expand...
Click to collapse
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Click to expand...
Click to collapse
Mmm will have to check. For me it's working in the EU using GSM/HSPA on the xt897 with the SIM mod.
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Another possibility is that it wouldn't work because of SElinux mismatches between kernel and userland. The following has to be in the fstab:
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,noatime,nodiratime,barrier=1,[b]context=u:object_r:radio_efs_file:s0[/b] wait,check
If it doesn't, on the xt897 you get no WiFi, but I expect results might vary by device
All I'm saying is, it might or might not be a kernel config, would have to check when I get to my PC.
mionica said:
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Click to expand...
Click to collapse
I reviewed the entire changelog from cm-11.0 to HEAD, and couldn't find anything that looked even remotely radio-related, so I reckon it's most likely the SElinux thing. And now that I built a TWRP that has a chance of running on AHD, I guess you could tell me whether that's the case
arrrghhh said:
Wait what wiki told you to use CWM for xt926!? CM's wiki?
Click to expand...
Click to collapse
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
palmbeach05 said:
I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section
....
The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well.
...
Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore.
...
So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item.
Click to expand...
Click to collapse
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
enigma9o7 said:
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
Click to expand...
Click to collapse
Yes, you can dirty flash this ontop of an existing CM11 after switching /data and /cache from ext4 to f2fs. Gapps will be fine since they install on the /system partition.
Sent from my ATRIX HD using XDA Free mobile app
Switched to Carbon, but preserved most of the goodies from CM; links in the first post.
Also added a note on how to hack your radio to disable CDMA/LTE - so you could go with this phone in the US and never register on Sprint's network (unless they have a GSM/WCDMA network in place too, which should be fine).
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
enigma9o7 said:
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
Click to expand...
Click to collapse
There should be an option to wipe things, go there
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There should be an option to wipe things, go there
Click to expand...
Click to collapse
Thanks, found it.
And now I'm stuck. But I bet it's an easy solution.
I changed filesystems, restored data & cache, installed cm (04/27), installed superuser (wasnt sure if needed, but figured it couldnt hurt), and I booted.
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
I thought maybe I'd try command line, but I'm no expert there... I su'd and tried similar things as in EX but similar results.
I thought I'd try to copy it back with TWRPs file manager, but I couldn't figure out where to put it, there was no /storage directory, so I tried putting it in / and that started copying for a while but before it was done it rebooted and just hung at the TeamWin screen until I powered off...
So yeah. Dunno how to restore sdcard0. Help please....
edit: maybe superuser doesn't work? I tried to use default "file manager" and it wont let me switch to root mode. Then I noticed that while trying ES File Manager again I didnt see the popup about "root granted" or something like that that I normally see. But superuser is installed, its in the apps menu and runs and a quick look thru the settings seems okay to me, but I don't recall ever setting anything before.
edit2: I'm giving up and going to try to go back to last cm11 nightly and hope my phone starts working again. I tried reflashing multiple times, eventually tried supersu instead of superuser and that worked to get root explorer working, but I still couldn't copy over sdcard0 using ES anyway, but using default filemanager I could start (although I hate that filemanager cuz I dont know how to change directories, usually have to tap about 15 times before it opens a folder), but it would always start then reboot before it finished. So I still dunno how to copy that back.
enigma9o7 said:
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
Click to expand...
Click to collapse
Superuser is probably not a smart choice on KK. Use SuperSU instead.
The very first boot is somehow handled differently - I discovered this when I worked on integrating SuperSU into a catch-all zip of mine (alongside Windows Mobile ringtones, Midnight Commander, patched hosts, and a few other goodies). I got no radio with my package, but if I flased SuperSU instead, it worked.
It took me a coupe of tries to find the culprit - a flag file in /etc that SuperSU created after the first boot (and I attempted to create that from my zip). Made my zip not create that, and bang! everything worked just fine. Btw, removing that file after the first boot had no effect, the phone'd be screwed until you wiped /data.
Now, the fact that SuperSU handles the first boot differently kinda makes me think that older su's might very well not work (properly) on KK - and what you're reporting seems to confirm that.
I would strongly suggest going Carbon instead; that includes a working su. It's essentially CM with a different boot logo and a good few extra customization options (which you can safely ignore if you're not into that sort of thing).
So if you didn't go back yet, try either
flashing carbon and being done with it, everything will work;
flash the cm rom alongside supersu, not any other root app,
Either way, root will work, phone will work, and you'll be able to copy stuff around to your heart's desire.
As for a FM, I strongly suggest an app called Total Commander. The UI is atrocious as of late (the author is obviously better at coding than designing icons ), but it' probably the most complete FM solution for Android, bar none. And it's free, without adds; wait til you try it in landscape
I'm sorry for you inconvenience, but I also somehow feel it's earned - the OP said SuperSU back before Carbon replaced CM; because that's what I was using, and it worked for me - no guarantees if you went your own way. I've re-added the limitation and made it bold+orange in the CM part of the post (Carbon has its own, fully working, su).
Added the 2015.05.03 build of Carbon; links to 2015.04.30 removed.
At this stage, CM users should have everything they liked about CM, already compiled in (except for WhisperPush, the point of which I don't quite see).
Changelog from 2015.04.30:
added Calendar (!!!) - why on earth would the Carbon guys build an ROM without this?!
built on gcc-4.8.x-sabermod-20150429
added CMWallpapers, Video Editor
added the previously-missed vim, unrar, zip and gdbserver
synced with upstream; in particular, there was a noteworthy GPU memory allocation improvement in the kernel
Todo:
add an app for messing with the NV settings (enable/disable bands, enable/disable US GSM lockdown)
enable zram.
Added the 2015.05.05 build of Carbon; links to 2015.05.03/04 removed.
Changelog from 2015.05.04:
set default governor to msm-dcvs - better out-of-box performance
imported the cm-12.1 init support (including swap enabling)
Changelog from 2015.05.03:
support for fstab alternatives, cm12-style (my own code in fs_mgr); now you can use the ROM with either f2fs or ext4 for /cache and /data
massively improved FS performance for both ext4 and f2fs - tuned the fstab settings for best performance;
added radio-tool to enable/disable US GSM lock and groups of radio bands (CDMAs, US GSM/HSPA, EU GSM/HSPA, Sprint LTE, Verizon LTE) - see spoiler in first post
Todo:
figure out why swapping doesn't want to start, despite the device being there and mkswap succeeding (error -16).
Updating the recovery to a 20150505 build is highly recommended.
Q&A for CyanogenMod 12.1 for Photon Q
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CyanogenMod 12.1 for Photon Q. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Boot stuck and Bootlooping -fix
Sweet merciful crap. I just got through a 5 hour fight with my Photon Q trying to bring it up to cm-12.1.
In a nutshell, I figured the advise not to dirty flash 12.1 on top of 12 was defunct once it started showing up in the nightlies. Be warned - it is not. Your experience may mirror mine and you'll get stuck at boot.
What's worse is that when I went into TWRP-2.8.6.0 recovery and attempted to do a wipe of data/cache, it started making a mess of my partitions. Not able to mount /data, not able to mount /cache... No matter what order, or selection in the Advanced wipe, it seemed to be making more and more of a brick out of my device as I tried.
I followed some advise I found that suggested newer TWRP versions had problems with wiping on the Photon Q, and to try CWM recovery or stock recovery. Tried CWM to wipe, no dice, similar problems. Spent a good deal of time trying to find the stock recovery somewhere; I think I reached the end of the internet and it's not there.
Then I started trying older versions of TWRP found here:
http://techerrata.com/browse/twrp2/asanti
Then things got really bad. Every one of the ones I tried with "asanti_c" in the name bootlooped (tried about 5 of them). The battery started getting low and I couldn't flash the recovery any more from the bootloader, and it would seem the phone won't take a charge while in bootloader mode. So I had to let it bootloop while it charged, which of course took a long time because all the bootlooping was keeping the battery taxed.
Finally I flashed this one, 'cause I figured my phone was a brick anyway:
openrecovery-twrp-2.2.2.2-asanti.img
It started up. It was also happy to restore/wipe my data, cache, and system partitions. Back to the bootloader, flash back to TWRP 2.8.6.0, install the nightly cm-12.1 and appropriate gapps. This time no errors about partitions, everything seemed clean. Sure enough, boot it up normally, wait about 8 minutes on the flashy Android face, and it does the fold/drop thing and proceeds with the initial boot sequence.
So be careful everyone! I hope at least someone comes here and finds this if they've "Bricked" their photon Q, and that it saves them from the depths of despair that I found myself in! If only I'd have seen this trick in this thread, I would have been back up and running in 30 minutes or less!
Best wishes with your upgrades/recovery!
kabaldan said:
For now, just a test build before the official cm-12.1 nightlies for Photon Q will be enabled.
Download link (cm-12.1-20150405-UNOFFICIAL-xt897): http://d-h.st/2ul
Gapps (use gapps-lpmr1-...): http://d-h.st/users/dhacker29/?fld_id=27426#files
TWRP 2.8.6.0 recovery for xt897: http://d-h.st/lEHx
(feel free to provide mirrors on other/better file hosts)
Device specific source repos:
motorola/xt897: https://github.com/CyanogenMod/android_device_motorola_xt897/tree/cm-12.1
motorola/msm8960_jbbl-common: https://github.com/CyanogenMod/android_device_motorola_msm8960_jbbl-common/tree/cm-12.1
motorola/qcom-common: https://github.com/CyanogenMod/android_device_motorola_qcom-common/tree/cm-12.1
kernel: https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common/tree/cm-12.1
Please note:
Since CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead. Use xt897 specific builds when you go beyond CM11.
GSM users (SIM card mod):
Please switch the Settings>Mobile networks>Preferred network type to 'GSM/WCDMA auto' or 'GSM/WCDMA preferred' from 'Global' for correct modem functionality on GSM networks.
What's new in cm-12.1 for xt897:
Lollipop turned out to be very RAM demanding. 1GB RAM devices seem to be below the limit of what lollipop actually needs.
To overcome this issue, 256MB of RAM has been dedicated to zram (compressed swap living in RAM). Zram can give us a bit more of effectively usable RAM space.
To speed-up the zram operations, kernel has been updated to the latest zram code with support for the fast lz4 compression.
Another new kernel addition is cpu-boost driver that can boost cpu frequency e.g. when input events are happening (touch screen interaction) regardless of cpu governor in use.
Known issues:
- USB audio output (analogue) via USB>audio Y-cable (Motorola Car Dock/EMU audio) is not working correctly yet
- USB audio DACs/sound cards connected as USB OTG peripheral do not work correctly yet
Click to expand...
Click to collapse
I don't know that my posts are even going to be seen because I haven't made 10+ posts here yet and therefore it keeps throwing me to this Q&A thread. Regardless, I will try.
I'm now running the 12.1 4-21 nightly.
After my first initial struggle to get 12.1 installed/running, I found that I didn't actually have a data connection once I got out of wifi range.
Took many trials and lots of time to figure this out. Turns out that some of the AT&T APN's are missing "hipri" which they apparently need to work. Once I added that, I got my data connection.
Now I'm have a problem reliably connecting to AT&T. This wasn't the case with 12.0 at all, connected quickly every time. After a reboot, it keeps cycling trying to connect and quickly failing. I have to fight with it in the network selection settings. Eventually it'll succeed at a manual scan where I can select AT&T, or it will succeed at an automatic selection. This seems odd because when I run an adb logcat, it does seem to be trying to connect to AT&T on its own. So whether it would eventually connect on it's own and the busy work of me fighting with the network selection settings just makes me feel better some how that I'm fixing it, I'm not sure yet.
I can also confirm that the lock page says "No Service" even when the network is connected including data.
I hope these things help someone else out and perhaps lead to a fix. Happy to try stuff out or run a trace if it would help, just let me know.
I had exactly the same issues when trying to flash CM 12.1 (Not able to mount /data, not able to mount /cache... )
Fixed this by manually formatting each partition at one time. I also changed data and cache to f2fs
No need to go with older TWRP
But I still have the connection issues exactly as you describe in your second post.
I'm running Freedompop (on top of Sprint network)
By manually formatting, what do you mean? Did you use TWRP Wipe-Advanced and just select the partitions one at a time? That wasn't working for me for some reason, it kept on messing up the partitions and failing. What version of TWRP are you using, is it the latest 2.8.6.0 or...?
You're brave to go with f2fs. Do you feel it's performing better?
Just to clarify on the network provider point - I did the simcard hack to my Photon Q, this is how I am able to run it with AT&T. Interesting that the problem I described happens with the native CDMA/Sprint network as well.
I hope we get a fix for the connectivity issue soon. I feel a little uneasy praying that the phone doesn't lose its connection or reboot for fear that I can't get it connected again in a reasonable period of time.
turbozapekanka said:
I had exactly the same issues when trying to flash CM 12.1 (Not able to mount /data, not able to mount /cache... )
Fixed this by manually formatting each partition at one time. I also changed data and cache to f2fs
No need to go with older TWRP
But I still have the connection issues exactly as you describe in your second post.
I'm running Freedompop (on top of Sprint network)
Click to expand...
Click to collapse
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
I have a feeling that your selection of f2fs for your cache and data partitions influenced your success with wiping. I attempted the same process numerous times, but without changing the partition file system, and was unable to get all the partitions to a proper state with TWRP 2.8.6.0.
I didn't see anything in the changelog (http://www.cmxlog.com/12.1/xt897/) that would suggest a fix was included for the connectivity problem in either the 4/22 or 4/23 nightly so I haven't tried updating just yet, preferring instead to try to prolong my existing connection until there is more hope that when I reboot I will be able to connect without struggling with it.
It's too bad we're not able to participate in the main thread as there is a more active discussion going on there. I suspect this is just a parking lot. Perhaps if we keep posting our ongoing findings here for a couple of more days we'll get over 10 posts and be able to generate some more activity on these issues.
turbozapekanka said:
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
Click to expand...
Click to collapse
timekiller_9 said:
It's too bad we're not able to participate in the main thread as there is a more active discussion going on there. I suspect this is just a parking lot. Perhaps if we keep posting our ongoing findings here for a couple of more days we'll get over 10 posts and be able to generate some more activity on these issues.
Click to expand...
Click to collapse
The Q&A thread is no different from the other thread. I don't think the maintainer cares if you post questions in the dev thread, but some maintainers can get annoyed by that. That's the whole point of the Q&A thread, to ask questions... The dev thread is "supposed" to be for development discussion only, although that seems to rarely happen.
Thanks for the tips arrrghhh.
Other than to confirm that others have similar issues and it's not a matter of something I'm doing wrong, I don't really have any questions. There are a couple of pretty serious bugs in CM 12.1 for the Photon Q. I would like to participate in the development of fixes in so much as I can. I'm not likely to be able to pinpoint where in the code things are broken as that would take some pretty serious time familiarizing myself with the layout. That said, I am a systems engineer by trade and feel comfortable running all sorts of tests/traces.
arrrghhh said:
The Q&A thread is no different from the other thread. I don't think the maintainer cares if you post questions in the dev thread, but some maintainers can get annoyed by that. That's the whole point of the Q&A thread, to ask questions... The dev thread is "supposed" to be for development discussion only, although that seems to rarely happen.
Click to expand...
Click to collapse
Hey turbozapekanka,
Check out my latest response in the main (albeit meant for development, it's where the real action is) thread:
http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781/page5
I'm not sure if it'll work for CDMA but you may wish to try it. It would be good data to know if your problem lies elsewhere in any case.
Good luck!
turbozapekanka said:
Yes, I used 2.8.6.0
I don't remember exact steps I performed, but the idea is to get rid of that "Not able to mount" errors.
I also performed Wipe->Format Data while trying to get rid of that errors. Not sure if it was necessary.
So after several unsuccessful attempts I finally I decided to change /cache to f2fs, and this is where I noticed, that the error is gone! So I just repeat the same steps (Wipe->Advanced Wipe) for all partitions (changing to f2fs for /cache and /data partitions only)
The key was to select only one partition at a time! when I checked several, I get "Not able to mount" error for some partitions. I think it is TWRP bug.
And just an hour ago I flashed latest nightly CM12.1 build (4-22) and it looks like the Network connectivity issue is also solved! (UPDATE: NO IT IS NOT, still loosing connectivity periodically, and Exclamation sign appears)
I did not notice any change to f2fs but I have nothing to compare with, I switched to CM just after I received the phone. (I bought it from Freedompop for $25)
Click to expand...
Click to collapse
wifi
Has anybody problems with Wifi?
i cant turn it on. Its off in the extended Settings is the Message "Wifi ist activating" but nothing happens
Do you guys have any idea on why we got 'no new update' message from settings/update, even though we have an obvious nightly update? http://www.cmxlog.com/12.1/xt897/
palmwangja said:
Do you guys have any idea on why we got 'no new update' message from settings/update, even though we have an obvious nightly update? http://www.cmxlog.com/12.1/xt897/
Click to expand...
Click to collapse
It's a server side issue affecting all cm12.1 devices, should be fixed soon.
Has anyone's 'long press volume keys for playback control' stopped working? When my screen is off the volume keys don't seek tracks like they did in a previous nightly.
Also ,does smart lock work for you guys? I can see the option but can't seem to get it to recognise NFC or my face.
hi.
Will cm12.1 support all f2fs file? It is the system / data / cache all formats into f2fs, thanks.
hhvstp said:
Will cm12.1 support all f2fs file? It is the system / data / cache all formats into f2fs, thanks.
Click to expand...
Click to collapse
CM12 supports it, I would imagine 12.1 does as well...
Heck, there is a CM11 build floating around with support for it.
12.1 Sprint CDMA access
Since I haven't posted much, I could not reply to the thread, but here's what I did to get 3G data back.
Installed the 05/01/2015 12.1 build.
Edited the build.prop file
changed ro.carrier=
to
ro.carrier=Sprint
rebooted - and I now have data.......
Not sure "why" that worked, but It hasn't up until I made that change....
apns-conf.xml issues
Compared to CM11, several of the entries in the /system/etc/apns-conf.xml file from CM12.1 are missing the "default" type. This makes it impossible to actually select the APN settings for Ting, Credo and Sprint MMS. For instance, I'm on Ting and changing:
type="mms"
to:
type="default,mms"
And then deleting /data/data/com.android.providers.telephony/databases/telephony.db and rebooting made it possible for me to select TIng. Previously there was no radio button next to the entry.
I still have the problem where the "Access Point Names" menu usually says "Access Point Name settings are not available for this user" most of the time but now when I *am* able to enter that menu I can at least select the right APN setting.
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
GreeGreeCreedle said:
Since I haven't posted much, I could not reply to the thread, but here's what I did to get 3G data back.
Installed the 05/01/2015 12.1 build.
Edited the build.prop file
changed ro.carrier=
to
ro.carrier=Sprint
rebooted - and I now have data.......
Not sure "why" that worked, but It hasn't up until I made that change....
Click to expand...
Click to collapse
Nice catch. It looks like ro.boot.carrier is set correctly but for some reason ro.carrier is unknown.
hi.
CM12.1 experience to perform part of the game will be LAG, turn off the sound, then you can ease, what is the problem?
millertoo said:
Compared to CM11, several of the entries in the /system/etc/apns-conf.xml file from CM12.1 are missing the "default" type. This makes it impossible to actually select the APN settings for Ting, Credo and Sprint MMS. For instance, I'm on Ting and changing:
type="mms"
to:
type="default,mms"
And then deleting /data/data/com.android.providers.telephony/databases/telephony.db and rebooting made it possible for me to select TIng. Previously there was no radio button next to the entry.
I still have the problem where the "Access Point Names" menu usually says "Access Point Name settings are not available for this user" most of the time but now when I *am* able to enter that menu I can at least select the right APN setting.
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
Nice catch. It looks like ro.boot.carrier is set correctly but for some reason ro.carrier is unknown.
Click to expand...
Click to collapse
I don't have this device but hopefully this post helps those with apn issues. If I toggled network mode to lte only, the apn listings would actually show.
http://forum.xda-developers.com/showthread.php?p=61070073