Still haven't figure out how to build a kernel from source for the Continuum, but I can still hack the stock kernel to add some functionality to it. Since this stock, you can't expect to much, but I did what I could. I made a few memory management changes to try and get the phone to run a little better. Added a root script that will auto-root the phone on boot, you'll still need the Superuser app if you don't already have it (find it in the market). Also added init.d support for those that have busybox and cleaned up the ramdisk and such a lot. Also, this should enable custom boot animations. Put a bootanimation.zip file in /system/media/ or /data/local/ and it should display when your phone boots up. I had one person test it, and they say it works for them, so I'm hoping it works for everyone else here. Download and flash in CWM.
Download - Custom boot animations and memory management settings
Download - Custom boot animations and stock memory management settings
Download - Stock boot animations and custom memory management settings
Download - Stock boot animations and memory management settings
Sweet. Thank you
Sent from my SCH-I400 using Tapatalk
Just installed. Flawless, so far
Sent from my SCH-I400 using Tapatalk
ChainsDD updated Superuser and the su binary tonight (of course) so I updated it in the kernel. No need to re-download unless you really want to, you can update the su binary via the Superuser app. Download link remains the same, so anyone that hasn't yet downloaded will get the updated version.
So youre saying you have source but dont know how to do it?
sent from my XDA phone - its more than a continuum
nodixe said:
So youre saying you have source but dont know how to do it?
sent from my XDA phone - its more than a continuum
Click to expand...
Click to collapse
The source that "we" have is from the Fascinate/Mesmerize. It has the stuff in there for the Continuum, but the times I have tried to build off of it, the resulting kernel doesn't boot. Not sure if what is there is just incomplete, or if the config is off. Feel free to try and get it working. Use the garnett_03_defconfig (or similar) as the base.
imnuts said:
ChainsDD updated Superuser and the su binary tonight (of course) so I updated it in the kernel. No need to re-download unless you really want to, you can update the su binary via the Superuser app. Download link remains the same, so anyone that hasn't yet downloaded will get the updated version.
Click to expand...
Click to collapse
Since i already had root, bb 1.84 and su installed, i should be good. I'll run su and update the binaries to be safe, though. Thanks for the heads up
Sent from my SCH-I400 using Tapatalk
Uh is there a reason my phone hangs at the Samsung logo after installing this?
EDIT: ...Forget I said that...
yea it will probably take a minute for the first boot since ite rewriting most of the system but after the first one u should be good.
imnuts thank u so much for this u have no idea how bad ive been wanting to get rid of the verizon boot lol
imnuts! thanks allot! You rock! testing now.
Animation works! so far all running good! gonna get some scripts in and let it run!
After installing my phone seems to stall a little on some apps. Like I was listening to music using UberMusic and it would skip kind of like an old CD player. And while I was listening to music I tried to open the XDA app and my phone completely froze. I couldn't open the task manager or anything. Had to pull the battery. With every reboot it seems to get worse
Try setting your cpu min above 400
Sent from my SCH-I400 using XDA App
I had my first ever auto-reboot on the Continuum just a few minutes ago. Brought me back to my days of toying with my Hero. And things do seem laggy since the install.
Guess I'll need to install the old kernel back, if'n it's a separate installable download. Can't remember.
Sent from my SCH-I400 using XDA App
If more people start having issues with it lagging or rebooting, I can undo the changes to the memory management and create a second version then. I used the same settings that I had setup on the Charge, and small hardware differences could make the settings not work properly.
Bierce22 said:
Try setting your cpu min above 400
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
I shouldn't have to
imnuts said:
If more people start having issues with it lagging or rebooting, I can undo the changes to the memory management and create a second version then. I used the same settings that I had setup on the Charge, and small hardware differences could make the settings not work properly.
Click to expand...
Click to collapse
That would be nice
imnuts said:
If more people start having issues with it lagging or rebooting, I can undo the changes to the memory management and create a second version then. I used the same settings that I had setup on the Charge, and small hardware differences could make the settings not work properly.
Click to expand...
Click to collapse
Isn't there a fundamental flaw with memory management in the Froyo builds for our Continuums? I have programs running that load from scratch when I switch back to them all the time. There are games on my phone that I lose all my progress if I switch from the game to anything else. I had the Fascinate and pushed it hard and never observed any of these issues, and I was using a Froyo build on there. As I understand it, the Fascinate and Continuum have basically the same hardware.
Granted, I hadn't had any auto-reboots until this last kernel, but I've had memory issues ever since putting any Froyo build on this Continuum.
I've just held out hope that someone will either release a new rom or find out how to make these Froyo builds run as efficiently as the ones for the Fascinate.
Either way, my Continuum is a more enjoyable phone today than it has ever been before!
I've had two auto reboots since I installed the new kernel and it never happened before
Itvhas to be the changes he made last night. My phone is running fine. Not much snapper, but no issues either
Sent from my SCH-I400 using Tapatalk
Here's the link to the old kernel if you want to revert back
http://dl.dropbox.com/u/20459391/ec07.tar
Ok, I've updated the OP with new download links. The original one is the first download, custom boot animations and custom memory management settings. The second download has the custom memory management removed. The third download has the custom memory management, but retains the stock boot animation, and the last download is stock boot animations and stock memory management.
As for why people may have issues with memory on the Continuum and not the Fascinate, which is the same basic hardware. My guess is that it's due to the ticker. The fascinate doesn't need to have softkey images loaded into memory, or any of the ticker functions/images/services/etc. It may not seem like much, but a few added MBs of memory usage could make the difference people are seeing. I did have a few games on my Fascinate, and now my Charge, that would re-load if I went back to the home screen (Angry Birds and Plants v. Zombies). Hopefully the stock memory settings clear up the issues folks have had. I may also be able to add a few items back in as I suspect the major culprit was the low memory killer settings.
Related
I had DC 3.2.2.1 on my phone and was running into reboot issues occasionally, FC errors, etc. (Not Reeve or DC's problem, I was causing my own issues.) and, considering that my phone is a business phone (with a little pleasure), I used the most current Sprint/HTC RUU and reverted it to stock settings. While Rooted, using AutoKiller and ATK, after boot I had approximately 200-210MB of RAM free since the "Sprint Bloat" had been removed. Now under stock settings, after a reboot, using ATK only, I have approximately 120-130MB of RAM free. I was wondering if there were any sort of non-root-friendly system optimization tools to change the boot settings (such as AutoStarts for rooted devices)... Probably not, but hey, you never know until you ask, right?
Thanks in advance for any help I can get.
Also, I'm aware that the phone is fully functional at 120-130MB free, however, I'm a PC tech and I know that using MSCONFIG to disable most startup entries directly results in a faster boot and a snappier environment, which also happens on Android.
Also, for those curious, I also reverted to stock so I can be ready for the Froyo update the moment it's ready, as opposed to waiting a day or two for a root-friendly 2.2 update to made available...
Alright, a little status update. By uninstalling Google Earth, Adobe Photoshop Mobile, Savvy Shopper, and Tesla LED, my phone now boots up with about 210MB free. I guess Earth and Photoshop are just very memory-hungry programs... Too bad they start up immediately.
Sent Supersonically by my EVO and the super awesome XDA app!
stang5litre_5.0_edition_dev_s5 downloaded and extract why next??
I'm on a galaxy s5 mm6.0.1 build QA1 I rooted my s3 a while back and was looking to do this phone to. Unfortunately I've learned it can't be done yet so I just want to change it somehow ...I downloaded and extracted stang5litre_5.0_edition_dev_s5 but nothing has changed I have the super su app and busy box that it installed but nothing else happened so I'm lost...any ino wold be greatly appreciated
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
swindelljd said:
Ever since I received the upgrade to gingerbread (first 4.06 and now 4.08), Sense will get shut down when I am in other applications. Then when I hit the home button I get the white "HTC" screen and then sense has to start up and reload all my home screens and widgets. It typically happens when I use the browser but has sometimes happens when in other applications.
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
* renice <htc.com.launcher process> -20
* installed Auto memory manager (AMM) and set it to "aggressive" mode
* using AMM reset the priority of "HTC Sense" from 6 down to 2 and specified "always keep alive" but the kernel seems to just reset the priority.
What's really annoying is when I look at the list of processes, things like facebook and weatherbug have a higher (meaning lower number) priority than Sense. Does anyone have any idea how to force Sense to be given priority over other apps so it can stop from being shut down?
tia,
John
Click to expand...
Click to collapse
with any OTA its recommended to do a factory reset. did you do this? its a pain to loss all your data but it might fix your problems.
sorry i didnt have my morning coffee yet.... If you wiped dalvik then that means you have root. your phone is not shutting down. something is killing rosie (the sense launcher.) and that why the white HTC splash screen comes up again. What rom are you runing? i know its the OTA but is it the RUU or one of the devs roms based off RUU??
swindelljd said:
Here are the things I've tried to keep this from happening:
* reducing the number of things on my home screens
* removed all widgets to try and reduce the memory footprint
* factory reset/cleared dalvik cache
Click to expand...
Click to collapse
If you read his entire post you would know he did a factory reset.
My best guess is to go back to stock sense before the last ota (by rooting and flashing or whatever way you wish..sbf or whatever) then download the ota on your computer and try manually updating your phone..if that doesn't work then I don't know
/Droid3
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That worked for me.
synisterwolf said:
... i know its the OTA but is it the RUU or one of the devs roms based off RUU??
Click to expand...
Click to collapse
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
RamAir02 said:
What about bulletproofing the launcher with V6 Supercharger?
Click to expand...
Click to collapse
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
swindelljd said:
Most recently I am running the stock 4.08 version starting with applying the 4.06 RUU and then applying the 4.06 to 4.08 update file. I do have root and really use it for monitoring/managing the /data/data partition.
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
There's no risk of brick with v6. It just tweaked a couple parts of the kernel.
Sent from my ADR6300 using Tapatalk
swindelljd said:
Whoa, that looks pretty serious. I'll have to read that through first so I can understand what it's doing and so I don't accidentally brick my phone.
Click to expand...
Click to collapse
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
RMarkwald said:
You'll just want to make sure you have busybox 1.18.2 installed, then run the script with Script Manager, and you'll want to select either 6 or 7 (I use option 7), then reboot. It won't brick your phone, but you can always run a nandroid backup to have something to fall back to.
Click to expand...
Click to collapse
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
swindelljd said:
Is this the correct script manager app: https://market.android.com/details?id=os.tools.scriptmanager ?
Noob question, how do I check which version of busybox I have installed. I found one in TitaniumBackup that is 1.18.14 but that looks like it is local to TitaniumBackup. I did find "toolbox" in /system/bin which looks like the stock rom's version of busybox. Is this what I should be looking at or is busybox installed somewhere else?
Click to expand...
Click to collapse
Yes, that's the app.
Download this app as well: Busybox Installer
It'll tell you what version you have (if you have it), then you can select what version you want to install. No need to adjust where it installs, just leave that at the default, just select version 1.18.2, then hit Install.
I read through the script just to get a sense (no pun intended) of what it was doing and then installed Busybox 1.18.2 and applied setting 11 "Hard to kill launcher" from the script. I've done a bunch of browsing to sites that normally caused Sense to get shut down and so far so good.
I initially installed busybox with symlinks and it the script threw a ton of errors so I reinstalled with symlinks to fix that.
Thanks for all the help. For completeness, here is a link to V6 Supercharger so all the links are in this one thread http://forum.xda-developers.com/showthread.php?t=991276 .
One thing I did have to change because I am running Sense and not a stock android launcher is the name of the launcher process itself.
On line 64, I changed this "pidof com.android.launcher" to this "pidof com.htc.launcher"
will the V6 script it just tells the android memory system to not reclaim memory from the launcher app so it stays on no matter what happens. only way to kill it is to go to settings and FC the launcher. also with the script you cant brick the phone because its not ran till after the phone boots. The term brick means : that the phone will not boot at all. you just have a phone that does nothing at all not even turn on. You can soft brick the phone meaning the software will not boot. all you need to do is make a backup before installing the script and you will always have a way back if anything happens.
for me i run the beta V6 script option under -=*512HP*=- which is more of a balanced one with bullet prof launcher and its is wonderful. but each phone is different so just try them out and see what works for you.
synisterwolf said:
... You can soft brick the phone meaning the software will not boot. ...
Click to expand...
Click to collapse
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
Yeah, you kinda need that one there!
Good job getting it replaced using adb and all, good to hear you figured it out!
swindelljd said:
I did "soft" brick the phone recently when I deleted build.prop and forgot to put a new one in it's place before I rebooted. Had to use adb to access the phone to restore build.prop. I can tell you that was a nervous few minutes after I realized what I had done. Definitely not a recommended activity.
Click to expand...
Click to collapse
yes that will do it. lol i did that a long time ago when i wanted to edit it my fat finger deleted it. now as good practice i always make a copy of it but add .bak at the end of it so if i do delete it i can just replace it before reboot.
I've been using options 1, 8, and 12 in the V6 Supercharger and my phone has been running great. What options did everyone else choose?
This is for the Galaxy S2 on T-mobile, for the LG Volt StockWalk go here
What this rom is.[/COLOR]
===========[/SIZE]
This a rebuilt stock deodexed rooted base, with some added csc tweaks and build.prop tweaks.
I have also updated the apps to their latest versions and included a couple extra Google apps (keep, and voice). Also included is
Mi FileExplorer, and Adobe Flash.
But this rom will be kept as the stock Touchwiz feel, I didn't like the way it was debloated by some so I decided to do it myself. And
I like the result.
Some of the features added
=================
Flash Player preinstalled and working - Apk Thread Here Thanks to stempox.
Browser has the user agent set to desktop by default
Browser exit option
Browser Bookmarks are editable
Carrier IQ removed (I consider that a feature lol)
Internet tweaks
4 way reboot - Credit to bryan2894
data/app folder for uninstallation of extra apps
proper root and busybox
Removed Preload Folder
data/app support
HD/off screen playback youtube - credit to theos0o
It does not have (yet)
=============
Unrestricted tethering/data cap (coming to a future build, i wanna take my time with smali editing though... its been a while)
Any kernel changes (never will, you can flash your own[I flash Tiberius])
Volume rocker wake (I hate it)
Flashbar (The amount of info on this is dang near nonexistant, so any help would be appreciated)
Issues
====
Starting with 1.1.1 there will be a tag to the right stating which post the release
started on for easy navigation later for people looking for issues in a particular version
Older
1.0.0
I ran into a no boot issue when wiping cache and dalvik cache, and when trying to flash a kernel, I am working on ripping a new base to attempt to resolve those issues, other than that no issues. The new base will be the next build.
1.0.1
superuser broken see post 13 for fix
1.0.3
left some stuff out by accident, skipping.
1.0.4
if google search is missing just download from play store.
1.1.1 post #36 is the release post
Google now settings don't stick, uninstall googlequicksearchbox.apk from system/app , reboot and install from market.
or just clear the data for google search...
Current
1.2.0 (lite) post #57 is release post
over 30 days of stability!!!!!
1.3.0 Updated version of 1.2.0
post #120 is the release post (if using twrp dont fix root)
Instructions
========
DISCLAIMER: I RUN THIS ON MY OWN PHONE AS MY DAILY DRIVER.
BUT I AM NOT RESPONSIBLE FOR BRICKED DEVICES OR SOMEONES
INABILITY TO READ. I WILL HOWEVER DO MY BEST TO HELP WITH
ANY ISSUES...
TWRP IS RECOMMENDED I AM CURRENTLY USING 2.5
-1. have a nandroid backup in case you have issues
0. use the superwipe scripts to eliminate any issues if you need them.
1. Wipe cache, dalvik cache, factory reset and system.
2. Install rom
2.5. If asked to fix root, don't.
3. Reboot
4. Wait for it to boot and have fun (works best if you
wait a few minutes after it boots for the signal to settle,)
If you use CWM recovery please let me know if it works.
Downloads
=========
Older
1.0.0 - Initial build
1.0.1 - Rebuilt base rom
1.0.3 - Uses chainfire su instead (skipped)
1.0.4 - removed boot sound, fixed flash player preinstallation
1.1.1 - Lots of internal revisions and prep for longterm stability. So far 95% stability, one hiccup. see if you can find anything else.
all old links broken and i have no backups of those
Current
1.2.0 - Lite version, no extra widgets, swype, tmemo or extra live wallpapers. (more system memory, no other apps removed.) over 24 hours of stability!!!!!
1.3.0 - update release for 1.2.0 (if using twrp dont fix root)
Changelog
=======
1.0.0 - Initial Release
1.0.1 - The awesome has begun. Totally re-done from scratch in ubuntu with dsixda's kitchen.
after some thorough testing it shows to be more stable and you can flash compatible kernels and tweaks with no issues, after wiping cache and dalvik cache you may have a slightly longer boot
1.0.4 - Uses Chainfire su v1.25, removed boot sound. fixed preinstallation of flash.
1.0.5 to 1.1.1 - Removed preload folder, updated apps, fixed broken apps, did some tidywork on the app naming for future upgradibility.
1.2.0 - slimmed way down to give 77 mb of space on /system compared to 39mb... removed swype, tmemo, some widgets and wallpapers (check screenshots... what you see is what you get.)
1.3.0 - Same as 1.2.0, Updated superuser and about 5 other apps.
Thanks/Credit
============
Koragg618 - 1.0.0 Base
Google
XDA
bryan2894 - 4 way reboot mod
chainsdd - superuser on versions 1.0.1 and 1.0.2
stempox - Adobe Flash apk
Jamison904 - wipe scripts
Powered by SuperSU - on version 1.0.0 and 1.0.3 and up
theos0o - HD Youtube with off screen playback
If you like this rom and want to use it as a base I'm cool with that. Please give credit to those above when you do.
THREAD RULES
============
i have some ground rules i wanna throw out early on so that everyone knows. I know there are rules and guidelines on xda about searching and whatnot before you post blah blah blah.
screw that... in this thread these are my guidelines (xda is total law over these obviously... what a mod says goes...) i suggest.
1. chit chat is cool as long as it semi-pertains to this rom. I've gotten great ideas and suggestions from chit chat.
2. if a total noob asks a total noob question, don't rip his/her ass for it. answer it or stfu and i will answer it. I don't care if the answer was one page back or in the op... be nice about it.
3. suggestions, feedback, and criticism negative or positive is encouraged. ESPECIALLY NEGATIVE CRITICISM. i'm super serious. the whole point of the rom is to rid all of the crap that annoys you.
4. I will always update the OP (original post, first post) whenever there is an update. and while i am working on the rom i update it super often (every few mins sometimes)..
5. eta requests are allowed.. and ill give one... but know that the e in eta stands for estimated.
Screenshots (1.2.0)
==============
Great
Sent from my SGH-T989 using xda premium
Mine....:thumbup:
Sent from my SGH-T989 using xda premium
New build is up. let me know if you find any issues at all. I cant find any yet.
I liked at but I had no play store. Installed an apk but that didn't work either, would just close immediately. That was the only issue I found.
Sent from my SGH-T989 using xda app-developers app
gariputo said:
I liked at but I had no play store. Installed an apk but that didn't work either, would just close immediately. That was the only issue I found.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
try the new build, its completely rebuilt, but as an fyi on the 1.0.0 version the playstore was working for me and phonesky.apk is in the preload folder and updated, along with gmscore and the others. also if you didnt let it settle for a couple minutes that may have been an issue. just try the 1.0.1 and lemme know. im running it now with no issues.
having trouble with superuser not asking for permissions on apps, any suggestions?
thank you for pointing that out. it may be the version of superuser, im gonna try another one and get another build out tonight.
NerdmastaX said:
thank you for pointing that out. it may be the version of superuser, im gonna try another one and get another build out tonight.
Click to expand...
Click to collapse
cool, i will wait, like you i hate volume rocker wake, at least on this phone...lol
edit: if its not to much to ask or i can do it when downloaded, but i also dont like on, off sound but if you do thats cool i can do it...thanks for the hard work and reply
yeah n/p ill remove the startup sound this go round, im deodexing again with the kitchen but this time im rooting with chainfire instead of chainsdd. manually replacing the superuser.apk and su binary fixes the root issue, i still want to let it finish deodexing the new build for that fresh build taste though. his superuser asks for an update on boot tho in the play store, so im gonna bundle it in so it doesnt ask.
NerdmastaX said:
yeah n/p ill remove the startup sound this go round, im deodexing again with the kitchen but this time im rooting with chainfire instead of chainsdd. manually replacing the superuser.apk and su binary fixes the root issue, i still want to let it finish deodexing the new build for that fresh build taste though. his superuser asks for an update on boot tho in the play store, so im gonna bundle it in so it doesnt ask.
Click to expand...
Click to collapse
sweet, Thank You, i will be waiting then report when all set up so you know whats going on...more info for you the better
this may fix your superuser issues for now while i work on the next build. i wanna do the tethering while i have the rom on the bench again.
NerdmastaX said:
this may fix your superuser issues for now while i work on the next build. i wanna do the tethering while i have the rom on the bench again.
Click to expand...
Click to collapse
if you want i can try that or i can wait no biggie to me, let me know
Hmmm, flashed the latest and still no Play Store. I am also not able to add a Google account. I waited 15 minutes after flashing. I am using Clockwork Recovery. I get stuck on the boot screen us TWRP. I did the appropriate wipes before flashing and cleared caches after.
gariputo said:
Hmmm, flashed the latest and still no Play Store. I am also not able to add a Google account. I waited 15 minutes after flashing. I am using Clockwork Recovery. I get stuck on the boot screen us TWRP. I did the appropriate wipes before flashing and cleared caches after.
Click to expand...
Click to collapse
4.1.2 is havinf trouble when wiping caches afterward, either dont wipe or use the cache wipe file from Jamison904. i dont wipe after flash anymore now...hope this helps
here is the link to it...http://forum.xda-developers.com/showthread.php?t=2235141.
just a helpful pointer if you think it gets stuck after wiping cache on twrp, it stays on the end of that loading bar what seems like forever but eventually does boot, so try giving it a little time, you may be thinking its stuck when its not. shouldnt take longer than 5 mins though.
btw new build is uploading now. root and flashplayer are working.
edit.... please read second post, the wipe scripts should solve our issues.
if i'm on ICS stock rooted, can i flash this in TWR to switch on over to JB?
850Mda said:
if i'm on ICS stock rooted, can i flash this in TWR to switch on over to JB?
Click to expand...
Click to collapse
i would reccomend you flash the newest radio beforehand for no issues (radios can be found here) UVMC6 should be at the top, also be sure to nandroid a backup first.
(note, im not certain if the radio is required, but its the way im using it, perhaps someone can clarify.)
Also... New build up... this should be the one to rule them all, very careful tweaking from here on out. please let me know of any issues you can find, also be mindful of how you wipe due to the symlink partition (read post 2)...
that being said i wiped normally even after flashing a kernel and i am not having any issues other than having to log into my google account again. and thats only when i wipe through twrp. but it does boot regardless if you wait. using the scripts should eliminate that problem though.
reflashed after downloading from my dev host link through the phone and i can flash dalvik cache and cache just fine again through twrp. so this is looking very promising and should turn out to be a stable base.
installed just fine, setup went good has superuser..set up to my liking now, using tiberus kernel with kernel tuner set both cores to max=1836 min=192, smartassv2, scheduler=row, and sd to 4096..only have internal sd so ( dont know if that matters but placebo effect makes me think it does...lol )......no volume rocker wake=awesome...no boot up or shut down sound=awesome.....steup screen to 220 density.....rebooted into TRWP recovery wiped cache/dalvik cache using Twrp advance wipe option installed miui player, s-voice, and transparent accuweather widget...running smooth and fast, wifi calling works...will report back after some more time but for now running great...awesome work, Thank You for the hard work!!!!
Hi,
Since i can't post in the thread, so I just highlight in here.
I've been using this rom for about a month. This rom is really nice but since the new update, it gets even better. Only one small thing, the LED flashlight widget in the quickpanel didn't show up although you have tick it in the settings.
That's all. I hope someone could tell this to Spizzy01 so that he can fix this.
Thanks...
matfai said:
Hi,
Since i can't post in the thread, so I just highlight in here.
I've been using this rom for about a month. This rom is really nice but since the new update, it gets even better. Only one small thing, the LED flashlight widget in the quickpanel didn't show up although you have tick it in the settings.
That's all. I hope someone could tell this to Spizzy01 so that he can fix this.
Thanks...
Click to expand...
Click to collapse
Most probably Spizzy01 has removed the flashlight because there is a bug with camera !!
Really?? Well, I didn't know that....
Thanks for a fast reply...
Swipe to move switch icons? No, havent listened...
Aurora Play Problems
Hello,
I just installed Aurora Play 1.1.0 and I am having problems which I think might be related to superuser.
The Rom works fine, but anything that requires root access gets frozen in place. My phone is rooted, I am pretty sure of it - not only the bootloader is unlocked but also, I did manage to initially change the clock speed to 1.4 ghz, and that change has remained so far.
However, if, for example, I try enabling root access on the ES File Explorer, it simply freezes the app (sort of like it is waiting for the confirmation from Superuser, but it never comes). I only ever saw the superuser authorization screen once when I changed the clock at first.
I am pretty sure the OC is not the problem, since I reinstalled the rom and did no OC on the 1st time at all, but the same problem persisted.
I would try uninstalling SU and installing that other superuser app on the market to see if that would solve the problem, but I couldn't manage to uninstall it.
Any thoughts on this? I would love to solve this problem since this room is outstanding on all other accounts.
PS.: I followed all instructions to the letter, and like I said I tried reinstalling the rom already. I am using Lupus v10 (tried Lupus v11 before on the 1st installation).
Fenrir007 said:
Hello,
I just installed Aurora Play 1.1.0 and I am having problems which I think might be related to superuser.
The Rom works fine, but anything that requires root access gets frozen in place. My phone is rooted, I am pretty sure of it - not only the bootloader is unlocked but also, I did manage to initially change the clock speed to 1.4 ghz, and that change has remained so far.
However, if, for example, I try enabling root access on the ES File Explorer, it simply freezes the app (sort of like it is waiting for the confirmation from Superuser, but it never comes). I only ever saw the superuser authorization screen once when I changed the clock at first.
I am pretty sure the OC is not the problem, since I reinstalled the rom and did no OC on the 1st time at all, but the same problem persisted.
I would try uninstalling SU and installing that other superuser app on the market to see if that would solve the problem, but I couldn't manage to uninstall it.
Any thoughts on this? I would love to solve this problem since this room is outstanding on all other accounts.
PS.: I followed all instructions to the letter, and like I said I tried reinstalling the rom already. I am using Lupus v10 (tried Lupus v11 before on the 1st installation).
Click to expand...
Click to collapse
Please try downloading the following ZIP and flashing it VIA clockwork mod.
Let me know the results.
http://forum.xda-developers.com/attachment.php?attachmentid=1890140&d=1366191665
Spizzy01 said:
Please try downloading the following ZIP and flashing it VIA clockwork mod.
Let me know the results.
http://forum.xda-developers.com/attachment.php?attachmentid=1890140&d=1366191665
Click to expand...
Click to collapse
Can CWM coexist with TWRP? I think I only have TWRP installed. Or can I just use TWRP instead?
missing pixels in landscape app drawer
Spizzy, first and foremost congratulations on this great rom, it is fantastic! The only gripe I'm having is that when the app drawer is in Landscape mode it is cutting some pixels on the bottom (can't see the lower end of the blue highlight when using the ps controls). Other than that, all is perfect so far.
It worked!
Thanks a lot, Spizzy! Whatever that package was, it worked great and now superuser is not giving me any headaches anymore. Everything works great and the rom is blazing fast!
Just one thing - when I checked the info that comes up on the pachage before installing it, it said it was for locked bootloaders, but I assume that was a typo (since the zip file is for unlocked, and mine is unlocked as well). Just mentioning since it could maybe cause a little confusion on people downloading it in the future.
Oh and I did use TWRP in the end - I guess it's the same thing.
Hi all, I am certain others are having this problem, but I couldn't find any threads about it.
Does anyone know how to get a reboot widget to work? I used to keep Quick Reboot on my home screen just to have easy access to recovery and other stuff. Since the Lollipop update, none of the reboot managers on the play store work.
Anyone know of a work around or alternative?
Is your phone rooted, from what i understand the app you're referring to or any like it requires it. If you are rooted most any custom rom will have the boot menu your looking for just not as a widget.
Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk
samep said:
Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.
pinetreehater said:
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.
Click to expand...
Click to collapse
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk
samep said:
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.
pinetreehater said:
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.
Click to expand...
Click to collapse
I got some ideas just slow going setting up a fresh ROM. For stock, I had a highly customized setup, look and feel but everyone's preferences are not alike so I can't complain. Even with Titanium and TWRP tar to pull from, I had system customized too. I've got apps and lib folder to edit; some to copy over and some to delete. Keyboards have got to go; back to custom Swype with top number row and directional left right arrows. There's always the nandroid to restore but I'll try to set this up for a backup.
I'll chime in if I figure it out. Maybe just a matter of time. Not out of ideas yet. If someone has a solution, chime in.
Sent from my SM-N910P using Tapatalk