• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] DroidSmith_Force - Beta

I was able to flash previous versions of dsf too, I think this issue started with the last release or the release before that. Don't quite remember.
 
I wouldn't recommend using any battery saving apps, there's no point to them, and I wouldn't install any cpu tools, dsf already comes with menus equipped to control the important parts of the CPU.

So, what you're saying - I shouldn't be using Antutu Battery Saver, or anything else? I've always used it since I got root on my phones. If I don't need it, then cool.

Also, I find it hard to believe that having an on-demand setting from 384-1674 CPU is "helping" my battery. If anything, it's letting my phone clock higher than it can, and over max capacity. Therefore, draining my battery more.

But, JIM - I see ass something, and other types (besides on-demand). Can you specify which each one does? I'm trying to get the max work ability, with the lowest amount of battery drain.
 
I'm sorry, I got battery savers and task killers confused for a second, either way everything a battery saver does you can do your self and save you some memory and another percent of battery, so if you can learn to do that you shouldn't need a battery saver.
 
Nope its back.

Lol


When. Did it come back? I still haven't experianced this issue. In the rom I built for the warp there were issues early on, but where later resolved.

Here is what I need from all of you guys for bug reporting.

1) has the system been modified from what I originally provided?

2) If so, what mods are you using?

3) When did the issue occur? Was it first boot, or after an app or script has been installed?

4) has any theme work been done?

5) What CPU settings are you running?


I know its a lot of information to ask but its the only way I can solve issues. When I post updates its because I have tested them with the apps and settings I use, and have not had an issue. I want to build a fast and stable rom for everyone to use so I need to be able to recreate the issue in order to get the bugs out
 
I wouldnt use ondemand (it keeps cpu at min freq set then ramps all the way up to max freq set and ONLY switches between the two) its not a powersaver. I would use either smartassv2 or badass because it mixes power and battery.
 
Downloaded and restored stock nandroid. Booted it up to make sure everything went fine, things were fine so I flashed dsf and this time it froze at boot animation and showed a glitchy image of boost logo + dsf animation, but this time no crash, had to pull battery, powered on, never got past boot anim.
 
Version 0.5 is up. I have added new battery icons, and lightly themed Xperia. Matrix Kernel 1.1 is the default kernel, so there is no longer a need to down load it. I hope this addresses the issues some of you have been having. If there are any further problem please give me a detailed bug report and I will do my best to correct them. I you do not know what a detailed bug report is please see the first post on this thread.
 
Flashing from stock ROM I still get the same problem where on boot it freezes at the boot animation. Just to make sure, it couldn't be the recovery I'm using if I've been able to flash every other ROM fine, right?
 
Flashing from stock ROM I still get the same problem where on boot it freezes at the boot animation. Just to make sure, it couldn't be the recovery I'm using if I've been able to flash every other ROM fine, right?


I would highly doubt it, but since it at least boots for everyone else I have to wounder. Are you using the cwm that 1mouse3 built?
 
But I successfully flashed previous ROMs/kernels.
0.4.9 was the last ROM to work for me.


OK that gives me an idea. I'll back the default speed of the CPU back to stock. That may take care of your issue. You will still be able to over clock if you want, but it will slow the device down a little at boot.
 
But why are other people able to flash it fine and not me?


I honestly do not have a clue. My best guess is that your CPU does not get a long with the 1.67 ghz setting. Or maybe even the gpu overclocking. ZTE isn't known for quality control. Our best bet now is to try to work something out that works on your device. If you haven't already try testing matrix kernel with the stock rom. If it boots then we know thatbthe issue is with the rom and not the kernel. If not then its safe to assume your issue is with the kernel
 
Back
Top Bottom