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

Root [ROM] DroidSmith_Force - Beta

sawbones999 said:
Yeah I definitely don't want to write something over a partition or block device that I am not supposed to.

Thanks,
-SB
Click to expand...

If you keep the existing format and mount commands it should be fine as they are setup for the force and that update-binary.
 
Wanted to post a wholehearted thank you. I think this rom has given my phone a new lease on life. Have had it for about a year and it's been getting laggier as time goes by.
Finally decided I didn't have the patience anymore.
I'm running everything smoothly now and connection is great, texts send/receive faster, etc. Thanks again!! ♥
 
I flashed this yesterday, got a "sprint software update" on my phone, even though I use boost, and without thinking hit ok on it.

On full day later I am unbricked and flashed it again, but again the damn update is showing. Is there any way to get rid f this notification or to allow the update without soft bricking?
 
yeah, I get that.


I've flashed this to a clean device, didnt mod anything and using the cwm from the sticky to fla

the rom doesnt seem to have stable internet connectivity/web browsing - only wifi for data, which comes and goes - when off and trying to connect with a browser I get a white screen.

Tried updating profile, then prl, and rebooting. I get connectivity for maybe 2-5 minutes tops then off again.

The google play store also says i have no carrier - i assume this is an apn issue, but ive never had to deal with that - how do you change it to boost mobile?
 
For those getting system update notification, Google fotakill.apk, download and use a root explorer like es browser to insert into /system/app then restart and bingo, no more ota update.

BTW my rom is in progress if anyone is interested. It's really just a mod of dsf. Hope to get first release up this weekend.

Cheers,
-SB
 
I'm willing to try it out. Huh, for some reason FOTAKill wasn't working when I had it on my Force but hey, I barely even use the phone anymore xD.
 
Due to work my first release is being pushed back. Hopefully before the end of the week.

It's taking me longer than I thought to lock down the privacy with xprivacy (that is one of the added features I am including. It's an xposed framework module that allows you to specifically limit what each installed app has access to, like calendar, sms content, or contacts for example).

My goal is not only to add functionality and a change of ui to DSF, but to alter it in other practical ways such as improved security, privacy, and increased potential for blocking ads.

Fotakill is included by default and has worked perfectly for me on this (using dsf Rom) and other phones.

Cheers,
-SB
 
Now that I got the 4.1.2 Jelly Bean rom booting (with the help of your updater-binary/script and kernel, JimSmith80). I may switch to that platform.

Check that thread for updates. I couldn't get it working with the kernel shinru2004 dumped, but I was persistent and got it up with the kernel from dsf .7 and just using the ramdisk that shinru dumped.

Wifi and BT are not working, but I think it's BC I need to replace the drivers with the ones from DSF since I'm using that kernel. Makes me wonder if the one shinru dumped was 3.4 but he has not verified that with me yet. I know everyone was hoping to see that out. JimSmith80, do you think that one possible reason why the newer kernel won't boot could be a radio update? I'm still trying to get him to dump /modem for me.

But JB is up and running! It's probably at beta level bc I haven't had time to really dive in. Work is a lot lately.

I copied a lot of files from DSF into that ROM to get it to boot, basically I copied everything from system, but didn't allow anything to overwrite so only missing files were copied. It wouldn't boot before I did that, so without your work Jim, the JB wouldn't be working.

Thanks again for that! Couldn't have done it without you. I'd still like to find out what that other kernel is and if we can get it running.
Cheers,
-SB
 
If anyone has some extra time that they want to use to help me out, just give me a shout.
Click to expand...

I've got a force and can test for sure. My comp is slow and my knowledge limited, but if your are patient with explaining things I'll learn as I go. But testing for sure. I'm running DSF right now and noticed exactly what your talking about with the benchmarks jumping through the roof like that. I don't use service with that device though so I haven't tested WiFi or Web. Runs games movies and music like a champ though. I was going to try to port cm10 for this sweet little phone but I haven't started yet. (and likely won't for some time)
Anyway I'll keep my eyes open on this thread to see if there's anything to test. Be sure to let me know what info you need from a non working rom as well. I think I can swing a logcat, but have never needed to actually do it yet.
 
It looks like my enthusiasm for the JB ROM was premature. I don't think I can get Wi-Fi or Bluetooth working in it with the 3.0.8 kernel. I've spent hours and hours trying to make it work.

Also I'm getting a galaxy s4, for use with freedompop, so this will become a spare and my DSF mod will become much easier to complete.

Cheers,
-SB
 
sawbones999 said:
It looks like my enthusiasm for the JB ROM was premature. I don't think I can get Wi-Fi or Bluetooth working in it with the 3.0.8 kernel. I've spent hours and hours trying to make it work.

Also I'm getting a galaxy s4, for use with freedompop, so this will become a spare and my DSF mod will become much easier to complete.

Cheers,
-SB
Click to expand...

the Force is my spare too. Large sd card basically makes it an I pod touch with games. It's awesome.

Now as far as getting Bluetooth and WiFi to work I have a couple questions. I read that the WiFi module is kernel specific... A) did you try splicing in the correct WiFi module? B) what happened? / why didn't it work?
And I wonder if Bluetooth isn't the same.. Just kernel specific, so what happened when you copy the old module into the new rom? Or are there other difficulties?
DISCLAIMER: I will 100% ask question that I cannot understand the answers to
 
knoober said:
the Force is my spare too. Large sd card basically makes it an I pod touch with games. It's awesome.

Now as far as getting Bluetooth and WiFi to work I have a couple questions. I read that the WiFi module is kernel specific... A) did you try splicing in the correct WiFi module? B) what happened? / why didn't it work?
And I wonder if Bluetooth isn't the same.. Just kernel specific, so what happened when you copy the old module into the new rom? Or are there other difficulties?
DISCLAIMER: I will 100% ask question that I cannot understand the answers to
Click to expand...

I tried swapping in the appropriate drivers but they still failed to load properly. I tried copying config files as well. Same deal.

Haven't taken time to check the logs with dmesg yet.

Cheers
-SB
 
sawbones999 said:
I tried swapping in the appropriate drivers but they still failed to load properly. I tried copying config files as well. Same deal.

Haven't taken time to check the logs with dmesg yet.

Cheers
-SB
Click to expand...

Drivers = modules? Just for my own knowledge. Also (and doing this is above my head so that's why I'm asking about it rather than testing) is it possible that the kernel points to a different location for the drivers and that you could change where the kernel wants the driver to be to where it is?
I don't know if that makes sense, or if that is a reasonable thing to expect to be able to do to a kernel (like I said that's why I ask)
 
i have my voicemail jacked up.... it might have nothing to do with DSF but the timeline is making me question myself... anybody know how the settings are aquisitioned??
 
knoober said:
Drivers = modules? Just for my own knowledge. Also (and doing this is above my head so that's why I'm asking about it rather than testing) is it possible that the kernel points to a different location for the drivers and that you could change where the kernel wants the driver to be to where it is?
I don't know if that makes sense, or if that is a reasonable thing to expect to be able to do to a kernel (like I said that's why I ask)
Click to expand...

Basically modules= drivers in this context. A kernel module is precompiled kernel code which can be loaded and unloaded vs the old school monolithic kernels which required all pertinent code to be compiled into the kernel as a whole and then used as needed.

I remember when I first started using Linux was with the 1.x kernels which were not modular and when you got a new piece of hardware you had to go through a make file and select all your hardware in advance, then recompile and replace your old kernel.

So much more inefficient than modern kernels and using modprobe or insmod, but I feel like I learned something about kernel architecture with the monolithic kernels that I might not have learned if I were only exposed to modular kernels and precompiled modules.

As for moving the location of a module the simplest way to do this is to just make a symlink in the fs from where the script which loads the module expects the module to be, to the actual location.

Cheers,
-SB
 
ZTE Force said:
i have my voicemail jacked up.... it might have nothing to do with DSF but the timeline is making me question myself... anybody know how the settings are aquisitioned??
Click to expand...

I don't know what the hell you just said, but I would take the long way around to determine cause. Restore from a stock backup and test. If works, the reflash DSF and check again. Low tech I know but like I said, I don't know what the hell you just said except that your voice mail doesn't work
 
Make sure you are doing factory reset, as well as wipe dalvik cache, and doesn't hurt to format /system as well, before installing dsf. Then you should update profile and prl, and everything should work as long as you are on boost. You can even let visual voicemail update.

Cheers,
-SB
 
You must log in or register to reply here.
Back
Top Bottom