Related
**Last update! This thread will (shortly) be locked, and a new one will be posted With Galaxian-Soup ICS Alpha 2
Check back in a few hours!
**Update, this tread will be retired and locked come this Thursday 1/5/2012
Read between the lines, and you will see that a brand new thread in its place will be posted, complete with a yummy new alpha of ICS for our dedicated fans to enjoy... We thank you for your patience, after this alpha goes out we believe tere will be more frequent releases and postings
Stay tuned, but from what I've seen so far we have many surprises in store for our next release, and you, is ICS nirvana just around the corner? Check back on thursday!
Please don't take this to mean we've fixed every outstanding bug, but we have made major core improvements, and fixed some of the big "items"
We are seaking anyone with expeirence working HAL's and drivers.. if you are interested please PM me.
TTFN!!
** Update ** Work around for voice search
It appears that voice search is broken in several AOSP roms, during my research I managed to get voice search working, however its the older version (prior to ICS). So far it seems to work fine!
So until Google fixes (or we do hah) do this to get voice search to work
Download
Voice_Search_2.1.4
Go to the location the this file was downloaded and from a terminal (linux/mac) or the command prompt (windows)
Code:
adb shell
su (if not root)
rm /system/app/VoiceSearch.apk
reboot
Then side load adb Voice_Search_2.1.4
Code:
adb install Voice_Search_2.1.4.apk
After the install click on the microphone icon near search at the top left of the home screen, accept the permissions (you have to do this a few times, 3 by my count), don't panic if it asks a few times, it does stick.
Enjoy!
** Update** Happy New Year XDA and esp our friends with the Galaxy Tab 8.9! is this the year of the droid? We shall see!
Hey everyone I wanted to give everyone an update and general goings on! Im sorry to inform you that there will not be a New Years alpha, but we will have something for you all very soon after.
Here is a taste of what early 2012 will bring to Alpha 2.
1. We have decided to use ASOP source rather than Cyanogen Mod, this is primarily why there hasn't been a new release since xmas. After reviewing some of the initial bugs, and reflecting on what we accomplished in under 4 days, we decided we wanted the focus of this rom to become "best in breed" optimized for the Galaxy Tab 8.9. Meaning we are going to cherry pick the best features of both to create the best possible experience, with the lightest footprint, and most importantly stock ICS launcher! NoWiz, no Trebuchet. So far it has yielded very positive results.
2. Moving to ASOP and stock launcher has fixed one of the big bugs, automatic home screen orientation. I know more than a few of you were hoping this would be resolved fast, well there.. happy now?
3. MTD
4. General cleanup and optimizations have resulted in improved launcher response, it feels more fluid and less laggy...
5. Our repo is nearly finished, we are just ironing out some manifest bugs, when alpha2 arrives, so will our git links!
6. We have chosen a team name! Galaxian-Soup!
Thanks for supporting us, and we look forward to celebrating a "Droid 2012".
In the spirit of openness, if you would like to use our rom in your work please credit us in your OP and release notes. Our git repo should be up soon.
***Update*** Xmas Dinner Edition ***
Updated links to a 1.1 version, I added the livewallpaper.apks and re-zipped, no other changes.
and a newer version of Google Apps, seems to be more stable, but I've only been using it an hour, let us know!
Good Morning and Merry Christmas!
Is there something in your stocking for your GT7310? Well Santa Clause (in the form of _Motely, nycbjr, poisike, termleech (still need a team name!)) is delivering the first public alpha!
This build has been tested on the 7310 (Gtab 8.9 wifi, no 3g), and 7300 with no 3g (3g is being looked at).
Standard YMMV tag: You are flashing this at your own risk, make a nandroid backup first! If this breaks your tab we are NOT responsible.. now go play and have fun!
ICYXMAS-p5wifi-alpha1.1-cwm
icyGapps V2
Alpha V1 - ICYXMAS!
ICS 4.0.3_r1 vanilla
Rooted, deodexed,
Includes motley kernel v2e beta (see his thread for git details)
WiFi, GPS, Bluetooth
Installation:
In CWM recovery, clear your data/factory reset
Clear the dalvik cache (under advanced, or under the wipe menu in overcome cwm)
Flash the provided zip using CWM recovery
Flash gapps from CWM recovery
Bootup and setup your Google account
Install cpu control of choice, and set to interactive governor (this is required!)
*tested SetCPU, No-frills CPU control, and Antuantu.
Give it a chance, this is a deodexed ROM and will boot slow the first time and when you use apps the first time.
Doesn't work/Limitations:
WiFi-only, but 3G will be looked at for a future version (no ETA at the moment)
Camera doesn't work, don't know when or if it can be fixed.
Some video limitations, youtube HD vids not working. Some stuttering will occur until we get the kinks out.
Charger screen doesn't look correct when you plugin without booting up (charging status)
Voice search doesn't work - May have something to do with this error:
W/PackageManager(257): Failure retrieving resources forcom.google.android.voicesearch: Resource ID #0x0
Probably more that we haven't listed, this is an alpha - please let us know.
Team members:
nycbjr - project manager, dev (first working build), testing/troubleshooting
motley - lead dev, p5 device tree, final build, kernel development
poisike - pioneer testing with other tegra ICS ROMs, testing/troubleshooting
termleech - testing
Credits:
Google - for the releasing the OS
Cyanogen Mod Team - for their awesome git repo and developers. We used the p4 device tree as a starting point.
We would like to offer our p5 device if they are interested.
Samsung for the awesome device and kernel source (for HC 3.1 at least)
digetx - for pointing us in the right direction on the green frame buffer fix!
alterbridge - for his CWM Recovery port for 73xx.
JaeCar99 - for the sweet "Blue Hallway" bootanimation
I'm looking forward to a fully working ICS rom But a good thing takes time. Keep up the good work, guys!
great to see this development start
Sent from my HTC Incredible S using Tapatalk
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
termleech said:
Do you guys want some help? I'm currently working on a rom for the nexus with some other guys but could lend a hand here as well. What's the best way to get a hold of you guys?
Sent from my Full AOSP on Maguro using Tapatalk
Click to expand...
Click to collapse
I would never turn down any help, I'm very new at this (long time sysadmin, but only been a droid head since march hah).
Only caveat is you will need approval from motley before I can release anything to you, for now you can PM me and I will give you my aim/gchat and offline email, but I think we should setup an IRC, or aim/gmail chat to make this go faster.
As this is coming from CM9 sources I need to contact them too, I don't want to flub any licensing issues, etc, and maybe they will want to help, or us to help them!
Awesome! Thanks fellers!
great work
_motley said:
As far as WiFi, the P4 (Galaxy 10.1) uses a broadcom 4329 and we (the P5) uses the newer 4330. This is where the challenge will come it. When I get a better look at the Android code and have a flash up and running, hopefully it will become clear if something needs to be done on the kernel side or the Android side. If we start making good progress, we will need to get a git setup for our P5 stuff so we can share changes and files etc.
Click to expand...
Click to collapse
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
this is awesome guys.. after the posts yesterday and staying up till 3:Am , I got the sucker booting.. of course that was it though. Great to see this post today.. Sounds like it's not too far off.. at least for me wifi would be the only thing left that's important since I havent touched the camera app or bluetooth yet.
poisike said:
I don't know... I just flashed my P7300 with P7500 rom and wifi driver loads just fine. I only edited the build.prop and used a kernel from overcome rom, i didn't touch anything else. Also if you look in \system\etc\wifi you will see that both 7500 and 7510 roms have bcm4330 files there, so it looks to me that the wifi card is the same as our.
I also tried the kernel you sent me with 7500 rom and wifi driver still loads.
Click to expand...
Click to collapse
right, I'm going back over the source, and the board config, some wifi stuff seems commented out. I know I need to get on irc.. but work interjects lol..
for the record on linux to use broadcom it has to extract the firmware for the card, I don't think it has to for droid as in this case the firmware is provided to us. I should probably stop spinning my wheels and go back and read/learn more about how android treats these things.
I am all ears however, anyone with debugging exp can have the rom with permission to use the kernel from motly.
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
ok thanks I was looking at the source on my build system remotely, and the drive went oiffine, I think my ssd is going, so I'm going to get a new on on the way home. pisses me off!
Great work!
I'm seeing forward to try this out.
Gesendet von meinem GT-P7300 mit Tapatalk
poisike said:
I don't think that the problem is in your build. I have tried 3 different builds and they all have the same error:
Code:
ERROR/WifiStateMachine(168): Failed to load driver!
ERROR/WifiStateMachine(168): DriverFailedState
So it looks to me that the problem is in kernel. Of course i could be wrong.
Also it looks to me that the bcm4330 driver source is posted on github (https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/net/wireless/bcm4330), so i hope _motley finds time to take a look.
Click to expand...
Click to collapse
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Well other than the green screen affect, wifi, camera,bluethooth this thing really runs well.
HC was a pig for memory, as I noted on my Acer when I ran ICS for a bit, memory mamagment is hugely improved over honeycomb, I never had more than 200mb free on a regular basis, with ICS its well over 400mb.
and the thing really cooks along, I snap in and out of screens really fast, and angry birds works! haha
I will spend some time tonight on wifi, and making a new build.
poisike I'll setup irc tonight, I may have to rebuild the macpro, who knew running an os other than apple would cause a problem lol..
_motley said:
Sorry, I misspoke, the 10.1 does indeed use the 4330 like us...been looking at Iconia, Xoom, and ASUS TF1 ROMs too much lately.
Click to expand...
Click to collapse
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
This is great news!! Once the wifi is working, I'll be using this as my daily driver. Will this be a completely AOSP project or still based on TouchWiz. I wish I could have stock e-mail, calendar, etc.
Excellent news! I will be waiting patiently....
Asop only! "Don't wiz on my ICS"
Sent from my SGH-I777 using xda premium
nycbjr said:
The otapackage build does spit out a file called "kernel" would that help you any?
I can drop it in my dropbox
actually there is a boot.img.cm9 in my alpha zip you have, but I can still upload just the file called kernel if yoi think it would help.
also once I have my macpro back in op I'm not against setting up accounts for you and poisike, or setting up our own git repo, would be beneficial to work against the same source once we zero in and attempt to create a working port for everyone.
oh and btw, your OC settings work, running ICS at 1.4ghz
Click to expand...
Click to collapse
That sounds like it is just the zImage binary for their build, I think I remember seeing it there too. It won't do me any good. Sounds good about the repo. I can still browse the repos to look at code as necessary for the time being. Glad to hear that the OC is is still working good.
I just sent poisike a 3G kernel with the touchscreen fix so he can start working on that end.
"Don't wiz on my ICS!" haha
CyanogenMOD 9.0 by TE4M NOW MTD!!!!!![4.0.4]
dear all,
this thread is created to seperate non development post inside the cm9 development thread and to keep it clean.
WHAT CAN BE POSTED HERE?
-Related to cm9.0
-problems during installation
-Possibilities of bugs
-All the noob questions
WHAT should not be posted?
-thanks,thank you....
-please do not report SAME BUG
-Do not report if you are downloading new release (just download it and report bugs only)
CM9.0 THREAD
http://forum.xda-developers.com/showthread.php?t=1385153
HUMBEROS UPLOAD AREA
http://www.humberos.com.br/p/android-ics.html
GREAT NOW WE HAVE OFFICIAL NIGHTLIES
GSM- http://get.cm/?device=p1
CDMA- http://get.cm/?device=p1c
PEOPLE BE CAREFUL!!!!! NOW BUILDS ARE MTD (FOR MORE INFORMATION LOOK AT POST 2)
hit thanks if i helped you
Installation guide
PEOPLE NOW BUILDS ARE MTD!! FILE SYSTEM BE CAREFULL
FOR INSTALLING MTD BUILD IT IS [MUST] COMPULSORY TO RESTOCK[ FOLLOW TILL STEP 3]
DONOT!!!!!! RESTORE ANY OTHER BUILDS ON MTD BUILDS
IF WANT TO GO BACK TO GB RESTOCK IS AGAIN NEEDED!!!
1)RESTOCK to gingerbread by following overcome method
www.teamovercome.net
2)flash the overcome kernel 4.0 to convert the system to ext4 from the above website
3)DOWNLOAD ANY ANY BUILD [OFFICIAL NIGHTLY OR SOMEONE ELSE BUILD]
4)copy the zip to tab and then reboot into recovery
5)wipe data,cache and dalvik cache
6) a) if MTD build once u flash them mtd zip it boots into mtd recovery and U HAVE TO FLASH THE ZIP AGAIN
b) if NON MTD just flash the zip
7)reboot!!!!
What doesnt work (19-04-2012-build)mtd
tv out
minors
external sd as sd-ext
gps (unconfirmed)
ums
Any chance of p1000l owners can have the TV mobile apk working? I've been trying to restore it with titanium and I have not been able to restore it.
By the way, anyone having low battery time?
Hatori28 said:
Any chance of p1000l owners can have the TV mobile apk working? I've been trying to restore it with titanium and I have not been able to restore it.
By the way, anyone having low battery time?
Click to expand...
Click to collapse
titanium backup not working on the build
The new update seems to eliminate the software keys; is there a way to reenable them?
Don t agree just wipe everything and restore user app with Tb. Works fine however i think it s a bad idea do such about system/data.
Sent from my GT-P1000 using XDA App
ronak.super said:
titanium backup not working on the build
Click to expand...
Click to collapse
If you haven't already done that, update your TB, the last version works on ICS.
I've been really enjoying this build. Thanks alot for the whole team!
UI runs very smooth and basicly no log at all.
Almost everything works better compared to the orginal 2.3.3 stock rom I used before.
Few things I noticed, the battery life seems to be somewhat worse.
Also a question about the multitasking in ICS. I cant find a way to open the thumbnails? Long pressing home doesnt seem to work and since theres no software based keys (which I think is a good thing) I'm not sure what to do.
Tab P1000 and I'm using the latest kerned (30.1) with bt fix and rom.
Medikay said:
The new update seems to eliminate the software keys; is there a way to reenable them?
Click to expand...
Click to collapse
in build prop set
setprop persist.tablet.hidehome 0
setprop persist.tablet.hiderecent 0
setprop persist.tablet.hideback 0
Graven-eof said:
I've been really enjoying this build. Thanks alot for the whole team!
UI runs very smooth and basicly no log at all.
Almost everything works better compared to the orginal 2.3.3 stock rom I used before.
Few things I noticed, the battery life seems to be somewhat worse.
Also a question about the multitasking in ICS. I cant find a way to open the thumbnails? Long pressing home doesnt seem to work and since theres no software based keys (which I think is a good thing) I'm not sure what to do.
Tab P1000 and I'm using the latest kerned (30.1) with bt fix and rom.
Click to expand...
Click to collapse
dude undervolt your settings using voltage control for better battery im getting the same battery which i used to get in gingerbread
ronak.super said:
in build prop set
setprop persist.tablet.hidehome 0
setprop persist.tablet.hiderecent 0
setprop persist.tablet.hideback 0
Click to expand...
Click to collapse
Sorry for the noob question...but how do you access that?
build.prop file /system/buil.prop
Sent from my HTC Desire using XDA App
Medikay said:
Sorry for the noob question...but how do you access that?
Click to expand...
Click to collapse
use root explorer go to system and then hold the build.prop and open in text editor
hit thanks
Hi all, this thread is a good idea, it mostly works on the galaxy s 2 cm9 forum but their are still idiots posting in the development area. Codeworx (the developer on s2 cm9 thread) has really bought into it and tells people to post in the discussion thread if they post noob stuff in the dev thread. If the devs here (cdesai, humberOS etc) buy into this discussion thread then maybe more people will use it
Anyways, i tried changing lcd density to 120 to check out more tablet apps on the market but when I do the keyboard zooms and I can only see half of it, so I can't type properly... Any ideas?
Sent from my GT-I9100 using Tapatalk
biffroy said:
Hi all, this thread is a good idea, it mostly works on the galaxy s 2 cm9 forum but their are still idiots posting in the development area. Codeworx (the developer on s2 cm9 thread) has really bought into it and tells people to post in the discussion thread if they post noob stuff in the dev thread. If the devs here (cdesai, humberOS etc) buy into this discussion thread then maybe more people will use it
Anyways, i tried changing lcd density to 120 to check out more tablet apps on the market but when I do the keyboard zooms and I can only see half of it, so I can't type properly... Any ideas?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
set density to 160 it works fine becoz in 120 it becomes damn small and same the market page bcomes small when oriented horizontal
ronak.super said:
set density to 160 it works fine becoz in 120 it becomes damn small
Click to expand...
Click to collapse
I know that I used the honeycomb alpha at 120 and liked it that small. But my question isn't about the best density to have, it's about the keyboard at 120 and if anyone knows how to fix it or has any suggestions.
This is my GalaxyTab. There are many like it but this one is mine.
If, by some kind of freak occurrence I helped you, please hit THANKS!
my keyboard work fine on 120 check the attachment
It would be awsome if there is such way to force apps to start in tablet UI with 160 LCD density coz 120 is very small for 7" displays
CM9 on P1000
Hey guys, I tried to flash the latest ICS build for the P1000, but my tablet wont leave the start up screen...
I downloaded both files, replaced the kernel part of the zip with the one specific for the P1000, wiped cache, davik and reset user settings.
Then I flashed the zip file, but at reboot it won't leave the start up screen.
Any idea on what I may have done wrong?
Thanks!
:::::::... Kernels & Recoveries for || 4.4.x || KitKat Builds...::::::::
With:
TWRP Recovery
or
CWM Recovery
Devil Kernel
or
AOSP || CM Based Stock Kernel
...……………………………
...……………………………
Important...
DO NOT MIX
A 4.4.X Kernels to 4.3.x, 4.2.x, Etc. ROMs
...……………………………
...……………………………
from the hard work of Recognized Developer - DerTeufel1980
and those continuing to use his kernel mods
I have only put them into a standalone flashable .zip package ... Enjoy
I take no responsibility if it messes anything up,,,, these work for me or I dont post them ,,, ,,,, make backups,,,, nandroids,,, whatever you favorite choice is...
be prepared to potentially wipe, if it wont boot and you can get back into recovery,,, but worst case scenario you will have to ODIN back to stock EH03 and start fresh ...
:: If anyone needs a kernel I have not done up yet shoot me a reply or PM ::
Information and Compatibility
>>>>> >>>> >>>
Android 4.4.x
These Kernels/Recovery are interchangeable across AOSP/CM/OMNI/PA ROMs ,,, {{ So feel free to mix & match accordingly }}
General method of installation:
from Recovery:
Install Zip
Reboot
Enjoy
these zips allow a Rom to boot into chosen Recovery/Kernel combination - including all other Devil Kernel tweaks with programs like the ones below
With some ROMs offering nightly builds sometimes these may not work with the newer nightly ROM builds, just depends on what gets changed.
Just head the warnings and be prepared for possible incompatibility.
Tweaks --- Over Clocking and Kernel Control Programs --
>>>>> >>>> >>>
Devil Kernel Memory Tweak Options
-- 383mb -- Stock
-- 396mb -- XL -- No known issues
-- 408mb -- BigMem -- (Breaks only 720 Video Recording, 480p Video still works fine)
-- 439mb -- Max Ram -- No Camera [picture or video] at all -- [your memory may vary]
...........................................................
...........................................................
Some of the more popular programs if your included one lacks some features
>>>>> >>>> >>>
DevilTools by: DerTeufel
DevilTools-1.1.2.apk :: http://forum.xda-developers.com/attachment.php?attachmentid=2453825&d=1387010535
http://forum.xda-developers.com/showthread.php?t=2276036
Devil Kernel Manager
DevilAppSGS.apk
http://forum.xda-developers.com/showthread.php?t=2558082
https://play.google.com/store/apps/details?id=com.metalignus.devilappsgs&hl=en
Trickster MOD
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
ROM Toolbox Lite is excellent with the stuff available in it...
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&feature=search_result
I also found this nice Lulzactive controls app
specifically for the Lulzactive Governor and explains things nicely
https://play.google.com/store/apps/details?id=com.tegrak.lulzactive
>>>>> >>>> >>> >>>>> >>>> >>>
My Personal Favorite KitKat Devil settings are
100 Mhz CPU Min
1000 Mhz CPU Max
Zen - I/O Scheduler
Lulzactive - Governor || Smooth Ui = Off ||
Live O/C = 120% || OC Target Low = 1000 Mhz || OC Target High = 1000 Mhz ||
with that setting it it overclocks only the 1000 Mhz to = 1200 Mhz [ I still keep good battery life ]
[ Live OC has the benefit of also OCing the GPU, from 200 -> 240 Mhz @120%]
[ I also up the 1000 Mhz CPU Voltage setting +25 mV = 1300 mV, seems to help stability ]
396mb Memory
Zram 40%
Swappiness 80%
and SD read ahead 1024
Dirty Tweaks - Build Prop Mods::
PM Sleep Mode = 1 [Power Collapse (Best)
Wifi Scan Interval = 1500 [1st set to anything 15-420, then manually edit build prop]
dalvik.vm.heapstartsize = 12m [manually edit build prop]
......................................................................................................................
......................................................................................................................
I take no responsibility if it messes anything up,,,, these work for me or I dont post them,,, ,,,, make backups,,,, nandroids,,, whatever you favorite choice is...
be prepared to potentially wipe, if it wont boot and you can get back into recovery,,, but worst case scenario you will have to ODIN back to stock EH03 and start fresh ...
::KERNEL LINKS::
Fascinate - 4.4 Kernels
My 4.4 Kernels Link ~ thanks AndroidFileHost.com
~~~ clickable Link ~~~ https://www.androidfilehost.com/?a=show&w=files&flid=9626
--- New links show up in these first, before the "Direct Links" get posted
……………………………………
……………………………………
:: KERNEL Direct Links ::
:: :: 4.4 Kernel :: ::
Do not mix 4.4.x Kernels with 4.3.x and Earlier ROMs
2.1-cm11-4.4__TWRP_11-10-2013-fassy.zip
http://www.androidfilehost.com/?fid=23212708291679682
Made from:: [4.4] Unofficial CyanogenMod 11.0 || By: Unjustified Dev || http://forum.xda-developers.com/showthread.php?t=2521427
TWRP - Stock Kernel
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
Made from:: DIRTY UNICORNS[4.4.2][v5.0][OFFICIAL][TWRP 2.6.3.0][12-29-13] || By: BDogg718 || http://forum.xda-developers.com/showthread.php?t=2591794.
TWRP - Devil Kernel
3.1-kernel-cm11_cwm_4.4.2_01-04-2014-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202535
Made from:: [4.4.2] Unofficial CyanogenMod 11 [1/4/14] || By: times_infinity || http://forum.xda-developers.com/showthread.php?t=2598051
CWM - Stock Kernel
3.6-cm-11-unjust-kernel_cwm-6.0.4.9__06-04-2014-fassy.zip
http://www.androidfilehost.com/?fid=23501681358551286
Made from:: cm-11-20140604-UNOFFICIAL-fascinatemtd
CWM - didhiys kernel-by unjust
…………………………………………………
…………………………………………………
::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::
Credits:
BDogg718, Dirty Unicorns, Unjustified Dev, DerTeufel1980, Notta, AOSPA, Mazda, Cyanogenmod, PacMan Rom, jt1134, AOSP, Omni Rom, LasVegasRomeo, times_infinity, other developers, users, supporters and anyone else that has helped out!
::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::
.
@hhp_211. Can you marry a Devil kernel with a cwm 6046 to try on the cm11 1/09 ROM? Is it a big project or is it pretty easy?
kb8no said:
@hhp_211. Can you marry a Devil kernel with a cwm 6046 to try on the cm11 1/09 ROM? Is it a big project or is it pretty easy?
Click to expand...
Click to collapse
I hope in the near future to be able to these type of things,,, still learning it.
What issues are you having?
Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.
They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)
.
hhp_211 said:
I hope in the near future to be able to these type of things,,, still learning it.
What issues are you having?
Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.
They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)
Click to expand...
Click to collapse
It took me a long time to figure out how the kernel and recovery worked on this device and re-learned it several times til it sunk in but now I get it.
I got all those media errors with twrp/Devil. Maybe the SD card trick you proposed will fix that. Then I got some crashes and no sounds worked so I bailed.
My assumption was that it was twrp and not Devil. The dev in his OP is very particular about using cwm on his ROM. I don't know why they both shouldn't work as long as you have the right ones. Seems that is how it works in other ROMs. Dev called the recovery issue a "debacle" I believe and sounded frustrated. There should be a story here. Why wouldn't twrp flash ROM?
So that's why I'm thinking Devil/twrp is an issue. Have you tried it?
kb8no said:
It took me a long time to figure out how the kernel and recovery worked on this device and re-learned it several times til it sunk in but now I get it.
I got all those media errors with twrp/Devil. Maybe the SD card trick you proposed will fix that. Then I got some crashes and no sounds worked so I bailed.
My assumption was that it was twrp and not Devil. The dev in his OP is very particular about using cwm on his ROM. I don't know why they both shouldn't work as long as you have the right ones. Seems that is how it works in other ROMs. Dev called the recovery issue a "debacle" I believe and sounded frustrated. There should be a story here. Why wouldn't twrp flash ROM?
So that's why I'm thinking Devil/twrp is an issue. Have you tried it?
Click to expand...
Click to collapse
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.
Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.
hhp_211 said:
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.
Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.
Click to expand...
Click to collapse
I can get that. Are you saying first flash is about correct partitioning and not correct recovery? That's a reoccurring Fassy theme! So once it is flashed and partitioned correctly and then the ROM flashed, shouldn't we then be able to use any recovery, like a 4.4 compatible twrp?
hhp_211 said:
My understanding of the "recovery debacle" is the fact up having to go through the exact process is to get the partitioning set correctly.
Much of the the same reason why on @Unjustified Dev cm11 that you had to switch over to a certain TWRP recovery 1st, because he compiled his cm11 with the TWRP.
Click to expand...
Click to collapse
You can expect to to change recovery by flashing boot.img we don't have a recovery partition.
Boot image break down
Boot.img contains
* ramdisk
*zImage/Kernel
* recovery ramdisk
We load recovery from boot due to samsung old partition layout
Kernel is inside boot.img this isn't the issue
The issue is the ramdisk.
Some roms contain their own init.blahblah.rc and without it you will get soft-bricked due to certain things not getting initialized and not everything might work and two your ramdisk also contains your init files flashing an incompatible version will soft brick your device due to some things not correctly getting permission . This is the best I can explain it not really a kernel dev or what not so this is the best info I can provide from knowledge .
Newer phones layout
Recovery Partition is separate meaning you can load any recovery in theory without having to be forced to change the Kernel and all ramdisk files which is not good for this reason I always provided zips for my roms with the option to have twrp or cwm because we can't change recovery separately
Boot partition is separate boot.img and kernel never get touched by recovery which is great because you can have no recovery and it still will boot up.
In theory we can flash just recovery such as that twrp zip but it fails for some odd reason I can't understand . TWRP inject script should allow us to flash recovery ramdisk into boot.img so we can have any recovery we want. I may work on getting it to work but for now my fascinate is soft bricked. Also our boot partition is small twrp isn't always fitting in some roms for this reason I build cwm
Unjustified Dev said:
You can expect to to change recovery by flashing boot.img we don't have a recovery partition.
Boot image break down
Boot.img contains
* ramdisk
*zImage/Kernel
* recovery ramdisk
We load recovery from boot due to samsung old partition layout
Kernel is inside boot.img this isn't the issue
The issue is the ramdisk.
Some roms contain their own init.blahblah.rc and without it you will get soft-bricked due to certain things not getting initialized and not everything might work and two your ramdisk also contains your init files flashing an incompatible version will soft brick your device due to some things not correctly getting permission . This is the best I can explain it not really a kernel dev or what not so this is the best info I can provide from knowledge .
Newer phones layout
Recovery Partition is separate meaning you can load any recovery in theory without having to be forced to change the Kernel and all ramdisk files which is not good for this reason I always provided zips for my roms with the option to have twrp or cwm because we can't change recovery separately
Boot partition is separate boot.img and kernel never get touched by recovery which is great because you can have no recovery and it still will boot up.
In theory we can flash just recovery such as that twrp zip but it fails for some odd reason I can't understand . TWRP inject script should allow us to flash recovery ramdisk into boot.img so we can have any recovery we want. I may work on getting it to work but for now my fascinate is soft bricked. Also our boot partition is small twrp isn't always fitting in some roms for this reason I build cwm
Click to expand...
Click to collapse
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.
kb8no said:
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.
Click to expand...
Click to collapse
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
hhp_211 said:
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
Click to expand...
Click to collapse
I flashed it and as I said I had to revert as did the other guy. Have you used it yourself? Should I try again?
hhp_211 said:
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
Click to expand...
Click to collapse
the only problem with that kernel is getting twrp also. i think it'd be better to be able to flash the recovery/kernel separately, but like UDev said, the kernel/recovery/ramdisk makes it difficult because we don't have a separate recovery partition. unless we do more partitioning of the system/data/cache/datadata and create a separate recovery, but i don't think we can without some major work.. which sucks. we pretty much need to copy from another phone, if it's been done anyway. i know the Nexus s can flash recoveries separately, but i don't know how their partitions are laid out exactly.
kb8no said:
Its so complicated. Thanks so much for taking the time to explain. So how do we get Devil kernel into 1/9 cm ROM with all that confusion? I like twrp but I want Devil so I can get some extra settings.
Click to expand...
Click to collapse
It's only compatible for so long I mentioned why. These boot.img aren't really the the best solution due to changes that make it not compatible please guys go read on what a ramdisk is and what all this stuff is like init and stuff so you can understand why
Part of ramdisk is in system/core/rootdir in source code other parts come from your device tree . It's not like this code stays the same not even in the device tree it needs to be changed to fix things or give permission to new things or initialize things like sensors snd it runs more like wifi , bluetooth , etc. This boot.img was only made to allow you to get on 4.4 since recovery is in boot.img you had no choice due to recovery being incapable of installing new 4.4 since set permission is gone it's set metadata now . Compatibility with this boot.img is broken now and I wouldn't install it.
Sent from my SM-T210R using Tapatalk
---------- Post added at 12:47 AM ---------- Previous post was at 12:35 AM ----------
ztotherad said:
the only problem with that kernel is getting twrp also. i think it'd be better to be able to flash the recovery/kernel separately, but like UDev said, the kernel/recovery/ramdisk makes it difficult because we don't have a separate recovery partition. unless we do more partitioning of the system/data/cache/datadata and create a separate recovery, but i don't think we can without some major work.. which sucks. we pretty much need to copy from another phone, if it's been done anyway. i know the Nexus s can flash recoveries separately, but i don't know how their partitions are laid out exactly.
Click to expand...
Click to collapse
Actually we have one it's just not used due to how the device is made. I think it's a bootloader limitation based on how it was set up. I always imagined it was possible to load recovery there but I don't think the block is active or something to be used it just exists
Sent from my SM-T210R using Tapatalk
Unjustified Dev said:
It's only compatible for so long I mentioned why. These boot.img aren't really the the best solution due to changes that make it not compatible please guys go read on what a ramdisk is and what all this stuff is like init and stuff so you can understand why
Part of ramdisk is in system/core/rootdir in source code other parts come from your device tree . It's not like this code stays the same not even in the device tree it needs to be changed to fix things or give permission to new things or initialize things like sensors snd it runs more like wifi , bluetooth , etc. This boot.img was only made to allow you to get on 4.4 since recovery is in boot.img you had no choice due to recovery being incapable of installing new 4.4 since set permission is gone it's set metadata now . Compatibility with this boot.img is broken now and I wouldn't install it.
Sent from my SM-T210R using Tapatalk
---------- Post added at 12:47 AM ---------- Previous post was at 12:35 AM ----------
Actually we have one it's just not used due to how the device is made. I think it's a bootloader limitation based on how it was set up. I always imagined it was possible to load recovery there but I don't think the block is active or something to be used it just exists
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
I wish there was a way to check to see if it's active without the possibility of bricking the phone. there's gotta be a workaround, but I don't know if that's even possible.
ztotherad said:
I wish there was a way to check to see if it's active without the possibility of bricking the phone. there's gotta be a workaround, but I don't know if that's even possible.
Click to expand...
Click to collapse
it's not made to be active this phone has a mtd partition I have no idea how it's set up but recovery is dead. Just kernel , cache , system , and datadata partitions are active.
Unjustified Dev said:
it's not made to be active this phone has a mtd partition I have no idea how it's set up but recovery is dead. Just kernel , cache , system , and datadata partitions are active.
Click to expand...
Click to collapse
so really that recovery is only activated within the boot.img
ztotherad said:
so really that recovery is only activated within the boot.img
Click to expand...
Click to collapse
Yep that's how it's read. Stock recover is different we had revovery .bin this was made to allow custom ones to work its how it loads it is different from stock. I think that was developed by kush. Brick your phone hard enough you will see cwm4 you installed on stock
Sent from my SM-T210R using Tapatalk
Unjustified Dev said:
Yep that's how it's read. Stock recover is different we had revovery .bin this was made to allow custom ones to work its how it loads it is different from stock. I think that was developed by kush. Brick your phone hard enough you will see cwm4 you installed on stock
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
damn. that just goes with what Adam Outler created "the unbrickable mod" for the fassy. I'd love to do that with my phone and then try and flash a nexus s bootloader/kernel/etc and see if something loads. Hell, I'd even like to try it on my other fassy that is bricked/whatever to see if it fixes it. lol. I just don't know how to use a welder at all.
skepticmisfit said:
helly is still an amazing 4.2 rom. hell I'm running aokp ms6 (ics) right now and it seems to be the only thing that's fully satisfied me as of late.
Sent from my SCH-I500
Click to expand...
Click to collapse
Hey skepticmisfit and others too ,
I've seen you and a couple others prefer the aokp ics ms6 over other newer roms.
What do you feel it's doing that's hands down better?
Also...
What are its quirks?
What do you use your fassy for the most [surfing, gaming, music, mixture, other. ]
Can you list out what bugs you in newer Roms the most
I ask because I've been working hard on some tweaked settings in DU 4.4 that have reality improved the speed and stability for me and they should work for all the 4.4 Roms,,,
And I want to get some initial response to make sure I'm heading on the right path
Hopefully I'll have these tweaks in the next few days.
Whoever is ready or able to test let me know.
————— ————— —————
For me 4.4 has been good overall,,,
The hanging black screen on receiving a phone call has to be issue numero uno! drove me nuts!!!
and very slow at switching tasks ,
and slow looking up anything in the interweb,
Not to mention,, generally within a few hours from a fresh boot will cause a hang/reboot
[ or any semi heavy multi tasking it will happen faster]
So I've put a lot of hours into researching and finding out what certain settings effect and I've compared and made a spreadsheet if settings from ROM's that were popular or considered fast,,, and the results have been extremely positive
.
hhp_211 said:
Hey skepticmisfit and others too ,
I've seen you and a couple others prefer the aokp ics ms6 over other newer roms.
What do you feel it's doing that's hands down better?
Also...
What are its quirks?
What do you use your fassy for the most [surfing, gaming, music, mixture, other. ]
Can you list out what bugs you in newer Roms the most
I ask because I've been working hard on some tweaked settings in DU 4.4 that have reality improved the speed and stability for me and they should work for all the 4.4 Roms,,,
And I want to get some initial response to make sure I'm heading on the right path
Hopefully I'll have these tweaks in the next few days.
Whoever is ready or able to test let me know.
————— ————— —————
For me 4.4 has been good overall,,,
The hanging black screen on receiving a phone call has to be issue numero uno! drove me nuts!!!
and very slow at switching tasks ,
and slow looking up anything in the interweb,
Not to mention,, generally within a few hours from a fresh boot will cause a hang/reboot
[ or any semi heavy multi tasking it will happen faster]
So I've put a lot of hours into researching and finding out what certain settings effect and I've compared and made a spreadsheet if settings from ROM's that were popular or considered fast,,, and the results have been extremely positive
.
Click to expand...
Click to collapse
oh man.. well... specifically with AOKP, it's really stable and really fast a lot of the time. scrolling and opening apps is way faster than in JB and KK roms. gaming is also a bit better too. benchmarks, though they don't usually matter on phones, actually do better with an ICS rom than in JB.
some quirks with AOKP are that built in Wi-Fi tethering doesn't work and that only like two flashlight apps work (I use tiny flashlight). stock torch is broken.
Sent from my SCH-I500
skepticmisfit said:
oh man.. well... specifically with AOKP, it's really stable and really fast a lot of the time. scrolling and opening apps is way faster than in JB and KK roms. gaming is also a bit better too. benchmarks, though they don't usually matter on phones, actually do better with an ICS rom than in JB.
some quirks with AOKP are that built in Wi-Fi tethering doesn't work and that only like two flashlight apps work (I use tiny flashlight). stock torch is broken.
Sent from my SCH-I500
Click to expand...
Click to collapse
you can fix the wifi tethering issue by using Skunk works Glitch (0518 seems to be the only build still on the internet. if anyone has something newer PLEASE SHARE IT!) AOKP comes with IcyGlitch
Sent from my SCH-I500
Q&A for SM-T330NU Rom Development Cyanogenmod 11
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for SM-T330NU Rom Development Cyanogenmod 11. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cyanogenmod 11 sm-t231
Hello friends wondering if there will be a cyanogenmod 11 for the sm-T231 It's my tablet and I love to get away touchwichz If anyone knows of any future project thanks alert
nice
based off aosp? edit- can flash pa gapps?
I have attempted to connect my device to PC with this ROM installed but it fails to install MTP.
halo12lol said:
based off aosp? edit- can flash pa gapps?
Click to expand...
Click to collapse
I have PA Gapps 3-08 running fine on recent Cyanogen Mod 11 port for the T330NU with no issue..
However the PA GAPPs developer (TKruzze) no longer makes GAPPs packages..
If you have the latest PA GAPPs, it should work..
halo12lol said:
based off aosp? edit- can flash pa gapps?
Click to expand...
Click to collapse
Hi, i have included a micro package in OP. Read OP.
wire55 said:
I have attempted to connect my device to PC with this ROM installed but it fails to install MTP.
Click to expand...
Click to collapse
W, hey okay i add mtp to my todo list though i don't own a computer that mtp would actually work on, so it'll be guesswork.
Also now that sound is sorted, i'll take a look at the magnetic cover thingamawhatzit. Though i like to turn my screen
on and off the old fashioned way. :silly:
You folks don't expect too much more, I do have other stuff I have to get to.
m
moonbutt74 said:
Hi, i have included a micro package in OP. Read OP.
W, hey okay i add mtp to my todo list though i don't own a computer that mtp would actually work on, so it'll be guesswork.
Also now that sound is sorted, i'll take a look at the magnetic cover thingamawhatzit. Though i like to turn my screen
on and off the old fashioned way. :silly:
You folks don't expect too much more, I do have other stuff I have to get to.
m
Click to expand...
Click to collapse
Thank you for all your help. I understand you have thing to do, so you do what you feel is more important.
wire55 said:
Thank you for all your help. I understand you have thing to do, so you do what you feel is more important.
Click to expand...
Click to collapse
Sure, i've never had a magnetic cover, the basic idea is closed screen off, and open screen on right ?
also can you test out bluetoothiness, keyboard, i've never done audio streaming so i don't know much to that end.
m
moonbutt74 said:
Sure, i've never had a magnetic cover, the basic idea is closed screen off, and open screen on right ?
also can you test out bluetoothiness, keyboard, i've never done audio streaming so i don't know much to that end.
m
Click to expand...
Click to collapse
If I had a Bluetooth device I would test that for you but I don't have one.
---------- Post added at 04:19 AM ---------- Previous post was at 04:18 AM ----------
And yes the the magnetic cover question. I will do all the testing with that if ya need me to
extra
theme engine working? also want a video of ROM working if u can, thx.
edit - I'm happy to see that there is a person working on the t330nu. that means my money doesn't go to waste
edit 2 - the very much, I'm tired of seeing tricked up stock custom Roms?
halo12lol said:
theme engine working? also want a video of ROM working if u can, thx.
edit - I'm happy to see that there is a person working on the t330nu. that means my money doesn't go to waste
edit 2 - the very much, I'm tired of seeing tricked up stock custom Roms��
Click to expand...
Click to collapse
No videos. This is a high [low] class [rent] operation I'm runnin here. xD
Now here's the kicker, after i get a final decent build, i'm going back to stock. Why?
[ploop] , nuff sed. xD
m
@moonbutt74 hey did anyone else have this problem or just me? When I charge my tablet it goes to 25 percent then it doesn't rise. I wake up in the morning its at 25 I restart and it kicks to 100..
zach61797 said:
@moonbutt74 hey did anyone else have this problem or just me? When I charge my tablet it goes to 25 percent then it doesn't rise. I wake up in the morning its at 25 I restart and it kicks to 100..
Click to expand...
Click to collapse
Z,
hi, i have no issue but, i also maintain my tab regularly with sdmaid, you may need to clear out battery stats.
Also, are you running the rom with or without the kernel update? Lastly how many background processes do you
have running?
m
moonbutt74 said:
Z,
hi, i have no issue but, i also maintain my tab regularly with sdmaid, you may need to clear out battery stats.
Also, are you running the rom with or without the kernel update? Lastly how many background processes do you
have running?
m
Click to expand...
Click to collapse
Ok 1. How do I clear the stats
2. I updated it today
3. Idk how many processes I have running how do I check?
zach61797 said:
Ok 1. How do I clear the stats
2. I updated it today
3. Idk how many processes I have running how do I check?
Click to expand...
Click to collapse
Z,
hi again :silly:
you can run in terminal
ps
also you can also connect via adb and run adb shell, then as root [su] run
powertop
i say to do that one through adb because it doesn't display correctly and is kind of unmanagable in the tab's
terminal window.
Also try modifying you performance settings, on the updated kernel you should be set to ondemand/cfq
m
moonbutt74 said:
Z,
hi again :silly:
you can run in terminal
ps
also you can also connect via adb and run adb shell, then as root [su] run
powertop
i say to do that one through adb because it doesn't display correctly and is kind of unmanagable in the tab's
terminal window.
Also try modifying you performance settings, on the updated kernel you should be set to ondemand/cfq
m
Click to expand...
Click to collapse
Okay thanks and speaking of performance why can't I overclock at all like it kicks it back down?
zach61797 said:
Okay thanks and speaking of performance why can't I overclock at all like it kicks it back down?
Click to expand...
Click to collapse
Umm, because it's not overclocked.
Also skip the powertop approach, i forgot to config in the kernel, i'll get that in the next build.
I know nothing about overclocking, yet.
m
moonbutt74 said:
Umm, because it's not overclocked.
Also skip the powertop approach, i forgot to config in the kernel, i'll get that in the next build.
I know nothing about overclocking, yet.
m
Click to expand...
Click to collapse
Okay thanks looking forward to updates for this rom. Also I was wondering.. For the ROMs for the t530 tabs like the cm12 one they now have. What would need to be done to get it booting... I heard all the ROMs with the same board need is a working kernel.. Idk if that's right but if it is would the kernel for this ROM get the cm 12 ROM booting or does it need a new one?
zach61797 said:
Okay thanks looking forward to updates for this rom. Also I was wondering.. For the ROMs for the t530 tabs like the cm12 one they now have. What would need to be done to get it booting... I heard all the ROMs with the same board need is a working kernel.. Idk if that's right but if it is would the kernel for this ROM get the cm 12 ROM booting or does it need a new one?
Click to expand...
Click to collapse
For the most part that's somewhat true correct, however i haven't bothered because the roms are being packaged with the block setup
as opposed to the tried and true way and i just don't have the patience to unpack that setup and repack it.
To be truthful i think i've gotten addicted to this stuff in a slightly mentally unstable kind of way :silly:
And as such am running multiple projects at once, so if you want to chip in on trying that approach, downoad one of the
sm-t53xx builds, get it unpacked and repacked cm11 style and link me to it, a respectable site, not 4shared or dumbass gator
or any place like that, and i'll see what i can do. my current attempts with bliss keep breaking at camerawrapper issues and gps issues.
m
moonbutt74 said:
For the most part that's somewhat true correct, however i haven't bothered because the roms are being packaged with the block setup
as opposed to the tried and true way and i just don't have the patience to unpack that setup and repack it.
To be truthful i think i've gotten addicted to this stuff in a slightly mentally unstable kind of way :silly:
And as such am running multiple projects at once, so if you want to chip in on trying that approach, downoad one of the
sm-t53xx builds, get it unpacked and repacked cm11 style and link me to it, a respectable site, not 4shared or dumbass gator
or any place like that, and i'll see what i can do. my current attempts with bliss keep breaking at camerawrapper issues and gps issues.
m
Click to expand...
Click to collapse
Id love to waste time to get it working but I'm no developer by any means... I will do some googling and see if I can... I love to waste time on this stuff so thanks for the info I will message u if I am anywhere near successful... If you have any good links to show how to do it it would be very helpful. Thanks
Since buying this Sprint Note 4 I have tried 4 different custom ROM. 1 touch-wiz, and 3 AOSP. My opinion Detux Corp Rom v9.0-Zelfania'sLove is the absolute best in terms of looks, stability, customizing and response. This along with BeastMode-r61-UN7 kernel makes it a perfect combination for a phone that is now 6 yrs old.. . I did have a few issue, during the first few installs, as I have not dealt with a Touch-whiz ROM in a few yrs. Every thing about this Rom is superb. With plenty of customizing, and tweaking, you really do not need to add anything else to make this Rom stand out over the others.. One issue I did have was with viper4Android. With the option to install in Aroma, after installing it would not work like it was suppose to. It would never process or change any aspect of audio that I choose.. Once I Re did the Rom again, after trying a few AOSP, I downloaded the Viper4Android APK separate, along with the preinstalled busybox, it works flawless. Also it was very lagging, and would often be impossible to get it to to anything until it finally settled, but was worth the wait.. Right now nothing of note, is wrong not even Bluetooth, which seems to be a big issue on AOSP ROMS. Even with help on how to correct Bluetooth issue, it would still persist and never work correctly..
Just purchased two ZeroLemon batteries for my Note 4. The original works just fine, but wanted to have extra, for when this thing actually dies.. Of course I will swap out batteries at least once a month, and always have one fully charged and ready to replace, when I'm either at work or out and about.. I did purchase a new original Samsung battery, that was still in it's original box off of Ebay. But when it came, and I charged it and installed it in the phone. The phone would immediately shut off or just reboot.. Battery Man date was Mid 2017, but is defective. So went looking at alternatives, and settled on ZeroLemon as they have a good reputation.. Plus both with free shipping was $30 from their site.. Most aftermarket batteries, you can seem to only buy via Amazon or Ebay.. This is the route I did not want to go, so I'm glade I went to ZeroLemon..
Please can you send me screenshots of this detux corp rom
bahaa66 said:
Please can you send me screenshots of this detux corp rom
Click to expand...
Click to collapse
It's under the Android Development here in the Sprint Forum of the Note 4, along with screen shots.
Dtux rom and screenshots
https://forum.xda-developers.com/note-4-sprint/development/rom-dtuxrom-v5-redemption-t3424993
Dtux rom Original and Dtux rom with GRX touchwiz home V8 .zip added
6
doubledragon5 said:
Since buying this Sprint Note 4 I have tried 4 different custom ROM. 1 touch-wiz, and 3 AOSP. My opinion Detux Corp Rom v9.0-Zelfania'sLove is the absolute best in terms of looks, stability, customizing and response. This along with BeastMode-r61-UN7 kernel makes it a perfect combination for a phone that is now 6 yrs old.. . I did have a few issue, during the first few installs, as I have not dealt with a Touch-whiz ROM in a few yrs. Every thing about this Rom is superb. With plenty of customizing, and tweaking, you really do not need to add anything else to make this Rom stand out over the others.. One issue I did have was with viper4Android. With the option to install in Aroma, after installing it would not work like it was suppose to. It would never process or change any aspect of audio that I choose.. Once I Re did the Rom again, after trying a few AOSP, I downloaded the Viper4Android APK separate, along with the preinstalled busybox, it works flawless. Also it was very lagging, and would often be impossible to get it to to anything until it finally settled, but was worth the wait.. Right now nothing of note, is wrong not even Bluetooth, which seems to be a big issue on AOSP ROMS. Even with help on how to correct Bluetooth issue, it would still persist and never work correctly..
Click to expand...
Click to collapse
I agree, Dtux rom is the best of the best on Sprint Note 4 MM.
https://www.sammobile.com/news/galaxy-store-update-brings-dark-mode-and-one-ui-design/
I didn't expect this to work with 6.0 mm but OMG! Nugut on MM, no way !!! but it did, WoW.
Merry Christmas and happy holidays Doubledragon5
doubledragon5 said:
Since buying this Sprint Note 4 I have tried 4 different custom ROM. 1 touch-wiz, and 3 AOSP. My opinion Detux Corp Rom v9.0-Zelfania'sLove is the absolute best in terms of looks, stability, customizing and response. This along with BeastMode-r61-UN7 kernel makes it a perfect combination for a phone that is now 6 yrs old.. . I did have a few issue, during the first few installs, as I have not dealt with a Touch-whiz ROM in a few yrs. Every thing about this Rom is superb. With plenty of customizing, and tweaking, you really do not need to add anything else to make this Rom stand out over the others.. One issue I did have was with viper4Android. With the option to install in Aroma, after installing it would not work like it was suppose to. It would never process or change any aspect of audio that I choose.. Once I Re did the Rom again, after trying a few AOSP, I downloaded the Viper4Android APK separate, along with the preinstalled busybox, it works flawless. Also it was very lagging, and would often be impossible to get it to to anything until it finally settled, but was worth the wait.. Right now nothing of note, is wrong not even Bluetooth, which seems to be a big issue on AOSP ROMS. Even with help on how to correct Bluetooth issue, it would still persist and never work correctly..
Click to expand...
Click to collapse
Ported kernels of r56 to r61 successfully
Overclocked, hell Yea!!!
Mr. JAVI said:
Overclocked, hell Yea!!!
Click to expand...
Click to collapse
I'll have to give that a try on my day off LOL
doubledragon5 said:
I'll have to give that a try on my day off LOL
Click to expand...
Click to collapse
The Mods .zip available in the link below removes the once alway by default. Let you choose without forcing you to set default app.
https://forum.xda-developers.com/note-4-sprint/development/rom-t3568075
doubledragon5 said:
I'll have to give that a try on my day off LOL
Click to expand...
Click to collapse
Check this out
5DQ15 bootloader and Modem running on a Lollipop custom rom, system root and Samsung theming full functioning as it should.
Cons= camera is blurted but I'll see if I can port or modify the files. Perhaps flash the modified r61/r56 Marshmallow kernel. Experimentation and observation.
Check out SuperSu Pro V2.52
I kept having issues with BusyBox. I finally found where it was pre-installed but it took me a while, I will admit. The Busybox by Steritson or what ever, was showing it was installed to the /sbin/. However, I discovered it was in device/ data/local/ and there it was Busybox. The screen shot is from after I manually deleted it with my root file manager . Yea, I took a bit of a risk but it did fit well with me. It just didn't look right.
Next, I unistalled previous bbox applets from within the app. I rebooted and ran the app to see if all was bbox was removed. a. Tgen I denied it root , forced stoped cleared cache, data and unistalled. nd indeed. I now use l Busybox app to Jrummy. Looks good so far but will see. Anyway, system/xbin for syatem root and syatem/sbin or system/bin for syatemless root.
Mr. JAVI said:
5DQ15 bootloader and Modem running on a Lollipop custom rom, system root and Samsung theming full functioning as it should.
Cons= camera is blurted but I'll see if I can port or modify the files. Perhaps flash the modified r61/r56 Marshmallow kernel. Experimentation and observation.
Click to expand...
Click to collapse
Which Lollipop custom rom?
doubledragon5 said:
Which Lollipop custom rom?
Click to expand...
Click to collapse
Hello my friend, Its good to hear from you. I'm running the Ultimate Note 5 hybrid rom (MOAR). Hears the link if you interested.
https://forum.xda-developers.com/note-4-sprint/development/rom-t3330135
Which kernel did you use? How is your battery life? I never did like battery life with the marshmallows ROMs
I gave it a shot, but wifi doesn't work... So back to UN7
Yea, I never almost never use Wifi but I couldn't get my hot spot to work. Blurred camera, no Wifi and no hot spot. My Bluetooth works. I have an old back from my previous Note 4, I was wondering if I should flash the modem partitions . Freaking fused 5, binary 4 bit the bog one. Dam!!
Im using the besst mode 2.2 ZL by @freeza. I think I try porting the r56 boot.img to the .zip of the R 2.2 ZL kernel zip. I appreciate any input or suggestions @doubledragon5
Mr. JAVI said:
Yea, I never almost never use Wifi but I couldn't get my hot spot to work. Blurred camera, no Wifi and no hot spot. My Bluetooth works. I have an old back from my previous Note 4, I was wondering if I should flash the modem partitions . Freaking fused 5, binary 4 bit the bog one. Dam!!
Im using the besst mode 2.2 ZL by @freeza. I think I try porting the r56 boot.img to the .zip of the R 2.2 ZL kernel zip. I appreciate any input or suggestions @doubledragon5
Click to expand...
Click to collapse
I can care less about hotspot. But if we can get Wi-Fi to work that would be fantastic