Related
What are nightly builds?
Nightly builds are automated builds from latest cyanogenmod sources. they are not tested in deepth like RC's or stable versions. In most cases they work without any issues. Thats because all patches get reviewed before they are merged into sources - this way, merging of bad code doesnt happen very often.
Since vega does not have official nightly status yet, i do semi-official builds for you on a semi regular basis. We will get official nightlies, once bluetooth is working - but that is a pretty complicated issue.
Vendor vega
The vendor vega is currently for Advent Vega and PoV Mobii devices. There might be more added later on.
Official nightly mirror
http://mirror.teamdouche.net/?device=vega
Update 31.05.2011
buildbot had a hdd crash, and it can take some more days until nightlies are back online. that long, i might post semi-official nightlies here.
mirror1: cm_vega_full_teamdesire-20110531-1412.zip size: 66M (68406215 bytes)
mirror2: cm_vega_full_teamdesire-20110531-1412.zip md5sum: 3b8bb1c21cb7c992927566a609a8c21d
Nightly changelog
http://cm-nightlies.appspot.com/?device=vega
Nightly install instruction
Coming from another rom?
Do a full wipe in clockwork mod recovery
Install latest nightly build from here
Flash latest gapps from here
reboot
do the first-time-run-setup wizard
if you dont use gsm/phone, reboot to recovery and flash attached vega-phone-removal.zip - saves battery
Upgrading from older nightly?
Just flash latest rom from here in clockworkmod recovery
No need to wipe or flash gapps again, if you done on first install
In rare cases you will encounter bugs, noone else encounters - wipe then and do a fresh install
In at least 99% no wipe needed - there are known people not having wiped for at least half a year
Doing a nandroid backup before upgrading is always a wise idea, in case something goes wrong
if you dont use gsm/phone, flash attached vega-phone-removal.zip - saves battery
reboot to your updated rom and enjoy
Overclocking instructions
use settings->cm settings->preformance->cpu settings to switch frequencies. optionally use setCPU and similar tools.
USB Host mode instruction
to enable usb host mode for keyboard, mouse and other support, power device off. power it back on. once the screen gets lit, press and hold back key until device is booted (you see the homescreen or lockscreen). now you can connect various usb devices.
clockworkmod 3 for vega
with nightly 61 and later, use rom manager to flash latest stable recovery.
List of known bugs
This is a list of cm7 bugs specific to vega - i wont cover cm7 general bugs here, since they are covered on other places. Feel free to discuss them here, thats what this thread is for.
no legacy a2sd yet - working on it
power->reboot->recovery doesnt work and power->reboot->bootloader should be removed
Removed Themes
To save space, we had to remove the two cm included themes. If you want them, just download them here and install like any other app.
mirror1: Cyanbread.apk size: 3.6M (3748359 bytes)
mirror2: Cyanbread.apk md5sum: a6963767a063a888536bc470569dcb54
mirror1: Androidian.apk size: 4.0M (4192665 bytes)
mirror2: Androidian.apk md5sum: 6657fa2e31c5a86ec5bdb03ac6e72a65
Removed Wallpapers
To save space, we also removed CMWallpapers app. To reinstall them on data partition, download this app and install like any other app.
mirror1: CMWallpapers.apk size: 6.0M (6248124 bytes)
mirror2: CMWallpapers.apk md5sum: b0d02c6eb75e39b7aa0b77e5cee20ace
This seems really sweet!
I have some questions:
1) Can the soft buttons be placed further away from each other? Unlike the Nook Color, the Advent Vega has a screen with touch registering issues and it's probably easy to misclick buttons if they're in the normal disposition.
2) What's the "encore" release for?
Danke für die Anstrengung!
Hi i tried to install CM7 before the version b2 and now this one and both stuck at the boot screen with android and the arrow makes circles. Do i miss something? i tried full wipe + format sd but still nothing. I must wait longer than 20 min?
Any suggestions
Thank you
dkampo said:
Hi i tried to install CM7 before the version b2 and now this one and both stuck at the boot screen with android and the arrow makes circles. Do i miss something? i tried full wipe + format sd but still nothing. I must wait longer than 20 min?
Any suggestions
Thank you
Click to expand...
Click to collapse
Same here. Full wipe of data, cache, dalvik cache.
Waited 40 minutes but system does not boot. Only arrow making circles. Restart did not help either.
Welcome to Vega Murdock, remember you from my DesireHd Nightly days. Whats up with these two zips? One is the rom and one addons?
Logseman said:
This seems really sweet!
I have some questions:
1) Can the soft buttons be placed further away from each other? Unlike the Nook Color, the Advent Vega has a screen with touch registering issues and it's probably easy to misclick buttons if they're in the normal disposition.
2) What's the "encore" release for?
Danke für die Anstrengung!
Click to expand...
Click to collapse
with the big buttons (much bigger as on default cm7), i dont have any issue to hit what i want. dont want it even bigger.
BeeGee_Tokyo said:
Same here. Full wipe of data, cache, dalvik cache.
Waited 40 minutes but system does not boot. Only arrow making circles. Restart did not help either.
Click to expand...
Click to collapse
zero idea. works here. gotta point bumble bee to this. you did take the vega build and not flash the encore build?
nickwarn said:
Welcome to Vega Murdock, remember you from my DesireHd Nightly days. Whats up with these two zips? One is the rom and one addons?
Click to expand...
Click to collapse
still having and hugging my desire hd
encore = nook color
vega = vega + mobii
i just copied that post from the nook color thread where this is all discussed.
please discuss overall issues (non-vega-related) on nook color thread
mad-murdock said:
...
zero idea. works here. gotta point bumble bee to this. you did take the vega build and not flash the encore build?
...
Click to expand...
Click to collapse
Yes, I checked the file on my SDcard its the Vega file. I checked as well the build.prop and updater-script, it says definitely Vega.
When I am back home tonight I will reflash stock ROM to recover and retry flashing your ROM.
The Vega rom boots and runs nice. Its very odd having statusbar going from bottom to top but very cool. Nice work. Now back to testing
Just one question, why did you post Nook Colour rom here? Encore is Nook, right?
Maybe we could have multi language, would be nice
Edit. You answered before i posted, im to slow
mad-murdock said:
...
zero idea. works here. gotta point bumble bee to this. you did take the vega build and not flash the encore build?
...
Click to expand...
Click to collapse
nickwarn said:
The Vega rom boots and runs nice. Its very odd having statusbar going from bottom to top but very cool. Nice work. Now back to testing
Just one question, why did you post Nook Colour rom here? Encore is Nook, right?
Maybe we could have multi language, would be nice
Edit. You answered before i posted, im to slow
Click to expand...
Click to collapse
Does the ROM require EXT2/3/4 on the SD card? I don't have it and this is the only thing I can think about at the moment which might be different.
The ROM comes with its own kernel? I had before installed [KERNEL] Buzz Vega | .32.35 | CIFS | TUN | EXT4 | SLAB | NOOP | WiFi | NTFS | HOST/SLAVE | 0.7, Updated 25/03/11 from buzzing bee. But that should have been overwritten when I flash your ROM.
BeeGee_Tokyo said:
Does the ROM require EXT2/3/4 on the SD card? I don't have it and this is the only thing I can think about at the moment which might be different.
The ROM comes with its own kernel? I had before installed [KERNEL] Buzz Vega | .32.35 | CIFS | TUN | EXT4 | SLAB | NOOP | WiFi | NTFS | HOST/SLAVE | 0.7, Updated 25/03/11 from buzzing bee. But that should have been overwritten when I flash your ROM.
Click to expand...
Click to collapse
I came from CorvusVega rom but as long as you wipe everything cache,dalvik,system,data,boot, it shouldnt be a problem. I hate that we cant get in to recovery from off position. If thats possible to do with some hack that should be the next big thing
Hello,
when i try to download your ROM i became a error 404 file not found.
new build, new features, new links - updated first post.
and yes, its buzz kernel - no idea if he made slight modifications, but its the same guy responsible for buzz kernel and vega cm7 target.
rbensch said:
Hello,
when i try to download your ROM i became a error 404 file not found.
Click to expand...
Click to collapse
deleted the old files BEFORE uploading... shouldnt do that next time get new build from first post
mad-murdock said:
new build, new features, new links - updated first post.
and yes, its buzz kernel - no idea if he made slight modifications, but its the same guy responsible for buzz kernel and vega cm7 target.
Click to expand...
Click to collapse
Does this means we can do the switch to host mode by the back button trick?
Can anyone try?
Thanks!
Got the ROM finally working, maybe during 1st flash something went wrong.
Its still the old version, new version is still downloading (terrible slow connection here in China).
I installed it on a Viewsonic Viewpad 10s, which is the Vega but with build in 3G card. Unfortunately the card is not working. when I go to the settings -> Wireless & network settings -> Mobile networks, I can enable data communication, but he does not find any provider and the signal in the task bar shows no signal.
In the stock 1.09 ROM its working without any problems.
Will download latest version, test again and report here.
Harplo said:
Does this means we can do the switch to host mode by the back button trick?
Can anyone try?
Thanks!
Click to expand...
Click to collapse
should work. feel free to flash another kernel over this. changes are not kernel related.
current build got some minor bugs which I fix when I get back tonight. mainly the new soft button. check nook color thread for details
Morsed by hitting a plastic pipe with my Desire HD. Excuse typos.
I believe this rom will have the same kernel as Bumble-Bee's CM7 build, so no host and no a2sd!
However I have asked BB to make a new kernel so hopefully he will do this asap.
Great Rom!! Thanks for sharing your work & time with us.
Thinks I like.
CM7 Booting image
CM7 look & tweaks
CM7 Table tweaks, especially bottom bar.
Host mode working. N1!
Don't like:
The bar buttons. Really don't like them.Any change of changing them? I know it's a silly thing but them seem huge to me.
Bugs I found:
Default Keyboard going on and off every time I press a key. Annoying.
Wifi disconnecting randomly and not reconnecting in a while.
Touch Screen not responding until I change orientation. Weird.
Thanks!
Harplo said:
Great Rom!! Thanks for sharing your work & time with us.
Thinks I like.
CM7 Booting image
CM7 look & tweaks
CM7 Table tweaks, especially bottom bar.
Host mode working. N1!
Don't like:
The bar buttons. Really don't like them.Any change of changing them? I know it's a silly thing but them seem huge to me.
Bugs I found:
Default Keyboard going on and off every time I press a key. Annoying.
Wifi disconnecting randomly and not reconnecting in a while.
Touch Screen not responding until I change orientation. Weird.
Thanks!
Click to expand...
Click to collapse
We are all diffrent i like the soft buttons. about keyboard going on and off try moving soft buttons to right side and remove quick notification button. That fixed it for me. The buttons can be changed back later than it will work as it should. But i think theres some strange behavior from quick notification button, for example when pressing it it shuts down the screen it dont answer to any touches only on soft buttons, so i have to press the statusbar up and from there press the back button then it wakes up. I dont know, maybe its supposed to be like that.
Very nice ROM. Flashed it last night and seems to work nice. The buttons work great.
However i have a performance issue. A couple of minutes it works very smooth and then it freezes for a while and then continues. Still have the problem after a couple of reboots and after using it for a few hours.
second i installed the gapps that are available for CM7 (the metapackage wich should also work for tegra based devices). I can download apps, but then i cannot see in the market as downloaded.
I came from Modaco r8 and did a full wipe before installing.
Keep up the good work.
EDIT: When the screen freezes only the statusbar and the buttons are responding on touches. The rest of the screen does not respond. The screen will respond again when i change the orientation of the screen (i.e. from landscape to portrait and back to landscape).
Sent from my HTC Vision using XDA App
Thomas.Raines and Team Fah-Q! presents
source code Lightning_Zap_Powered CM-10 Unoffical for SGH I577
https://github.com/TeamFahQ/msm8660-common_lz_kernel.git
https://github.com/TeamFahQ/msm8660-common_LZkernel_tools.git (scripts and zipalign binary)
A BIG THANK-YOU goes out to DR4ASTIC for the many months of work he put into porting cm-10 and our kernel so if you see him hit his thanks button, and if you have the means help get him some soap..lol Also thanks to Thomas Raines for bringing us LZ. the site will be under construction for a while as I have had a few requests for links to the various guides and tuts I've used to learn how to build...mind you it takes alot of time and research but to me its deffenitly worth it...Here is a thread for the blaze TFQ tweaks and install instructions for the LZ kernel. also features from this thread http://forum.xda-developers.com/showthread.php?t=1959657
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
TUTS
[GUIDE] PARANOIDANDROID:JB
http://forum.xda-developers.com/showthread.php?t=1863547
Project Rookie How to build ROMS
http://forum.xda-developers.com/showthread.php?t=1798056
Guide how to compile and install CM10 for i9300
http://forum.xda-developers.com/showthread.php?t=1946481
TUT Building your first kernel
http://forum.xda-developers.com/showthread.php?t=1748297
Thanks to everyone who has helped this rookie put all this together
Dr4stic, thomas.raines, racing19969, and many others who i dont remember thanks everyone.
Warning: if you rooted your phone using the blaze recovery you need to use Odin and push our custom recovery tar file located below. make sure to uncheck repartion. if you push this with the blaze recovery it could cause issue's.
ok so d4astic cooked us up a CM 10 mod unofficial and our very own CMW recovery here are the links, and we need someone who can grab this and take over because d4astic doesnt have this phone and has a nightly on the blaze, so here you go everyone. I've taken over running the builds so....
,,,let the fun begin....
One more thing make sure you push the recovery first because the blaze one won't work with this rom
WARNING: if you brick your phone its not my fault i did this and it worked out fine just so you know
Also find this at this thread
http://forum.xda-developers.com/showthread.php?t=1730518
New Govs and U/V control brought to us by Thomas Raines and j3r3goss who dedicated his entire christmas break getting this to work for our phone. Also we know that at this time you cant control voltage with 3 rd party controls we are working on this so no need to tell us thanks
recovery cwm
cwm-6.0.1.4-exhilarate.tar - 6.92 MB
md5sum: f4f327659c35942ac8b5d08940b27efc
Cwm flash able zip
http://d-h.st/0KP
twrp 2.6
TWRP-2.6-Recovery-I577.zip - 7.67 MB
Official cm-10.2 thread
http://forum.xda-developers.com/showthread.php?p=45140599
official carbon rom by somcom
http://forum.xda-developers.com/showthread.php?t=2458690
official pacman by ink slinger
http://forum.xda-developers.com/showthread.php?t=2445143
4.3 is here hey guys so we skipped 4.2 and jumped right up to 4.3 due to efforts of many people
credits
j3r3goss
dr4stic
uberpeaguin
thomas raines
racing
somcom
teamchopsticks
meticulous(wifi-fix and several other things )
and of course yours truley
i know this list should be bigger and if you need to be on it because i missed you pm me and i will add you
i want to offer everyone on this list my heartfelt thanks from me and the rest of the i577 and blaze community without each and everyone of you we would still be stuck on 4.1 so thanks
4.3 moretz kernel source
thanks to these fine gentlemen
Team Chopsticks
CyanogenMod
Car vs Driver
elbermu
https://bitbucket.org/carvsdriver
moretz kernel oc to 1.5 ghz
flash from recovery and wipe caches
moretz_fixed_exhilarate.zip - 5.97 MB
4.3 roms
Liquid-JB-v3.0-UNOFFICIAL-exhilarate.zip - 115.52 MB
dirty unicorns all fixes included camera, torch, light sensor
du_exhilarate_2013-09-23.zip - 167.97 MB
beanstalk all fixes
BeanStalk-4.3.08-20130924-exhilarate.zip - 174.92 MB
pa_exhilarate-3.99-20130831.zip - 150.55 MB
i left out my slim build since meticulous has that under control there is a pac build in the thread by ink search for it its in the last 20 pages or so of the thread we are oficially supported by cm and team chopsticks and working on getting our own forum but xda seems to not be listening to me so all of you raise your voices and be heard by mods and anyone else who has a say in it i hope you enjoy my work this is the culmination of several months of time and energy and believe it or not i didnt even know what linux was when i started lol enjoy
old builds
4/25/13
SlimBean
Slim-3.1.0-i577-20130426-1514-UNOFFICIAL.zip - 80.51 MB
root box
5/6/13
fixed menu button and rom control
RootBox-JB-i577-Nightly-20130506.zip - 141.89 MB
http://d-h.st/3Nw
Remember with the LZ kernel if it hangs at boot let it sit for 10 minutes reboot and enjoy...
pacman LZ UPDATED 2/8/13
http://d-h.st/Afa
1/12/13
http://d-h.st/sjj
Paranoid Android: UPDATED 2/8/13
http://d-h.st/X5B
1/9/13
http://d-h.st/3AF
check this one out guys....
LiquidSmooth UPDATED 12/14/12
LZ:http://d-h.st/4z1
http://d-h.st/bqe. No LZ: NOT UPDATED
AOKP UPDATED revamped kernel
2/8/13
http://d-h.st/UEr
01/28/13
http://d-h.st/gg8
12/18/12
http://d-h.st/Wzb
rom and md5sum: cm10 sgh i577 exhilirate zip unofficial(Powered by LightningZap Kernel)
Cm10 updated 2/8/13
http://d-h.st/2Pd
UPDATED 1/9/13
http://d-h.st/4Hi
G-apps. JB
http://goo.im/gapps/gapps-jb-20121011-signed.zip
CM 9 stable unoficial build by dr4stic (At this time CM 9 does not have the lightning zap kernel)
so below is the folder where you will find the zip file for the cm9 build, make sure you get the md5 sum and compare it,please make sure you do a factory reset and wipe the dalvic cashe also, its under advance in the recovery
Now just in case you did not read from the top and just jumped down here; please push the recovery from the link above, if you do not do this you will have issues.
Thanks dr4stic for all your hard work, I'm going to post the ICS g-apps link . I hope everyone enjoys this as much as i do... With all that said .....enjoy....
CM9 unoficial rom with new kernel(updated by j3r3goss)
http://d-h.st/lNB
ICS G-APPS
http://db.tt/65fqUOcO
Ported ROMS
these roms were ported by InkSlinger420 they are not built from source but still very stable and a good expieriance
Credits
Avatar thanks for letting us post this here
the original thread can be found here
http://forum.xda-developers.com/showthread.php?t=2142130
Avatar Port
http://www.d-h.st/B4O
LiquidSmooth
Donation link for liquid smooth
http://bit.ly/Ruy2HF
thanks to Xwolf13 and the all star team for allowing us to port their work and post it for you guys the original thread can be found here
http://forum.xda-developers.com/showthread.php?t=2284763
Rom Port
http://d-h.st/RE5
i didnt do these ports guy so look up InkSlinger420 hit his thanks button and then go to the original thread and click the thanks button on the op post
this stuff takes alot of time and effort weather its a port or built from source so show them some love
thanks for posting it here... I will test it. Also you should post Gapps link. I have it.. but others might not and may flash the wrong Gapps.
This is NOT a rant...
These are some bugs I found so far.
1. Screen Orientation (Which OP mentioned)
2. While charging if you touch the power button It will black out and Hangs up (Pull battery and restart)
3. Camera sometimes having issues. (camera not found) but most of the time works perfect.
4. Call quality Low (Like all CM builds)
Rest everything seems to be very smooth. Google Now works without any issues.
I'm just writing this for information purpose only for those who like to use this build.
Thanks a lot to dr4stic for giving us this build.
Googler_1976 said:
These are some bugs I found so far.
1. Screen Orientation (Which OP mentioned)
2. While charging if you touch the power button It will black out and Hangs up (Pull battery and restart)
3. Camera sometimes having issues. (camera not found) but most of the time works perfect.
4. Call quality Low (Like all CM builds)
Rest everything seems to be very smooth. Google Now works without any issues.
I'm just writing this for information purpose only for those who like to use this build.
Thanks a lot to dr4stic for giving us this build.
Click to expand...
Click to collapse
Guys, turn off the notifications. The touchkey driver I used is the stock samsung one which doesn't have the BLN (button lights notifications) which CM is looking for. Whenever you get a message, or email, or really anything that would trigger a blinking LED, it's gonna crash the phone cuz the driver doesn't know how to handle it.
http://forum.xda-developers.com/showpost.php?p=32548093&postcount=108
dr4stic said:
Guys, turn off the notifications. The touchkey driver I used is the stock samsung one which doesn't have the BLN (button lights notifications) which CM is looking for. Whenever you get a message, or email, or really anything that would trigger a blinking LED, it's gonna crash the phone cuz the driver doesn't know how to handle it.
http://forum.xda-developers.com/showpost.php?p=32548093&postcount=108
Click to expand...
Click to collapse
BLN was never checked at-least on my phone. But its the screen rotation issue made me rollback to Stock ICS. I know you're very busy... but if you can guide me where to look into for that issue I will. Thanks again for ur hard work.
He needs a log cat run during the screen rotation and during start up so he can see what's going on. I don't know how to do this yet I've been looking into it but don't really know where to start. Do you know how to do this
Sent from my SAMSUNG-SGH-I577 using xda premium
Another thing that would be nice, the output of dmesg.
Just a brief explanation of what these things are. Logcat is basically the general android system logs as it boots up and runs. The dmesg is the log specifically of kernel messages as it boots up. This often includes details on drivers and potential errors there. ADB = android debug bridge, a way to connect to android, push and pull files, get a shell on the system, etc...
Install ADB drivers: If you've installed the drivers necessary to use Odin with your phone, it should include Samsung's ADB drivers for the phone. So I don't think you need to worry about that.
Install ADB: Not great, but not horrible ADB install tutorial
As for the phone itself, ADB is automatically enabled within recovery. When the phone is booted up as, you know... a phone... you'll want to go into Settings -> Developer Options, find "Android Debugging" and make sure it's turned on. That will enable ADB on android.
Now, some sample ADB commands to make your lives easier...
Check to make sure ADB sees your device (you should do this whenever you connect your phone to your computer, just to make sure you won't run into any errors with the commands below):
Code:
adb devices
Grab the output of dmesg (two versions, see it or redirect to a file.. you pick):
Code:
adb shell dmesg
or
adb shell dmesg > C:\name-of-some-text-file.txt
Grab the output of logcat (two versions, see it or redirect to a file.. you pick):
Code:
adb logcat
or
adb logcat > C:\name-of-some-text-file.txt
* NOTE: This will continue to grab output until either the system reboots or you hit CTRL+C on your keyboard. If you're just looking for the most recent messages, let it run for a few seconds and then CTRL+C it out.
Get a Linux shell on the system:
Code:
adb shell
Restart local ADB server (sometimes necessary... if you KNOW your phone is connected and ADB stopped recognizing it):
Code:
adb kill-server
Thanks guys!
I began setting a dB up on my comp last night I have java installed and started on the SDK but I fell asleep will work on it some more today. Now I'm going to read the links you posted and see if my research went in the right direction. One thing I will tell you is I've been spoiled by windows. Setting this up has given me flashbacks to the days of DOS. Lol
Thanks for the info and the time to point us in the right direction.
Sent from my SAMSUNG-SGH-I577 using xda premium
ktempleton said:
I began setting a dB up on my comp last night I have java installed and started on the SDK but I fell asleep will work on it some more today. Now I'm going to read the links you posted and see if my research went in the right direction. One thing I will tell you is I've been spoiled by windows. Setting this up has given me flashbacks to the days of DOS. Lol
Thanks for the info and the time to point us in the right direction.
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
Another easy way is install Droid Explorer (http://de.codeplex.com/) Power off phone when connected. then click on the logcat console button. It will open the command window and lines keep scrolling... Don't do anything till it completely boots. then Save the file (option on cmd window).
But i think the rotation issue is in the kernel so we might have to use the cmd line provided for that. U can use it in the same app.
Currently I'm back on ICS... So once I can't do it now. Today when I get some time I will re-install and run this.
Googler_1976 said:
But i think the rotation issue is in the kernel so we might have to use the cmd line provided for that. U can use it in the same app.
Click to expand...
Click to collapse
It probably is in the kernel. That's why I want the output of dmesg as well.
Incidently, it seems my initial kernel patch is winning some reviews and with any luck, I'll have it in the official cm kernel fairly soon now.
I did a search in the play Store for Log Cat, there are numerous apps in there for saving, sharing logcats, will these do the job? I certainly seems it would be much easier than ADB. Just curious.
dr4stic said:
It probably is in the kernel. That's why I want the output of dmesg as well.
Incidently, it seems my initial kernel patch is winning some reviews and with any luck, I'll have it in the official cm kernel fairly soon now.
Click to expand...
Click to collapse
So Is it basically same kernel for ur device and I577? if it is.. That's really cool.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
pegb856 said:
I did a search in the play Store for Log Cat, there are numerous apps in there for saving, sharing logcats, will these do the job? I certainly seems it would be much easier than ADB. Just curious.
Click to expand...
Click to collapse
I think most of them cant run booting up... ("I think is the keyword")
Googler_1976 said:
So Is it basically same kernel for ur device and I577? if it is.. That's really cool.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
I think most of them cant run booting up... ("I think is the keyword")
Click to expand...
Click to collapse
*I think* that makes sense and you are probably right.
dr4stic said:
Guys, turn off the notifications. The touchkey driver I used is the stock samsung one which doesn't have the BLN (button lights notifications) which CM is looking for. Whenever you get a message, or email, or really anything that would trigger a blinking LED, it's gonna crash the phone cuz the driver doesn't know how to handle it.
http://forum.xda-developers.com/showpost.php?p=32548093&postcount=108
Click to expand...
Click to collapse
Here is the Logcat... and Kernel Log
Well I'm all in. I was cleaning things up before loading everything up and accidentally deleted all my backups . Oh well, so far I'm loving this. Hope it's good to go for a daily or I'll be setting up a new ICS install too.
I could always upload one of my ICS backups to drop box for you if it comes down to that
Sent from my SAMSUNG-SGH-I577 using xda premium
ktempleton said:
I could always upload one of my ICS backups to drop box for you if it comes down to that
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
Not a big deal. So far not having any issues other than rotate bug. Even notifications are working ok. I did turn off some notification light setting and I thought I saw something about softkey flash notification, but I couldn't find it again. Take me a bit to get used to the menu structure.
Everything is pretty smooth as of right now.
Unfortunately my phone randomly shut down twice today and I ended up going back to ICS for now. The first time I had foursquare open but had laid it down since the light changed and when I picked it up it was off, the second time it was just laying on the desk and when I picked it up it was off again. I did back it up before restoring ICS though. I've got a lot going on the next couple days and need a dependable device.
I might restore back to CM 10 and tinker with it when I'm not expecting phone calls.
pegb856 said:
Unfortunately my phone randomly shut down twice today and I ended up going back to ICS for now. The first time I had foursquare open but had laid it down since the light changed and when I picked it up it was off, the second time it was just laying on the desk and when I picked it up it was off again. I did back it up before restoring ICS though. I've got a lot going on the next couple days and need a dependable device.
I might restore back to CM 10 and tinker with it when I'm not expecting phone calls.
Click to expand...
Click to collapse
Same here after i provided the logs. The phone was lying and when i checked it was shutdown.
.
We were having similar problems on the blaze end. Most of them seem to be getting worked out pretty quickly so I'm fairly confident you guys should be seeing some problems fixed soon too.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
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, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Follow this install guide substituting various filenames with filenames below if you don't understand the below instructions
Get nookhd-emmc-cwm.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost). (use dd under Linux and MacOS, use Win32DiskImager or similar tool under Windows, use 7zip under windows to unpack).
Download CWM recovery zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need it). As another option there's a graphical TWRP recovery available. (you can only have one recovery option)
Also download latest nightly from http://download.cyanogenmod.com/?device=hummingbird
You can write installation zips for recovery, cm binary + whatever else you need and transfer them to Nook user storage (if you have it activated and all), OR add all these files + whatever other packages you might need right away on to the sdcard.
Insert sdcard into Nook and reboot the Nook, next install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Use Install zip from sdcard, if you copied installation zips to sdcard, otherwise use "choose zip from internal sdcard" - both options are in "Unstall update from zip file".
Erase /data (only on initial install, this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there before you remove).
Remove the sdcard 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).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhd in build.prop) - This is because they specifically blacklist Nooks! For workaround #2, revert the value back to hummingbird when done installing, otherwise you'll lose sound.
- Certain sdcards still remain unstable.
- Google Earth crashes when you press "my location" button, but works fine otherwise.
Changelog:
13/08/09 - We are part of official CM and latest nightly from here is what you should get now: http://download.cyanogenmod.com/?device=hummingbird
13/08/01 - cm-10.1-20130801-UNOFFICIAL-hummingbird-emmc.zip
- Data usage statistics should now work
13/07/19 - cm-10.1-20130719-UNOFFICIAL-hummingbird-emmc.zip (backup link)
- Update wifi drivers to R5.SP3.06
- Kernel with initial charger control for the charger app to work
- 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.
13/07/11 - cm-10.1-20130712-UNOFFICIAL-hummingbird-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-hummingbird-emmc.zip
- Rebased on cm-10.1.1 for security fixes.
13/07/08 - cm-10.1-20130708-UNOFFICIAL-hummingbird-emmc.zip
- ExFAT and NTFS support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-hummingbird-emmc.zip
- revert accidentally applies frequency bump patch that made it into 07/04
13/07/04 - cm-10.1-20130704-UNOFFICIAL-hummingbird-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-hummingbird-emmc.zip
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-hummingbird-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-hummingbird-emmc.zip
- Experimental kernel work
- enabled 1.5GHz freq by default
- in-kernel bluetooth
13/06/24 - cm-10.1-20130624-UNOFFICIAL-hummingbird-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-hummingbird-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-hummingbird-emmc.zip
- Boosted speaker and headset audio levels.
- gfx cash on startup fixed
- Zinio now works out of the box
13/06/12 - cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc.zip
- Fixed HDMI audio
- Fixed HDMI video upside-down picture
- Added usb audio support
- Enabled tabbed view in Settings app.
13/06/10 - cm-10.1-20130611-UNOFFICIAL-hummingbird-emmc.zip
- Initial release
This is unrelated development to bokbokan's sdcard/hybrid install, because he does not make his source code available, so don't ask me to pick features from his build.
oh my god
finally, :laugh:
Works great.
Sent from my Nook HD running CM10.1 on emmc.
Sweet!!!!!!
Will test it out.
I guess this means we will have access to a working repo soon so we all can start building from source.
dubidu said:
I guess this means we will have access to a working repo soon so we all can start building from source.
Click to expand...
Click to collapse
https://github.com/verygreen/android_device_bn_hummingbird
verygreen said:
https://github.com/verygreen/android_device_bn_hummingbird
Click to expand...
Click to collapse
Txs
Woohoo! Fantastic work! And thank you so much for posting source.
New binary release: cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc.zip
Changes:
- Fixed HDMI audio
- Fixed HDMI video upside-down picture
- Added usb audio support
- Enabled tabbed view in Settings app. (This seems to be looking ok, but if you find it's too bad, let me know and we certainly can try to roll it back or only have it for landscape or some other stuff).
Thank you!! :victory:
Running fantastic for me. Thanks.
AMAZING! I just wanted to cruise by the forums because I was bored with nothing new until I see this post! Awesome work is all I can say. Does this mean no more reboot restores with /system and complete control and customization of the device without the unlocked bootloader?
Haven't look at the code yet, but I believe if you change "ro.product.device" in "build.prop" you will loose all the sound.
Can someone test it?
Niiiiice! Thanks, been waiting on this.
Now, quick question: There is a stock ROM to flash, right? I just exchanged another HD & it was easy enough to just remove the SD card. I've only had this HD a week.
Thanks!
Oh yeah, I remember now: Yes, there is.
http://forum.xda-developers.com/showthread.php?t=2062613
LAYGO said:
Niiiiice! Thanks, been waiting on this.
Now, quick question: There is a stock ROM to flash, right? I just exchanged another HD & it was easy enough to just remove the SD card. I've only had this HD a week.
Thanks!
Click to expand...
Click to collapse
This is a ROM to replace the stock on emmc. You should back up your stock first. E.mote has an excellent tutorial that verygreen links in his OP here. Then you can restore that backup to get back to stock if you need to return it.
Edit: Guide is here. Just substitute the files from the OP instead of the ones listed in the guide:
http://forum.xda-developers.com/showthread.php?p=42399961
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
This is a ROM to replace the stock on emmc. You should back up your stock first. E.mote has an excellent tutorial that verygreen links in his OP here. Then you can restore that backup to get back to stock if you need to return it.
Edit: Guide is here. Just substitute the files from the OP instead of the ones listed in the guide:
http://forum.xda-developers.com/showthread.php?p=42399961
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I guess I wasn't clear in my question (too early). I just needed to know if there was a stock ROM to flash back to stock in case I had to return it. Of course, I could just Nandroid my stock install too (DUH, didn't think about that, just like you said).
Updating to latest ROM?
Folks,
I picked up a Nook HD+ 16Gb last night and followed the guide to install CM10.1. Everything went smoothly. A big THANK YOU to verygreen and lepinlar for all the work in creating this and the guides/instructions on how to install.
I've got a couple questions:
I installed the cm-10.1-20130608-UNOFFICIAL-ovation-emmc ROM and have made some changes on the tablet (added my daughters as Users, downloaded some apps, etc). How would I go about upgrading to the cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc ROM? Would I lose the changes I've already made? Is there way to install/upgrade to the new ROM and keep the changes I've already made? Thanks.
Shenandoah
shenandoah2 said:
Folks,
I picked up a Nook HD+ 16Gb last night and followed the guide to install CM10.1. Everything went smoothly. A big THANK YOU to verygreen and lepinlar for all the work in creating this and the guides/instructions on how to install.
I've got a couple questions:
I installed the cm-10.1-20130608-UNOFFICIAL-ovation-emmc ROM and have made some changes on the tablet (added my daughters as Users, downloaded some apps, etc). How would I go about upgrading to the cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc ROM? Would I lose the changes I've already made? Is there way to install/upgrade to the new ROM and keep the changes I've already made? Thanks.
Shenandoah
Click to expand...
Click to collapse
First you do not want to flash that ROM to your HD+. If you look at the filenames you will see ovation (which means HD+) and hummingbird (which means HD). But if you want to upgrade to a newer ovation ROM, just flash the newer ROM over the top of your old ROM. It will keep all your changes you've made.
Sent from my Nook HD+ running CM10.1 on emmc.
Lepinlar,
Sorry about the post. I didn't read it close enough to realize it was for the HD (not the HD+). Should I delete my original post so it doesn't confuse anyone else?
Shenandoah
shenandoah2 said:
Lepinlar,
Sorry about the post. I didn't read it close enough to realize it was for the HD (not the HD+). Should I delete my original post so it doesn't confuse anyone else?
Shenandoah
Click to expand...
Click to collapse
No, it might actually help others users who are confused by the issue. Leave it there as originally posted.
Sent from my Nook HD+ running CM10.1 on emmc.
Awesome ROM, thanks for doing this. Battery life vs stock is amazing, UI looks much better, more customizable, great having root to back up apps and etc.
I had a small issue with the 06/08 build on my HD+ where the battery would not recharge. Power cycling (turning it off and then on again) seemed to fix it. Is anyone seeing this issue with this 06/12 build? Thanks!
I see there's this new CM11 going, and thanks to @Hashcode who solved most of the complex problems already, here's my first stab at CM11 on our Nook HDs that installs into internal memory (EMMC).
The install is a lot similar to how it was done in CM10.2 days, but you will need a new recovery image (and a new sdcard image for those doing initial install):
So, For Nook HD+: Initial ovation sdcard image (cwm) | ovation recovery image (CWM)
For Nook HD: hummingbird Initial sdcard image | hummingbird recovery image (CWM)
I did some light testing and things seems to be working for whatever light loads I came up with, but still there are probably tons of problems that I have not yet noticed. Please write in the comments about what's broken and I'll try to fix it. Once it's good enough, I'll try to get official nightlies going for CM11 as well, I guess.
Latest CM11 EMMC images are now available as CM11 nightlies at:
For Nook HD+ get ovation builds
For Nook HD get hummingbird builds
There also might be experimental builds available referenced below in the history section.
(Also for completeness, For Nook HD+ sdcard image cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook
For upgrades from CM10.x (the only tested are 10.2 and 10.1). If you have any problems after upgrade - you'll need to do factory reset to clear /data:
Download recovery zip and CM11 install and place it on the nook
Reboot into recovery you already have installed
Flash the recovery zip you just downloaded
reboot into recovery again (This is important! Failure to do this will botch your upgrade and you'll need to wipe /data) so that the new recovery is started.
Install CM11, install other stuff you need like gapps
reboot
enjoy
Note: After upgrade you will need to reenter all of your wifi passwords.
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (usually only needed on official CM builds, as otherwise you can use Quick Settings panel): USBHostSwitcher.apk
Known problems:
- attempting to reformat external sdcard from android crashes volume manager - seems to be upstream problem of some sort. The sdcard is left in some strange state, so don't do it. (if you did, reformat the sdcard on your PC, all data will be lost either way)
Changelog:
2014/11/297 - Bring sdcard build to current source version:
* cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
2014/08/17 - Bring sdcard build to current source version:
* cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip
2014/01/18 - Fixed 1080p movie playback on Nook HD+:
* cm-11-20140118-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140118-UNOFFICIAL-ovation-sdcard.zip
2014/01/17 - Fixed headset mic issue
* cm-11-20140117-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140117-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140117-UNOFFICIAL-ovation-sdcard.zip
2014/01/15 - Switched to TI wpa supplicant, should fix a bunch of wifi-related issues
* cm-11-20140115-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140115-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140115-UNOFFICIAL-ovation-sdcard.zip
2014/01/09 - Fixed inability to write to sdcards.
* cm-11-20140110-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140110-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140110-UNOFFICIAL-ovation-sdcard.zip
2014/01/08 - Misc updates: autodetect sdcard format, not just vfat. fuzzy touch patch courtesy of D Marble, bt-pan services that reportedly fix bt tethering for some people.
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip
2014/01/06 - Initial release
* cm-11-20140106-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140106-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
The screen kept flickering like a tube light few times.
Thank you! Welcome back
Sent from my BN NookHD+ using xda app-developers app
Welcome back, you've been missed greatly. I kept telling everyone not to panic, you would be back.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks dude. I was hoping you'd start building it. Downloading now!
Working well so far. Thanks for making it and glad to have you back.
for those who need gapps you could see below (Be sure to choose 4.4.2 gapps.)
Link for PA gapps : http://forum.xda-developers.com/showthread.php?t=2397942 <MINI MODULAR PACKAGE 121 MB>download link http://goo.im/devs/paranoidandroid/roms/gapps-mini/pa_gapps-modular-mini-4.4.2-20131230-signed.zip
My personal favorite is BaNK's gapps : http://forum.xda-developers.com/showthread.php?t=2012857 <core gapps only, 17MB>download link http://www.androidfilehost.com/?fid=23269279319195954
Thanks for starting the work again -- I can't wait for official nightlies. And welcome back.
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Nice to see this, I've used Bokbokan's eMMC build off his blog with TRIM support by default (MAG2GA ver06 10/2012), and I've used yours with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
It would be interesting to know if it presents visible differences from CM 10.2 regarding responsiveness, especially with ART enabled. It's the last fort to be conquered with our nooks (trim+art). Sadly my nook is not back yet so any reports would be welcome.
Awesome
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
jjjooonnn said:
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
Click to expand...
Click to collapse
It should be updatable via the settings once it's an official built. Right now, all of the builds are unofficial ones, so they have to be fully downloaded and flashed.
verygreen is the official device maintainer for CM though, so once he "approves" of the build, it will be built nightly by the CM servers, and then it will be fully integrated into their update mechanism (or CyanDelta if you use that). Just like the 10.2 builds.
TeutonJon78 said:
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Click to expand...
Click to collapse
It's on the todo list, but cwm was easier to make at first (as in, next to zero effort)
jjjooonnn said:
Does this build come with TRIM enabled?
Click to expand...
Click to collapse
Yes, this has TRIM-enabled kernel, though I have not decided if I should do it for the official releases.
Have there been any more bricks with the trim-fixed kernels in the past couple of months?
Will this be updatable via CM updates in settings?
Click to expand...
Click to collapse
I guess yes, once there are official nightlies again. But I want to make sure it's at least of adequate quality before enabling that.
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Good job!
I can't speak for anyone but didn't see anything from a quick search in the post: TRIM FAQ. I can attest that mine works and I believe it should be one of the bad eMMC (MAG2GA ver06 not ver05).
I did test TRIM (vdc fstrim dotrim) no issues, and found the CM11 under updates (after I updated to CM11) so I can attest to that much!
Thanks for the reply
Darrian said:
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Click to expand...
Click to collapse
I would say they are about same smooth. Succulent's build has some nice framework and more option in performance settings. But just from system ui or user experience they are almost the same. Not could I tell the difference in app opening or transition.
Stock launcher Does lag when press the app drawer butter from home screen. But I use Nova launcher to solve the problem.
No find significant performance inprovememt over cm10.2 yet. Maybe Kitkat just does more job in UX polishing rather then performance.
Hopefully we could find some Performance MOD to use in KitKat.
It may very well be due to the fact that I upgraded from CM 10.2 and did not do a clean install, but for me Succulent's build was extremely laggy, many apps froze frequently, and when too many apps (more than like 3) were open it would reboot itself. I have none of those problems with this build, it's super smooth and fast and I haven't had any apps become laggy or crash or reboot my tablet. And this is upgrading from CM 10.2>Succulent's KK>Verygreen's KK; I still haven't done a factory reset and don't plan to unless it becomes necessary later. I use Nova as well. I'm not saying Succulent's build is bad, I thought it was bearable enough to use and was planning on using it long term, updating with each new build until it got to where I thought it should be, but then I installed this build and the difference is staggering. If I reflashed Succulent's build and wiped my data partition I might have a better experience, but now that I have this I don't see any need to.
this is great, glad to see you're back =)
my nook is currently being borrowed, i was wondering if anyone could quickly benchmark it?
thanks
Thank you Verygreen for this new build.
I will try it today.
I have 2 questions about CM11 and Nook HD+ hardware:
- did the HD+ have a bluetooth low energy (BT 4.0) chips?
- did the HD+ have a Low-power audio playback (kitkat new feature) capable chips?
If yes, is it included in this new CM11 build?
Thanks
Edit:
I found that Nook HD+ has wl1271l chip and uses wl12xx driver. That chip is BT 4.0 and BLE. See here http://www.rfm.com/products/data/wls1271l.pdf
But this thread show that BLE isn't activated in CM.
verygreen said:
久しぶりでした
(Also for completeness, For Nook HD+ sdcard image cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
Click to expand...
Click to collapse
Thanks verygreen. Great to see your are back in action.
The SDCARD image link is downloading emmc image. Here is the correct like if any one is looking.
cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
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.