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

Root Where are all the devs at?

Yeah, I'm afraid I'm going to sell it, and my marquee also, to finance a used p930 or half of a new N4. It's pretty hard to dev for a phone that you don't have lol.


Well, seems like the developers are going to be few and far between.

Sigh. Big Sigh. I have my Spectrum on VZW and I'm not going anywhere so even though I have very little free time I might be able to download the latest SDK and start doing a little development.

Man, did I just admit what I do for a living. I'm such a geek!
 
whats even more messed up is all the so-called devs we bought phones for who have disappeared. apollo and weblexa in particular. I'm trying to remember all the devs we got phones for over the summer to help development and which of those have never done the first thing for our phone. I think apollo and weblexa are the only two who have gone off the radar completely.

O'well though. Hopefully nitro finishes eclipse and that will be my DD until I can get rid of this phone and hopefully choose more wisely for my next one.

I'm still hanging out... waiting for a data fix for cm9. I was originally recruited to get MIUI ported, and I can't do that without cm9 or cm10.

EDIT: I just want to make sure nobody thinks I took a donated device without the intention of doing what I said I would. I do intend to get MIUI ported (and maybe a few other AOSP based ROMS) as soon as the data issue with cm9 is fixed. I wish I could help out with getting the data fixed on cm9, I just don't have the time nor skills to do that kind of work.
 
I appreciate that a lot, thanks. But to be honest what I would need for good development is VZW service. I am using my spectrum on Sprint (VM actually) which is why I haven't made any progress with data. I was hoping one of the other devs could get data working.

I'm pretty sure VZW 4g service requires an expensive contract and there's no way you guys are going to pay for two years of my phone service. I just couldn't accept that anyway.

If someone could loan me a spectrum with active service for a week or two that might work. But who can spare an active phone for that long...? And 4g on cdma is such a strange thing, there's no guarantee that I could figure it out.

But to answer directly, I paid $150 for it on ebay and that's the most I could expect out of it. It's in great shape, close to mint, just had a blacklisted esn (which is now zeroed). If anyone here wants it let me know.

Do you still need someone to loan you a Spectrum with VZW service? I have a spare line that I can activate my Spectrum on and ship it to you for a few weeks. Shoot me a PM...
 
Do you still need someone to loan you a Spectrum with VZW service? I have a spare line that I can activate my Spectrum on and ship it to you for a few weeks. Shoot me a PM...

Hey thats a great solution web, and thanks for offering to do that! I was getting kinda nervous about being able to come to solution and this sounds great. Hopefully you and tdm can work something out!
 
Hey thats a great solution web, and thanks for offering to do that! I was getting kinda nervous about being able to come to solution and this sounds great. Hopefully you and tdm can work something out!

Its the least I can do since I've had this phone for nearly 4 months and haven't been able to do anything with it yet.
 
Got the official sources compiled. I strongly suspect they played with the sources before release (hence the time required to package them).

The diffs required to build are below. I haven't tested the resulting kernel yet, but I'll get to that later tonight or in the morning.

Code:
diff --git a/Makefile b/Makefile
index d8d8b1e..f34e0cb 100644
--- a/Makefile
+++ b/Makefile
@@ -193,7 +193,7 @@ SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
 # Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
 #platform-bsp@lge.com 2011.01
 ARCH           := arm
-CROSS_COMPILE  := arm-eabi-
+CROSS_COMPILE  ?= arm-eabi-
 export KBUILD_BUILDHOST := $(SUBARCH)
 ARCH           ?= $(SUBARCH)
 CROSS_COMPILE  ?= $(CONFIG_CROSS_COMPILE:"%"=%)

diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
index 035a8f4..94d2e27 100644
--- a/fs/ecryptfs/keystore.c
+++ b/fs/ecryptfs/keystore.c
@@ -1987,7 +1987,7 @@ pki_encrypt_session_key(struct key *auth_tok_key,
 {
        struct ecryptfs_msg_ctx *msg_ctx = NULL;
        char *payload = NULL;
-       size_t payload_len;
+       size_t payload_len = 0;
        struct ecryptfs_message *msg;
        int rc;
 
diff --git a/lge/factory/lg_diag_testmode.c b/lge/factory/lg_diag_testmode.c
index 5561775..4e02393 100644
--- a/lge/factory/lg_diag_testmode.c
+++ b/lge/factory/lg_diag_testmode.c
@@ -16,7 +16,7 @@
 
 #include <userDataBackUpDiag.h>
 #include <userDataBackUpTypeDef.h> 
-#include <../../kernel/arch/arm/mach-msm/smd_private.h>
+#include <../../arch/arm/mach-msm/smd_private.h>
 #include <linux/slab.h>
 
 #include <board_lge.h>
 
Surprise surprise, it doesn't boot.

I guess I'll need to start digging and figure out what's going on.
 
Okay I'm stupid lol. That kernel base I posted before was from the Marquee. The proper kernel base is 0x40200000. Trying again...
 
And the change in bluesleep.c does not seem to fix bluetooth calling. The fix must be something else, possibly in combination with that.

Batting a thousand tonight lol.
You actually got it to boot thou, or you put the bluesleep.c change into your other source?
 
I tossed most of the changes from zv7 into my source tree and got the same results for bluetooth. Then I started changing the kernel config to match zv7. When I enabled SPI, bluetooth was not used for calls at all, the audio came out the speaker. That's a clue, I think. Still looking...
 
I tossed most of the changes from zv7 into my source tree and got the same results for bluetooth. Then I started changing the kernel config to match zv7. When I enabled SPI, bluetooth was not used for calls at all, the audio came out the speaker. That's a clue, I think. Still looking...
So they played with it so source built won't boot properly? I don't understand how that's fair... but i guess they don't have to have working code, just has to compile. >.<
 
So they played with it so source built won't boot properly? I don't understand how that's fair... but i guess they don't have to have working code, just has to compile. >.<

I'm pretty sure the source drop does not match the binaries. We should let them know that the source doesn't compile and ask them to update it to the real released source tree.
 
Reply from LG:

We are very sorry to hear that.
Please make sure that did you enter right command to build the source properly as following included README document.
If you follow the direction by README file, Maybe there will be not any problem.

Please share the build log file to check it again.

We hope this information will help you.

I guess next thing is to submit a build log proving it doesn't compile.
 
I hope we don't have to go through the programmer's list of excuses on this:

"Hey, it compiles on my machine..."
 
I tossed most of the changes from zv7 into my source tree and got the same results for bluetooth. Then I started changing the kernel config to match zv7. When I enabled SPI, bluetooth was not used for calls at all, the audio came out the speaker. That's a clue, I think. Still looking...

Just for the nastiness of it we should file a complaint that they never released the 6b sources that got flashed prior to the full ics update.
 
Just for the nastiness of it we should file a complaint that they never released the 6b sources that got flashed prior to the full ics update.

I think we should file a complaint that they never released the 7 sources that got flashed... cuz they obviously didn't :P
 
Back
Top Bottom