Hello People,
This time i bring you a cm10 build from the man it self "Hashcode" for our beloved Nook Tablet.
He is the one who took at his shoulders the Kindle Fire kernel and rom development and skyrocket their sales(Amazon).
I think no more needs to be said about the awesomeness behind this developer but to show our appreciation for finding the time to compile a test release from Nook Tablet Git.
We all expect more to come from this great day forward but nothing is promised and we all need to give our feedback and report issues from this ROM in this thread.
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it... there is always stock and CM7.
New Rom Link:
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20130123-UNOFFICIAL-acclaim.zip
Changelog:
- Added SIO and V(R) I/O Schedulers
- Sync with CM10 (a lot of changes)
- Disabled SR v3 and enable SR V1P5 as default.
- Patched Sensor(KXTF9) timing for faster response in games (from 100ms to 40ms)
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121207-UNOFFICIAL-acclaim.zip
Includes:
- 3 new CPU governors (LAZY-DYNAMIC_INTERACTIVE-WHEATLEY)
- Added safeboot settings for Silicon Performance (1.2Ghz)
- Added actual OSWR logic for mpu when turned on
P.s
Forgot to re-enable SR V1P5 Next time
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121128-UNOFFICIAL-acclaim.zip
- Deep Sleep really fixed this time, sorry guys
- I/O Tweaks for speed
- Better memory timings
- More Logical values added to CPU idle code
- Better Battery Life expected.
- 1.2Ghz CPU as default.
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121121-UNOFFICIAL-acclaim.zip
Includes:
- Reverted Kuzma's Emif changes so device can deep sleep again
- Removed SmartReflex 1P5 and downgraded to SmartReflex V3 for more compatibility with troublesome nooks
- Added O3 flag on compile for speed optimization
- Silicon Performance Enabled = 1.2GHZ CPU
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121115-UNOFFICIAL-acclaim.zip
Includes:
- 10 touch driver taken from Nook HD and adjusted to Multitouch compatibility by Mik_os
- New Backilight Led driver taken from Nook HD and adjusted to our github compatibility by Mik_os
- Still CM10(4.1.2) (JB4.2=CM10.1) sync
- Kuzmas excellent new drivers from Nook HD Source
- Bug fixes
All credits goes to our development team Kudos guys for an exceptional work!
In my opinion this is considered daily driver rom because:
Known Issues:
-None
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121107-UNOFFICIAL-acclaim.zip
Mirror:
http://celticstorage.co.uk/cm10/cm-10-20121107-Hashcode-acclaim.zip
Includes:
-New PVR Driver DDK [email protected]
-New WLAN firmware R5.SP3.03
-Greatly improved kernel thanks to all the nice developers in here
-All fixes Implemented:Touch/Accelerometer/PVR Graphics/LG Panel.
ROM Link:
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121023-UNOFFICIAL-acclaim.zip
Mirror:
http://celticstorage.co.uk/cm10/cm-10-20121023-Hashcode-acclaim.zip
Flashable Recoveries(Put into sdcard and flash from recovery like a rom)
http://celticstorage.co.uk/cm10/CWM_v6.2.7_emmc.zip
http://celticstorage.co.uk/cm10/TWRP_v2.3.3_emmc.zip
Thanks goes to Succulent (HD)
Gapps:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
And as always,
Enjoy your Nook.
Added a flashable package from a new code implemented into rom by Mik_os
This will give you peace of mind in touch controller firmware flashing as it is very user friendly and straight forward.
Just flash this with recovery and you will find a new package in android app drawer that can test and see what firmware version you are at and offer you the opportunity to flash the other. Other can be 2 or Multitouch and depends on what firmware you are at the moment you run the application.
Nice!!!!!
* DISCLAIMER *
To be perfectly clear: This was a flash .zip built straight from the device/kernel sources that the current NT devs have worked very hard on.
I built it as a test case to see if there were compile issues and/or other external problems with the existing builds compared to the Kindle Fire builds which don't show the same issues.
THIS ROM IS NOT NEW. I didn't do anything but sync down the 2 acclaim projects press "go" on the compile.
Only issue I see of now is apps on SD card still disappear when nook reboots. I will report any other issues as I see them.
Thanks for all your hard work devs on the nook. To think I was about to give it up for a nexus 7. No way now I love this thing. :thumbup:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Hey,
loving the development on the Nook!
I have flashed this ROM after full wipes, etc etc..
Everything seems to work..however, a big difference between this ROM and the 12/10 release from the other thread has been lots of choppyness/lag. Sometimes things lag so badly they crash..ie when in Settings. I'm not the most tech-savvy person so forgive me.
ps. it might be just me, but the colors seems sharper/cleaner/nicer!! And despite my comment about lag..when there is no lag, it is very responsive and even faster than 12/10 release..odd
Very nice otherwise
Mike
Downloading , i'll flash this rom
thanks u so much.
mikenexus said:
Hey,
loving the development on the Nook!
I have flashed this ROM after full wipes, etc etc..
Everything seems to work..however, a big difference between this ROM and the 12/10 release from the other thread has been lots of choppyness/lag. Sometimes things lag so badly they crash..ie when in Settings. I'm not the most tech-savvy person so forgive me.
ps. it might be just me, but the colors seems sharper/cleaner/nicer!! And despite my comment about lag..when there is no lag, it is very responsive and even faster than 12/10 release..odd
Very nice otherwise
Mike
Click to expand...
Click to collapse
the same felling with you. and.... Mic does not work...
Note:12/10 build had a workable Mic (SGT7+CM10+Cherry Picks,By meghd00t)
http://forum.xda-developers.com/showthread.php?p=31400856 this has the mic fix. Search around a little and you can find answers
Sent from my Droid using xda app-developers app
createpassword said:
Anyone? Its a pretty simple question...
Click to expand...
Click to collapse
I think is a simple flash to find out. The truth is out there.... (drums)
So my friend has the 16gb Nook Tablet.. will this work on it? And really? Everything works?!?!?! No more screen of death? Mic works too??!?! Netflix?!?!
I wanted to comment i tried this one and i have the same problem with all cm10 roms....after a few minutes....it wont let me download anything...like i try to download and it reaches 100% but says still in progress and freezes everything because once that hapens and you try to reboot or power off it just loads but does not reboot or power off....
Sent from my Nook Tablet using xda app-developers app
createpassword said:
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
I don't think anyone owes you anything at all. Such entitlement....
Sent from my Barnes & Noble Nook Tablet using xda premium
createpassword said:
It is not "simple" to mess with my wife's tablet. Nor is an experiment of this nature CONCLUSIVE. I have no interest in "trying" something that is well known to be broken/useless. Much better to leave it stock in that case, alter only when known functional.
And no, the answer is NOT "out there". That's why I asked.
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
This is a development rom in the development section of the forums. It seems to me it would be better for you to return your wife's nook to stock. This rom was posted for testing and bug reporting.
Sent from my DROID RAZR using xda premium
createpassword said:
I haven't seen any mention of it lately in any of the threads, but what is the status of things like random reboots and failures to wake from sleep?
Click to expand...
Click to collapse
I haven't had any reboots or hangs on my NT 16 GB, but it's only been 12 hours. I'll test it over the weekend more to see if I can make the permanent jump from CM7.
this rom have mixer or not.
createpassword said:
I haven't seen any mention of it lately in any of the threads, but what is the status of things like random reboots and failures to wake from sleep?
Click to expand...
Click to collapse
No. I put it on my mother's 16GB Nook Tablet and it's miles better than CM7 was. Not perfect but no serious flaws.
Has anyone experienced download problems that cause lag that doesnt allow you to reboot or poweroff or do anything?
Sent from my Nook Tablet using xda app-developers app
I have rooted every device I own. I also have a Nexus 7 and a Nook Tablet. In somewhat of defense of the guy earlier working 10 hours, wife and 4 kids sometimes it is easier to ask rather than "just flash it". I want to use my Nook so my kids ages 2 and 4 can watch Netflix on long car trips. The Nook is much more of a tank than the Nexus 7 and would bee much less bummed if the Nook gets broken over my Nexus.
I'm not saying my time it's any more important than yours. And it doesn't take any more effort to answer a simple question than it does to tell someone Rio flash back to stock.
I would like to know if Netflix works on this build? If so I will flash it ASAP. If not I will not get my Nook out of my nightstand and will keep checking back once and a while.
Thanks.
Sent from my DROID SPYDER using Xparent ICS Blue Tapatalk 2
Random reboots seems to be fixed.
createpassword said:
It is not "simple" to mess with my wife's tablet. Nor is an experiment of this nature CONCLUSIVE. I have no interest in "trying" something that is well known to be broken/useless. Much better to leave it stock in that case, alter only when known functional.
And no, the answer is NOT "out there". That's why I asked.
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
My deepest apologies.
It was an error from my part so i went and fixed my statement in Official post.
Thanks again for pointing out my huge mistake.
Related
This is the development thread of CyanogenMod 9.
Currently there is no ROM available, but I'm working hard to get you one
Please do not ask for ETA's and I will not tolerate posts like "when will be ready 100%, when will be stable and etc". Also, if anyone disrespects the thread, not counting if they are disrespecting devs or normal users, you will be reported! You have been warned.
For questions etc, please go to Discussion-thread...
After spending a lot of time to research and trying to solve things I'm gonna stop working on this for some time untill some more resources are available ...
Special thanks to:
Andy572
lupohirp
Currently working:
- default Audio
- GSM
- WiFi
- Touchscreen
TODOs
- fix sensors and sensor service
- fix bluetooth / dbus
- fix camera
- fix video
- fix audio and add fmVolume
- fix fm radio
- fix wired headset function
- fix bluetooth headset function
- fix usb (in vold service and kernel)
- fix general bugs as posted on CAF and CyanogenMod
for later use
* for later use
So ICS cyanogen sources are finally all up?
Excellent news! Awaiting for this
Awesome!!! Can't wait! Thanks arjen
Sent from my LG-P509 using xda premium
Using nightlies here
Simply Awesome if u do it..all d best to U..Hope u support this like Mik did..
I'z doesing that too! well,to be honest,I'm working on CAF ICS sources right here right now
Your PC specs? I can build ics in 40 mins with 6gb ram and an i7
Specs of the machine I'm currently working on are lower Guess buildingtime is about 90-110 minutes.
It's still busy on the build, had to fix a few things so far.
Will see how far it goes and what more needs to be done. For now it's been going for 60 minutes...
How big are the sources?
cause i'm getting them and i want to know if i can go to sleep till they are down
Andy just said ICS for our phones it's impossible, so don't get your ups high.
No, that's not what Andy said, for now it's impossible to have hardwareacceleration,
CM9 will still run on our phones. It will only support 2D for now.
_Arjen_ said:
No, that's not what Andy said, for now it's impossible to have hardwareacceleration,
CM9 will still run on our phones. It will only support 2D for now.
Click to expand...
Click to collapse
hey guys have you seen mu hw3d fix in phoenix thread??? hw3d they call adreno 200 lib correctly and i can go into th gui....problem is hwcomposer.so libraries that when called from launcher they go in bootloop and crash phone!! howewer i'm trying a bug bump....merging right now AOSP sources with cyanogenmod!!we need only a good hwcomposer!
Hope it will work eventually...
Build did not complete last night due to a power faillure
Will look at it again when Real Life Work is done
_Arjen_ said:
No, that's not what Andy said, for now it's impossible to have hardwareacceleration,
CM9 will still run on our phones. It will only support 2D for now.
Click to expand...
Click to collapse
that's really good news. I think 3d does not matter much for those of us who don't play many games.
great news well its always been great with p500 as we get almost every port and great supoort from dev.
best of luck for project..
server3249 said:
that's really good news. I think 3d does not matter much for those of us who don't play many games.
Click to expand...
Click to collapse
this is some wrong, please read here @all:
http://forum.xda-developers.com/showpost.php?p=19998704&postcount=476
Ok,
got CM9 compiled succesfully, wil test booting later today (or perhaps tomorrow)
Am really busy on webshops at the moment.
_Arjen_ said:
Ok,
got CM9 compiled succesfully, wil test booting later today (or perhaps tomorrow)
Am really busy on webshops at the moment.
Click to expand...
Click to collapse
Hope you get it in the first shot or atleast easily in a few tries
Sent from my LG-P500 using xda premium
You must already be on GB and have recovery installed. If you are on HC you must follow the directions in the forum on how to downgrade to GB
Use kevinrocksman's awesome tool to get to HC from GB(or downgrade from HC to GB, and many other convenient tools). He makes it easy for you
http://forum.xda-developers.com/showthread.php?t=1418258
This is a preview release of my DeSensed-View rom. This is WIP and this is the first preview release
Features:
Based off the Stock GB rom for the View
Lovethyevo's custom OC kernel. Thread found here: http://forum.xda-developers.com/showthread.php?t=1401112
deodexed
rooted
busybox
zipaligned
init.d support
ADW Launcher
Stock GB Bootanimation
Stock Calculator
Stock GB Browser
Stock GB Email App
A lot of the sense/htc apps and launcher removed
sprint bloat removed
Stock GB KB
Advanced power menus
Stock GB style status bar and icons
Stock GB lockscreen
maybe some other stuff I'm forgetting... lol
system rw at boot
phone.apk, telephony and hands free activation removed (radios disabled) I will released a 3g/4g enabler soon
Issues
You tell me.. test and let me know what's jacked up
When going through setup wizard and trying to select time zone it will FC. This is because the radios are disabled and it uses them to auto set your time zone. Just keep pressing next through set up and once it's finished you can go into settings and change it.
Maps might force close once or twice until you set up wifi
I have included the KB from CM7 but the keys are pretty small so I also included the GB KB,, the keys are small as well but you can make them bigger in settings
I am not responsible if you flash this and you brick your ****
DO NOT FLASH IF YOU ARE ON HONEYCOMB.. Follow the threads in the forum to learn how to downgrade to GB and get/keep s-off
Download Link: v 1
WIFI ONLY: http://goo.im/devs/graffixnyc/HTC_Evo_View/DeSensedViewGBv1.zip
Mirror : Coming soon
To enable sprint 3g/4g service flash this zip after you have flashed the rom(you can flash it right after flashing the rom) http://goo.im/devs/graffixnyc/HTC_Evo_View/enable4gGB.zip
mirror: http://d-h.st/1vm
Installation Instructions:
DO A BACK UP!
If coming from another ROM perform a FULL wipe in clockwork recovery: mounts and storage -> format /system format /data format /cache
If updating from a previous version of this rom just wipe the caches unless told otherwise
Flash the rom zip
reboot
enjoy
Changelog:
Code:
Changes in V1:
Fixed checkboxes being cut off
added live wallpaper picker back in
updated to google play store
got the AOSP calendar working
removed HTC calendar
removed a few other HTC apps that were left behind
moved flash player from being a system app to a user app
changed wifi scan to 180
I am not responsible if you flash this and you brick your ****
A few people have PM'ed me asking about donating. Well, I dont/wont ever ask for donations and honestly I prefer to NOT get donations. I do this work first and for most for me(Yeah I'm a selfish bastard) so I can learn more, so I can make my device the way I want my device, I just decide to share what I make for myself instead of keeping it for myself (I'm selfish, not greedy) and I feel if people start donating they might get more demanding and feel more entitled so I'd rather just skip all of that potential drama. When it comes to requesting things in this rom, I will put them in IF it's something I would use myself. If it's not, then I most likely wont add it. So please dont donate to me, If you want to do some good instead of donating to me, donate to a worthy charity instead! Thank you all for using my rom!
Awesome!
Sent from my PG41200 using Tapatalk 2
graffixnyc said:
So I know there are a lot of people that prefer GB over HC, So I have decided to make a DeSensed-View GB edition rom. I'm working on it as I type this message...So if you want some DeSensed GB goodness Stay Tuned....
Click to expand...
Click to collapse
Cool. I hate GB but its great to have choice. Looking forward to this.
Sent from my DROID RAZR using XDA
Well, as much as I hate having to go back to an older version, I don't like HC very much, so I will definitely try this ROM out.
My F5 button just got lucky; this will be its porn. Can't wait, man!
Sent from my PG41200 using XDA
So while I have the rom deodexing(it takes a while) I've been playing with the stock rom, deleteing crap and seeing what will break, also trying to add in some AOSP elements... that way when it is deodexing then I know exactly what I can remove and/or replace
removed a ****load of bloat and useless htc apps
rosie is gone, all the rosie widgets are gone, I have the free version of ADW, Stock GB browser and 3D Gallery all working, the stock calculator is working, GB KB included, The stock Calendar, contacts, camera or mms didnt work but I can try to tinker with them later
but the biggest one so far is I got rid of the Sense lock screen and have the stock GB one So much easier to do on GB than HC!
I might have a preview release up in a few hours
pretty cool man. but i think it would probably be pretty easy to actually build cm7 for the view. I believe the flyer has it going.
killahrey said:
pretty cool man. but i think it would probably be pretty easy to actually build cm7 for the view. I believe the flyer has it going.
Click to expand...
Click to collapse
pretty easy if you know how to kernel dev without a kernel dev porting the flyer CM7 kernel over or creating a new one we wont get anything AOSP The View only has a couple devs and zero kernel devs which means we are up ****s creek without a paddle for the time being
graffixnyc said:
pretty easy if you know how to kernel dev without a kernel dev porting the flyer CM7 kernel over or creating a new one we wont get anything AOSP The View only has a couple devs and zero kernel devs which means we are up ****s creek without a paddle for the time being
Click to expand...
Click to collapse
I asked the guy who did the Flyer CM rom to throw us Viewers a bone and port his Flyer version to the View. He said he might make it a weekend project but not promising anything.
If interested run over to his thread and pm the dev (very nicely) that you heard a rumor he might consider doing a View port and you just wanted to support the idea.
Maybe a little future fan influence will motivate him
Sent from my PG41200 using Tapatalk 2
Also check out the Q & A thread. There is a Chinese GB RUU out that has full pen support for the Flyer. May be some goodies to grab there.
Sent from my PG41200 using Tapatalk 2
Posted a preview release.. let me know what issues you guys find..
I noticed the market wasnt updating to the Play Store.. I'll include the updated APK in the next release but until then you can just install this and it will overwrite the market with playstore. No need to push it, just install it like you would any side loaded apk
http://d-h.st/aQQ
Another issue I found was sometimes the unlock slider disappears when you wake the device (just the left one though) but if you swipe as if it was there it unlocks. I'll have to look into that
Sent from my SGH-I777 using Tapatalk
Sounds great I may hold off on testing until it's done. Just hard bricked my E4GT this morning and I'm a bit gun shy.
Never hard bricked a phone before. Accidentally flashed an AOSP ICS rom over an ICS kernel. Apparently this is huge no no. Complete blue light of death hard brick. Thank god for insurance.
Just installed. Testing now. I'll edit in problems as necessary.
First thing I noticed is that the Setup Wizard force closes if I try to change the time settings. I can change the time settings just fine through the regular settings, though.
The keyboard wouldn't pop up at first for whatever reason. A reboot fixed it, though.
In the settings, the right side of the check boxes are cut off.
Also, the mobile signal level icon still shows up, even though I downloaded the WiFi only ROM. I'm guessing this is just an issue with theming for now, though.
freak4dell said:
Just installed. Testing now. I'll edit in problems as necessary.
First thing I noticed is that the Setup Wizard force closes if I try to change the time settings. I can change the time settings just fine through the regular settings, though.
The keyboard wouldn't pop up at first for whatever reason. A reboot fixed it, though.
In the settings, the right side of the check boxes are cut off.
Also, the mobile signal level icon still shows up, even though I downloaded the WiFi only ROM. I'm guessing this is just an issue with theming for now, though.
Click to expand...
Click to collapse
The first issue I mentioned in the OP. The keyboard popped up fine for me the first time. The check boxes I noticed and will look into. And the signal meter will always be there even if its just wifi. But you'll see its a empty signal. The only difference is hc puts a red x through it.
Sent from my SGH-I777 using Tapatalk
mitchellvii said:
Sounds great I may hold off on testing until it's done. Just hard bricked my E4GT this morning and I'm a bit gun shy.
Never hard bricked a phone before. Accidentally flashed an AOSP ICS rom over an ICS kernel. Apparently this is huge no no. Complete blue light of death hard brick. Thank god for insurance.
Click to expand...
Click to collapse
You don't have to be shy. I've been running it since last night and there are no huge major bugs that are show stoppers. Every rom has issues and is never perfect. But even though its a preview release its pretty stable except for the few mentioned small issues.
Sent from my SGH-I777 using Tapatalk
graffixnyc said:
The first issue I mentioned in the OP. The keyboard popped up fine for me the first time. The check boxes I noticed and will look into. And the signal meter will always be there even if its just wifi. But you'll see its a empty signal. The only difference is hc puts a red x through it.
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Doh...I just suck at reading, then.
graffixnyc said:
You don't have to be shy. I've been running it since last night and there are no huge major bugs that are show stoppers. Every rom has issues and is never perfect. But even though its a preview release its pretty stable except for the few mentioned small issues.
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Agreed. So far, it's definitely smooth, and just has those minor issues. I think this will do just fine until we get ICS (though I'll go over to an AOSP GB ROM if we get one). I like it better than Honeycomb already, even if it is an older system.
---------- Post added at 07:15 PM ---------- Previous post was at 06:31 PM ----------
Any chance I could get pointed in the right direction as far as getting the APK to enable live wallpapers again?
freak4dell said:
Doh...I just suck at reading, then.
Agreed. So far, it's definitely smooth, and just has those minor issues. I think this will do just fine until we get ICS (though I'll go over to an AOSP GB ROM if we get one). I like it better than Honeycomb already, even if it is an older system.
---------- Post added at 07:15 PM ---------- Previous post was at 06:31 PM ----------
Any chance I could get pointed in the right direction as far as getting the APK to enable live wallpapers again?
Click to expand...
Click to collapse
Didn't realize I took them out. Lol I must a went a little trigger happy on the delete key. Haha I'll get it back in.
Sent from my SGH-I777 using Tapatalk
Sounds good.
I was wondering if anyone could help me. I recently upgraded to a nexus and at that same time a friend of mine broke her phone, so I gave her my fascinate with AOKP M6 on it...but she's getting sick of the bugs. Since I really have no way of testing I was hoping someone could help me make the decision of putting either a TW ROM or the latest CM 10 nightly on the fascinate.
I've been keeping an eye of the CyanogenMod gerrit and it looks like Jt1134 has made some serious headway, but can anyone give me their educated opinion? (I'm already running the nightlies on my nexus so I'm more interested in device specific bugs)
Thanks if you can help, I just have no way to test and I don't want to piss off a bug intolerant girl. ^-^
CM10 nightly is my suggestion... personally I've never had any real issues with it. The Devil Kernel 1.6.1 has been working great, but sticking with the stock kernel could be good for future releases. I much prefer using Devil because of the performance tweaks, but your friend probably won't care.
The TW rom will give rock solid stability too, but honestly... CM10 is so fast and smooth I can't see why anyone would bother with a GB rom anymore... especially since CM10 is practically bug free.
Crawshayi said:
CM10 nightly is my suggestion... personally I've never had any real issues with it. The Devil Kernel 1.6.1 has been working great, but sticking with the stock kernel could be good for future releases. I much prefer using Devil because of the performance tweaks, but your friend probably won't care.
The TW rom will give rock solid stability too, but honestly... CM10 is so fast and smooth I can't see why anyone would bother with a GB rom anymore... especially since CM10 is practically bug free.
Click to expand...
Click to collapse
Thanks for the suggestion, yeah CM 10 looks like a very good option at the moment because of the now built in updater.
I also just remembered she was asking about the colors being washed out compared to stock, does the default CM 10 kernel come with anything to enhance that or would I need to flash devil kernel with Voodoo color? (She made it seem like a bit of a big deal so I promised I'd look into it)
sendan said:
Thanks for the suggestion, yeah CM 10 looks like a very good option at the moment because of the now built in updater.
I also just remembered she was asking about the colors being washed out compared to stock, does the default CM 10 kernel come with anything to enhance that or would I need to flash devil kernel with Voodoo color? (She made it seem like a bit of a big deal so I promised I'd look into it)
Click to expand...
Click to collapse
Hmm that's a good question. I've never really messed with tweaking the colors to be honest, and I've always used the CMC (Cyanogenmod Color) version of Devil because the VC one gives me a weird negative image flash when coming out of sleep mode. I'm sure there are some apps that will adjust color that she could get from the market, no matter which kernel it is. I think I even remember looking for the app that adjusts Voodoo Color and couldn't for the life of me find it. Sorry I can't be more help, the colors were always vibrant enough for me so I never really cared to adjust them
edit: Well I did find some basic color calibration settings under System Settings > Device > Advanced > Color Tuning. Not sure if it's going to be what she's looking for, but it seems to be a built in feature for the rom itself, and separate from the kernel options. The devil config manager I'm using doesn't have any color tuning options at all.
The app you were looking for was probably Voodoo Sound, a color calibration option becomes available in it if you're on a VC enabled kernel. It doesn't really matter though, it looks like I'll be flashing Devil kernel anyway as I just read some reports of "screen jumpiness" on the stock kernel in the devil kernel thread.
I'm not really sure what that means but I'd rather just avoid it entirely.
sendan said:
The app you were looking for was probably Voodoo Sound, a color calibration option becomes available in it if you're on a VC enabled kernel. It doesn't really matter though, it looks like I'll be flashing Devil kernel anyway as I just read some reports of "screen jumpiness" on the stock kernel in the devil kernel thread.
I'm not really sure what that means but I'd rather just avoid it entirely.
Click to expand...
Click to collapse
Those issues are almost always from someone who 'dirty flashed' instead of doing a proper data wipe and clean install. I've run on the stock kernel many times never experiencing those issues. That said, I still prefer the Devil kernel but I can see a couple of problems with her using that... 1) If a newer Devil Kernel is released, will she know enough to flash it? 2) If CM10 gets another partition change, or something that will break Devil, and she updates it could cause a boot loop, and 3) If she's not into customs roms as much as you she might go into devil settings and cause a lot of trouble if she's 'unhappy' with the performance. Food for thought
Crawshayi said:
Those issues are almost always from someone who 'dirty flashed' instead of doing a proper data wipe and clean install. I've run on the stock kernel many times never experiencing those issues. That said, I still prefer the Devil kernel but I can see a couple of problems with her using that... 1) If a newer Devil Kernel is released, will she know enough to flash it? 2) If CM10 gets another partition change, or something that will break Devil, and she updates it could cause a boot loop, and 3) If she's not into customs roms as much as you she might go into devil settings and cause a lot of trouble if she's 'unhappy' with the performance. Food for thought
Click to expand...
Click to collapse
Good points, I think I'll start her on stock kernel for a few days and go from there if she needs better performance/color control. Anyway, It's good to know the fascinate community is still awesome!
Thanks for your help.
I am curious to what bugs she has been having. I have been using AOKP since ICS build 28 with very few bugs if any throughout all the builds. I have been very pleased even with stock kernel as to how fast and responsive it is. I know CM to be good as well but prefer the cherry picks Steve spear has built into some of his releases
Sent from my SCH-I500 using xda app-developers app
Saiya69 said:
I am curious to what bugs she has been having. I have been using AOKP since ICS build 28 with very few bugs if any throughout all the builds. I have been very pleased even with stock kernel as to how fast and responsive it is. I know CM to be good as well but prefer the cherry picks Steve spear has built into some of his releases
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Apparently the browser randomly stops loading web pages and has to be force killed, MMS don't always come through, and...there were a couple more but I can't remember them at all.
I was really rushed when I flashed her phone and I'm pretty sure some of the stuff I put on there was in mid-development. (the kernel)
I have not had any problems with any web pages. MS6 for ICS should be stable although I am using the showcase on cspire network. Unfortunately I do not have picture/ MMS messaging to speak to that, but I know it has been a problem on several releases due to not wiping before flashing
Sent from my SCH-I500 using xda app-developers app
I agree that MS6 should have been a lot more stable, but my recommendation stands... go with CM10, it's just plain better
Crawshayi said:
Hmm that's a good question. I've never really messed with tweaking the colors to be honest, and I've always used the CMC (Cyanogenmod Color) version of Devil because the VC one gives me a weird negative image flash when coming out of sleep mode. I'm sure there are some apps that will adjust color that she could get from the market, no matter which kernel it is. I think I even remember looking for the app that adjusts Voodoo Color and couldn't for the life of me find it. Sorry I can't be more help, the colors were always vibrant enough for me so I never really cared to adjust them
edit: Well I did find some basic color calibration settings under System Settings > Device > Advanced > Color Tuning. Not sure if it's going to be what she's looking for, but it seems to be a built in feature for the rom itself, and separate from the kernel options. The devil config manager I'm using doesn't have any color tuning options at all.
Click to expand...
Click to collapse
i agree with this, for the colors i go there to the color tuning, just make sure you use a CMC kernel and not voodoo color. anyways my settings are 1.0 for red and blue, and .887 for green with all the gammas at -40. it looks amazing, vivid and sharp and not over saturated.
Wow that does look pretty good, did you just figure this out yourself or are there guides on how to calibrate?
Crawshayi said:
Wow that does look pretty good, did you just figure this out yourself or are there guides on how to calibrate?
Click to expand...
Click to collapse
i was just messing around with the colors in there and kept working down the gamma since im a sucker for vivid and non washed out colors lol, i ended up with them all the way negative but found out it had a tad of a green tone so i just moved the green slider back to where it looked about right. it is no one way calibrated or anything, just the best i could make make it look to my eyes.
If your friend really just wants a stable ROM, AOKP M6 should be their best bet. Likely the issue is that the phone has been upgraded many times; the best way to ensure a clean install of AOKP is to flash to stock in Odin then flash other things progressively to get to ICS. This post provides a great overview of the process.
exzacklyright.blogspot .com/2012/01/how-to-flash-ics-on-verizon-samsung.html
If your follow those steps for your friend, the issues with the browser should disappear. The end result? A bug free rom that makes everyone happy. I personally wouldn't suggest upgrading to CM10 unless your friend really just wants to upgrade their phone periodically.
mirwinator said:
If your friend really just wants a stable ROM, AOKP M6 should be their best bet. Likely the issue is that the phone has been upgraded many times; the best way to ensure a clean install of AOKP is to flash to stock in Odin then flash other things progressively to get to ICS. This post provides a great overview of the process.
exzacklyright.blogspot .com/2012/01/how-to-flash-ics-on-verizon-samsung.html
If your follow those steps for your friend, the issues with the browser should disappear. The end result? A bug free rom that makes everyone happy. I personally wouldn't suggest upgrading to CM10 unless your friend really just wants to upgrade their phone periodically.
Click to expand...
Click to collapse
I appreciate the response, sadly those are pretty much the exact steps I took to flash the fascinate before I gave it to her. I really don't know what's up with it, but why do you suggest staying on ICS?
I'm running the CM10 nightlies on my gnexus and the only real bug I have is ringtones reset to the default within the first day after flashing, after that it's pretty flawless. Are there some other bugs on the fascinate that I should be aware of?
sendan said:
I appreciate the response, sadly those are pretty much the exact steps I took to flash the fascinate before I gave it to her. I really don't know what's up with it, but why do you suggest staying on ICS?
I'm running the CM10 nightlies on my gnexus and the only real bug I have is ringtones reset to the default within the first day after flashing, after that it's pretty flawless. Are there some other bugs on the fascinate that I should be aware of?
Click to expand...
Click to collapse
That's too bad... I'm very surprised that there are still issues!
I'm pretty sure the fascinate isn't on the officially supported device list for CM10, which means that more bugs could be present, but honestly I'm not terribly familiar with that ROM. For me personally, I think ICS might be better since the voice search is much faster and there's more storage space or apps, but that's just me.
mirwinator said:
That's too bad... I'm very surprised that there are still issues!
I'm pretty sure the fascinate isn't on the officially supported device list for CM10, which means that more bugs could be present, but honestly I'm not terribly familiar with that ROM. For me personally, I think ICS might be better since the voice search is much faster and there's more storage space or apps, but that's just me.
Click to expand...
Click to collapse
The fascinate has been receiving official nightly cm10 builds for over a month, and due to recent partition layout changes, there is more storage space available than even a stock ROM.
Sent from my SCH-I500 using xda app-developers app
As much as I loved AOKP ICS M6, CM10 just blows it away. It's the best JB rom I've ever run, and with Devil 1.6.1 it's a beast :good:
are there any pics of cm10 anywhere and does the camera and camcorder work? Gapps seperate?
Let me preface this with the following (usually stated by the biggest idiot in the room) I am not a total noob when it comes to computer related stuff. I have been building and maintaining networks for better than a decade. Android is a bit new to me but I can follow directions and get things working without fail... usually. Also, Please let me state this is in no way shape or form a bash against the devs. This is an honest to god post looking for others feedback to make sure I am not missing something.
I guess this is a question for others that have run both CM 9 and CM 10. Has anyone noticed a degradation of performance when running CM 10 vs CM 9 from SD on a 16gb NT?
I have tried several versions of CM 10 and all have the same issues. SOD, games don't work, frequent power downs... the usual complaints. I originally skipped CM 9 because hey I wanted the latest and greatest but decided after reading some other threads about stability to give CM 9 0.5.3 a try. Wow what a night and day difference. Everything that didn't work in 10 works perfectly in 9(using the same card and partition layout).
On my CM10 installs I tried reformatting the SD card numerous times (Transcend 8GB/CL4). I tried the last 3 updated versions posted by chrmhoffman(SP?) I've wiped and re-wiped dalvik and cache, though to be honest from the SD version I am not sure if it does anything. I have tried re-downloading the files in the event they were corrupted. I've verified that I properly placed updater-script for the SD install. I have spent hours verifying and re-verifying I didn't miss something. Other than the B&N repartition I have nothing special done to my nook. I haven't even installed a recovery or rooted the stock OS.
So perhaps I'm doing it wrong? Will an internal install make a difference?
I have read many a thread and haven't found anything comparing the 2. If they exist and this has been mentioned please direct me to the appropriate reading material.
SlowCobra96 said:
Let me preface this with the following (usually stated by the biggest idiot in the room) I am not a total noob when it comes to computer related stuff. I have been building and maintaining networks for better than a decade. Android is a bit new to me but I can follow directions and get things working without fail... usually. Also, Please let me state this is in no way shape or form a bash against the devs. This is an honest to god post looking for others feedback to make sure I am not missing something.
I guess this is a question for others that have run both CM 9 and CM 10. Has anyone noticed a degradation of performance when running CM 10 vs CM 9 from SD on a 16gb NT?
I have tried several versions of CM 10 and all have the same issues. SOD, games don't work, frequent power downs... the usual complaints. I originally skipped CM 9 because hey I wanted the latest and greatest but decided after reading some other threads about stability to give CM 9 0.5.3 a try. Wow what a night and day difference. Everything that didn't work in 10 works perfectly in 9(using the same card and partition layout).
On my CM10 installs I tried reformatting the SD card numerous times (Transcend 8GB/CL4). I tried the last 3 updated versions posted by chrmhoffman(SP?) I've wiped and re-wiped dalvik and cache, though to be honest from the SD version I am not sure if it does anything. I have tried re-downloading the files in the event they were corrupted. I've verified that I properly placed updater-script for the SD install. I have spent hours verifying and re-verifying I didn't miss something. Other than the B&N repartition I have nothing special done to my nook. I haven't even installed a recovery or rooted the stock OS.
So perhaps I'm doing it wrong? Will an internal install make a difference?
I have read many a thread and haven't found anything comparing the 2. If they exist and this has been mentioned please direct me to the appropriate reading material.
Click to expand...
Click to collapse
Take a look at the CM9, CM10 and the kernel 3.0 threads in the developer section. There are two flavors of CM9 out there, one compiled with the GB kernel and one compiled with the ICS kernel (sorry, but I can't recall at which point chrmhoffman moved his CM10 build to the newer kernel). All of the problems you mentioned are well know bugs in the 3.0.x kernel at this time, and the devs are working feverishly to resolve them. In the meantime, running CM9 with the GB kernel (2.65.x) will give you a more stable platform, but no access to the advanced features in the newer kernel -- hardware video acceleration being the most obvious of the new features.
With all of that being said, I've been switching between chrmhoffman's latest CM10 build and demetris' latest CM10/cherry pick build for the last couple of days, and they are both tremendously improved over their earlier builds in terms of stability. I would confidently use either one as a daily driver at this point.
Ugh, see I'm an idiot. I totally spaced on the fact that it wasn't running 3.x kernel.
OK beyond that I still find CM10 really unusable and I'm not sure how others are getting it to function so well. I've tried the last 3 revisions with the same results on each of them. Could it be a matter of not running it from internal? Has anyone tried the SD version then switched to emmc? If yes what were your results and observations?
Sent from my NookTablet using xda app-developers app
I actually find that ROMs run better from my SD card, but that's probably due to my SD card having pretty good speeds. As for the problems that currently exist on the CM10 ROMs, there isn't going to be much difference in BSODs and random reboots between running from internal and SD.
Solar.Plexus said:
I actually find that ROMs run better from my SD card, but that's probably due to my SD card having pretty good speeds. As for the problems that currently exist on the CM10 ROMs, there isn't going to be much difference in BSODs and random reboots between running from internal and SD.
Click to expand...
Click to collapse
Yep, the biggest improvements I've seen is from turning on "Don't Keep Activities" in the Developer Options and setting the CPU Governor to HOTPLUG in the Performance Options. With these set, I'm actually able to run for days at a time without getting an SOD failure.
spcagigas said:
Yep, the biggest improvements I've seen is from turning on "Don't Keep Activities" in the Developer Options and setting the CPU Governor to HOTPLUG in the Performance Options. With these set, I'm actually able to run for days at a time without getting an SOD failure.
Click to expand...
Click to collapse
Are you ****ting me? Days? With those settings I am lucky to get mins! Seriously the reason for the post was that I get 20 mins tops before I have to reboot it. Then it takes forever to reboot stating it is optimizing applications.
I did a clean install of 04/10 the day it came out and I haven't had a single reboot or SOD. I do have some minor issues with video playback but YouTube works as does MX Player (with software decoder). Battery life has been great too with about 2 1/2-3 days on a charge.
This is with the ROM Installed to internal emmc.
Sent from my Barnes & Noble Nook Tablet using xda premium
LifeWOutMilk said:
I did a clean install of 04/10 the day it came out and I haven't had a single reboot or SOD. I do have some minor issues with video playback but YouTube works as does MX Player (with software decoder). Battery life has been great too with about 2 1/2-3 days on a charge.
This is with the ROM Installed to internal emmc.
Sent from my Barnes & Noble Nook Tablet using xda premium
Click to expand...
Click to collapse
Ill give that version a shot and see what happens.
Ok so I looked at the latest CM10 and it looks like 0.5.3. I have tried that revision with the same abysmal results as the 5.2 and 5.1 or whatever the 2 previous revisions were.
Ugh talk about frustrating! I truly don't understand what I can be doing wrong that others can daily drive it and I can't even get 30 mins out of it.
SlowCobra96 said:
Are you ****ting me? Days? With those settings I am lucky to get mins! Seriously the reason for the post was that I get 20 mins tops before I have to reboot it. Then it takes forever to reboot stating it is optimizing applications.
Click to expand...
Click to collapse
No ***ting at all. I let my son run my NT until the battery died yesterday. I plugged it in for a few hours (probably more like 6 or 7 hours, to be honest). Powered it up 12 hours ago and unplugged it to check on battery performance. Now it's been running for 12+ hours without an SOD, and is at 85% battery...
I hate you! hahaha Just kidding. I think I hate my nook right now though.
Hey guys, all well and good but I would recommend you due to serial number implemented now be careful when you show it on public forums. Maybe b&n is watching you :banghead:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Have to 2nd the no SODs. Got a few with the first few releases but nothing since. I'm on Chris' CM10 (internal), no changes to CPU etc. The battery life is still bad but I try not let it get too low so I plug it in every night to charge.
Nikkiel
Sent from my Barnes & Noble Nook Tablet using xda premium
Some of you are really making me feel like this! haha It seems that all of you running solid appear to be running it internally. I'm starting to get the funny feeling that the SD modified version may be the problem.
demetris_I said:
Hey guys, all well and good but I would recommend you due to serial number implemented now be careful when you show it on public forums. Maybe b&n is watching you :banghead:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Thanks for the warning/reminder... I hadn't even thought about that...
[KERNEL] Starship-Kernel The Next Generation Stock/AOSP & CM-13 04/25/16 (Linaro 4.9)
Welcome to Starship Kernel The Next Generation (TNG) for the Nexus 6 Shamu. Not much else to say other than more than ever the Kernel is by design light wait, power efficient and moves at Warp Speed. There are no special features to play around with but instead designed to just be installed and just work. If looking for things to play around with may as well just move on as this is probably not the kernel for you.
Have shed some light on a few names below but really need to thank all the Nexus 6 Kernel Developers as could not have done much of anything without them. Before this project I had limited Kernel knowledge. Have been developing since I guess my first Rom had been CM6 based but never had much Kernel dealings. Have always worked joining up with a team to get CM or other AOSP like Roms up and running on TouchWiz,. Sense and other devices far from the Stock Android Experience. In working in groups and teams have for the most part always been the Device File & Vendor Blob guy. Everything I have learned about Kernels has honestly come from sifting through other Kernels and researching the hell out of out of commits until being able to stand on my own 2 feet and think so far have done a dam good job putting together a hell of a Kernel for the Nexus 6 that is extremely stable and performs well beyond expectation besides the big ol Jinx I just through out there.
This is now the new and improved Next Generation moving from say warp 6 to warp 9. Would say 10 but some funky stuff goes down at ten and if you dont know lets just say its not a place you wana go.
Definitely need to throw up thanks to Flair2, Imoseyon and Neoboddy89 as have used a decent amount of their commits in particular..
Features Worth Noting
Have placed features into either groups or single commits that make rather large improvements but are welcome to sift through the Kernels Commit History below as there are many individual changes to numerous to mention in a single post or even page . As mentioned most come from just sifting over and reading commits from every Kernel I could find. Most from Shamu but also some carefully selected from other devices with similar hardware
Kernel Version 3.10.101
Fast USB Charging
LZ4 Compression
Sio & Bfq i/o Schedulers - "bfq" used as default scheduler
ExFAT Support
Power Efficient Workqueues
KGSL Optimixations
Audio Codec Optimizations
Video Firmware Optimizations
CPU Idle Optimizations
GPU Power saving Optimizations
Adreno_Idler
Color Temperature Interface Using PCC
Frandom Support
LED Support (Rom must also Support)
MSM Vidc: Optimizations
Net: Wireless Bcmdhd, Various Optimizations
PM Enhancements.
F2FS 3.10
Starship Kernel, Nough Said!!
Source / Commit History aka change log
https://github.com/Chairshot215/starship_kernel_moto_shamu/commits/mm-mr1?page=1
Download Starship-Kernel_Class_SMTNG7_(Linaro-4.9) (04.16.2016)
Marshmallow 6.0.1 Stock/AOSP
https://www.androidfilehost.com/?fid=24499762636007231
CM-13.0
https://www.androidfilehost.com/?fid=24499762636007230
Again I am not responsible for any negative effects using any of the files on this thread or any post that has been linked in this thread so using is all at your own risk.
seems like nexus 6 development just blew up with new ROMs and kernels, thank you pal
Sent from my Nexus 6 using Tapatalk
Yup!
Does this kernel bypass force encryption?
Team Octos -Nexus 6
force encryption is disabled in the r_2 boot.img but so far is still showing that my N6 is Encrypted. With that said have not performed the recommended factory reset when going from a force encrypted boot.img to one that is not.
System UI Crash
Perhaps I've misinterpreted the OP, but I seem to have a major issue. Assuming this kernel is meant for 5.1.1 AOSP builds, upon flashing the kernel and wiping caches I get System UI crashes that do not allow me to actually start Android... am I at fault here?
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
chairshot215 said:
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
Click to expand...
Click to collapse
An issue like this is usually directed at the ramdisk. You may want to look into moving to an any kernel installer instead.
Sent from my Nexus 6 using Tapatalk
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
ps000000 said:
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
Click to expand...
Click to collapse
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Took me for a loop when Google started using the Teal coloring I was using for a few versions.
calaeb08 said:
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
chairshot215 said:
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Through me for a loop when Google started using the Teal coloring I was using for a few versions.
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
Click to expand...
Click to collapse
I myself know nothing about developing roms or kernels, that's why I'm here to ride on the bus with the smart kids lol. I do know that you can just leave it the way it is, but you gotta let people know it's forced encryption so they don't have to start all over. They can flash that zip that disables it before booting up.
What's the point of a sig anyways?
Well Definitely it for Lollipop, Probably. One thing that bothered me moving from the N5 to N6 is my BT Headset sounded like a warped and scratched record. I had lucked out with that pair in that had been reasonable priced and sounded amazing previously. Have added a few choice commits, well almost 2 pages but the things work like a charm. Decided for that and a few other reasons for one last post until 6.0.
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
NolenUmar said:
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I actually am still receiving emails about the Victory. Not that I could ever return to either the screen size or Touchwiz but wish I still had the device. Still feel like that SOB defeated me. Had been I think the 3rd device I worked on developing from the CM source and was so dead set on doing everything crazy proper so it could be an officially supported device. Wish I still had the device as do not like the feeling of spending countless hours on something and then leave unfinished. Think in the end all but GPS, Camera and that dang reboot when switching from Wifi to LTE. Think I used the Apexq as a template for getting everything else going. Otherwise wish the community luck. The phone was nice for the Price just a shame it has been years and everyone is still stuck on Stock with last I checked a bunch of out dated Kernels. Anyhow thats my Victory, rather defeated Rant. Remember at one point had got so frustrated used some command I don't remember off the top of my head and a lib decompiler and made the below list of all the files and their dependencies when trying to put together a vendor blob list.
http://pastebin.com/SFyJ14kv
Whats crazy about just pulling up this list is that I see the creation date was todays date but in 2013. Just had to mention that SOB device. Now I’m all worked up, lol.
Updated the M Kernel to r1.2 as works fine with SuperSU 5.1
This is an Encrypted Kernel. Will probably change with next update but for now it is Encrypted.
Now 2.0 with a few optimizations. Forgot about encryption but again looking for next update,lol.
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
calaeb08 said:
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
chairshot215 said:
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
Click to expand...
Click to collapse
You'd probably be better off using hellsgods anykernel scripts. Though, I'm not sure why yours isn't working to disable it. Theres also a fed patcher that should fix it. It kinda defeats the purpose of anykernel if your replacing files in the ramdisk instead of editing them.
Sent from my Nexus 6 using Tapatalk