704 replies to this topic

[TeamSpeedCore]

I just tested the new safestrap with TSC roms. Works amazing! I love the new safestrap. Makes testing WAY easier.

[alchemist]

I can confirm that Cyancore 1.2 works just fine on SS 3.04. The new Safestrap is awesome!

[Sgerena]

Hey guys need some help, ive installed the newest safestrap and i have followed the Op for the install but all i get on start up is a black screen, it vibrates really quick and gets stuck on the black screen, any ideas on what could be wrong? thanks

ROM: CYANOGENMOD 10 KEXEC

[alchemist]

Hey guys need some help, ive installed the newest safestrap and i have followed the Op for the install but all i get on start up is a black screen, it vibrates really quick and gets stuck on the black screen, any ideas on what could be wrong? thanks

ROM: CYANOGENMOD 10 KEXEC

I had this happen back on Safestrap 2.11 with another kexec ROM. Never did figure out the issue...

[The Doctor]

Try non-kexec. Sts dev team has put kexec on hold until aosp base is 100%. Waiting on a full charge myself to try flashing on ss3

[TeamSpeedCore]

Okay this kernel building is a lot more complicated than I figured...I still am working with it, but in the meantime I will integrate Androguide.fr's PimpMyRom into the rom. Full credit to him of course.

Edit..looks like this isn't so easy to integrate.

Soooo...I'll make it so it is installable. Credit still goes to Androguide.fr.

[TeamSpeedCore]

Instant boot from rom to rom..incredibly fast data wipe and rom flashing..charging in recovery..naming of the different rom slots..and of course touch screen. This safestrap upgrade has got me drooling.

[The Doctor]

TSC....Need to point out that the new 4.1.2 AOSP Base is forcing all data to external SD card. People with the Nexus 7 are on the war path because the Dev's haven't been catching that fast enough. Tons and tons and tons of Bricked Nexus 7's out. Sounds like you can get it back, but the Nexus 7 doesn't use external memory (no ex card slot). I know most of us have bigger external cards, however, if you are like me you have 10 other ROMs stored, backup files, music, pics, etc, etc, there's no room on my ext SD Cards to support the entire ROM I was playing around with the new AOSP bases over the weekend and IMO are unusable in this state, so I bailed. I hope this is changed, but I wanted to alert anyone looking to switch over to 4.1.2 and don't see this right away.

[TeamSpeedCore]

Interesting. I HAVE noticed that sometimes when I download stuff it goes over to a Downloads folder on my ext sd.. but that is it.

Also this pimp my rom stuff isnt working out so well because no one has got it to run on the razr..it isn't compatible with safestrap so no one here can use it lol.

I am still trying to find an awesome combination of performance and battery for you guys. I want to get something I can give you now while I work on this new kernel..the new kernel is going to take a bit.

[eriv85]

First off great ROM.I just recently changed over to a Razr when I traded with a family member who didn't really use it. After running this ROM I have a question. Right now this is what I have.

Is 59% Android OS normal? I also tried the settings noted in post #305..I could visibly watch my battery decrease by 1% increments every minute or so after enabling those settings.

Any ideas would be great.

Note: This is extremely light usage for me. I also didn't list what ROM I'm running. I'm using CyanCore 1.2

Attached Files

•  Screenshot_2012-10-16-10-26-55.png   164.67KB   23 downloads

[twith70]

I would go to the market and install busybox. Run the app and then when it is done scanning use smart install. Since you received the phone from someone else..no idea what was done to it. It is also a good idea to do that after flashing any ROM. Android will work itself crazy if any binaries are missing. Hope this helps your situation.

[eriv85]

I would go to the market and install busybox. Run the app and then when it is done scanning use smart install. Since you received the phone from someone else..no idea what was done to it. It is also a good idea to do that after flashing any ROM. Android will work itself crazy if any binaries are missing. Hope this helps your situation.

I'll try that and see what happens.

[twith70]

Also, if you just flashed the ROM it takes a while to settle in with all of the changes to the system. I usually give a ROM at least one or two charge cycles to build caches and actually begin to operate normally. These custom ROM's have a lot of tweaks and scripts built in to them. Once your phone boots up the android system is still working in the background 'adapting' to new settings etc. I usually run through one charge cycle..reboot and wipe the cache for good measure. I hope you get it figured out.

[The Doctor]

As twith70 noted, it will take a few days. I have really been impressed with how the latest Android builds are actually learning about usage. Not that it wasn't doing it before, but it's getting more and more sophisticated as Google builds better and better AOSP builds. I think most will agree that we can get AndroidOS down to 20-30% usage. Depends on what I am doing for the day, but I can usually get it level out around 28%. I was starting to play around in the build props editor. I increased the frequency at which AndroidOS scans for wifi and I shaved off another percentage. There are some other tweaks we can all try, but really, until our wonderful Dev's can tweak those kernels we are tied up with some slightly high Batt drains. Google Now is still learning about me. I looked down today and it started populating all the places I normally travel to on a Tuesday (kids Karate class, stop at the store afterwards, back home, etc). Very, very cool algorithms in place

[alchemist]

I'll try that and see what happens.

If you are actually using a RAZR (as you posted earlier) and not a RAZR MAXX, your battery drain might be about right. I had one of those for a week or so before returning it and getting the maxx because the battery drain was horrible.

[eriv85]

If you are actually using a RAZR (as you posted earlier) and not a RAZR MAXX, your battery drain might be about right. I had one of those for a week or so before returning it and getting the maxx because the battery drain was horrible.

Yes, it's a Razr and not the MAXX (I might convert it later..plus it was free..traded a droid 2 for it). I wasn't expecting GREAT battery life, just wondering how there was a 25% drain, and I'd barely touched the phone. That just seems a little off to me. I ran the stock rom for a day, although I HATE blur, it didn't drain like that. I know this is a beta and this is just a part of the process. I was just trying to understand why the Android OS was using 59%.

[eriv85]

Is anyone else not getting all their text messages on cyancore 1.2 ?

[TeamSpeedCore]

Just want to report that I am actually starting to see the AndroidOS level off a bit on BATT usage, the OS is starting to learn more and more about my own usage. I am roughly around 20-30%, still not great, but better. I am getting about 18 hours out of a full charge again, not great, but better than what I was getting on a number of other Rom's. I am running JellyCore v1.2, I will give you guys all my tweaks and hopefully this will help a number of you:

I setup the Battery Script mention in the OP. Got the error after setting it, restarted JelllyCore, and it's been holding on every reboot since. No errors or anything after the 1st one
CPUSleeper is turned on and applied at Boot
I use an app called BatteryCalibration 100%, I use this after every flash, even an update
All BusyBox Binaries are updated and I update again after the past few updates from the App Dev. Use the "Smart Install" function unless you are a pro

ROM Tool Box Lite Settings
CPU Control - Govenor is set at hotplugx and apply on boot is checked

Kernel Tweaks - Sysctl Conf - Using ROM Tool Box's default settings, apply on boot. Advanced - I/O Scheduler is set for sio and apply on boot

Memory Manager - I am using the "Ultimate" preset. This is where we will all vary, next tab in "Task Manager." I have actually gone through and killed a number at boot. Some stuff doens't need to be running for a "just in case instance" I control my device and I will determine what MY needs are. I know some App Devs/Companies are just doing what think is best, but then why did I root my device? Go in there and just kill/prevent some stuff from booting and running in your upper memory. Remember, this is America and it's your device. You can even lower the oom value, giving those apps a lower priority.

SD Boost - Turn this up. Controls your read/write speed. This is actually pretty important because if your device has more memory to actually read/write data it can get done fast, not hang and use less battery. Mine is set to 2048kb & apply on boot

Oviously back up your device before making these kind of Root changes. Please ask me if you have any questions, here to help

Doctor I just want to thank you for your support.

[eriv85]

Seems that the battery drain after installing busybox has slowed, but on the Doctor's suggestion. I will wait a couple days and see what happens then. Now, I just need to understand why only part of my sms messages are getting to me.

[The Doctor]

Yes, it's a Razr and not the MAXX (I might convert it later..plus it was free..traded a droid 2 for it). I wasn't expecting GREAT battery life, just wondering how there was a 25% drain, and I'd barely touched the phone. That just seems a little off to me. I ran the stock rom for a day, although I HATE blur, it didn't drain like that. I know this is a beta and this is just a part of the process. I was just trying to understand why the Android OS was using 59%.

It actually has to do with how Jelly Bean AndroidOS interacts with the Moto ICS Kernel. I am not going to get into the whole "why Motorola sucks" debate in this thread. Google is just now getting their hands into the Exec's at Moto. A few months back they fired something like 90% of all VP's, closed up a number of facilities in regions where Moto was performing badly. Any time there is a MAJOR buyout like this the world standard is, "No changes for at least the first six months" We are finally getting into the next 6 months. And as you can see, Google is already changing things. Moto now offers a way to unlock the bootloader. They released the Moto source code so that Dev's can add it to AOSP Builds. It's a matter of time before Moto is under full control of Google, and I mean body, mind and spirit. We just had Motorola in here last Friday doing a demo, got to see some of the new items that are in the pipeline. It was funny, they were in here bragging that their new Enterprise level tablet is coming with Android OS. I called them right out because it was coming with Ginger Bread and a locked bootloader. They didn't have too much to say when I grilled them for their stupid policy of locking the bootloader. They did say this which they have NEVER said in the past.....We are willing to talk with you and your customers about unlocking the bootloader. Things are starting to change, it's just going to take time

So to back up to your question...We are running Jelly Bean on a kernel that was never design nor intended to run the complex code of Jelly Bean. The AndroidOS is having to work harder since the kernel isn't giving the software support on all levels. Our Dev's are scrambling to make it work and hey will, TSC and the other guys just need more time