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

Root [ROM]AOSP ShiftTh3ory

Shoot there used to be devs that would tell users to wipe more than once

especially the devs for the OG droid. almost every ROM had instructions to wipe data/cache/dalvik 3 times each between flashes. while i have been doing that ever sense, i will certainly be going back to 1 wipe each from now on. thanks for the heads up guys. :cool:
 
The only reason I can think that the multiple wipes would be needed is if the wiping functions were broken in the recovery. I don't think that is the case.
 
especially the devs for the OG droid. almost every ROM had instructions to wipe data/cache/dalvik 3 times each between flashes. while i have been doing that ever sense, i will certainly be going back to 1 wipe each from now on. thanks for the heads up guys. :cool:

I remember liquid always said that about his roms. Now that I think about it, pretty much every og dev did lol except Chevy (I think).

Yeah that is exactly what I was talking about. I think it started with CM and people not wiping before the flash so devs just said wipe 3 times in hopes of users wiping at least once.
 
lol,i just took out the gmail .apk,so when you flash it,it should upate the other apps to grey,but leave white gmail alone :)

I forgot you posted this and after having numerous problems with gmail and now the market and not being able to d/l any apps I ripped gmail out of the burn pack myself, flashed it and am rebooting now (better work or I'm never touching a DT ROM again) Wanted to thank you for posting it, though

All is working now. Wish I wasn't so lazy last week and would have just pulled it out, signed it and been down with it :rolleyes:
 
Sometimes doing things the most direct way is the best. I have heard it called brute stupidity--just do it in the most straightforward, got-to-work way.
 
So I switched from the Imo-3.5.11 kernel to the 3.5.8 a couple days ago, went to extreme, and noticed my Wifi would disconnect itself if I leave the screen off too long. Sometimes it instantly reconnects, sometimes I have to toggle it off/on to reconnect. Got annoyed so I went back to 3.5.11--except now it's doing the same thing on that kernel. Is it the kernel or because I switched from safe to extreme when I switched to 3.5.8?
 
Was that always there? Coming from Sense there are a lot of different settings options on AOSP.

Yea, it's always been there ;)

For what it's worth, I've been running Imos new 3.5.12 kernel and after almost 24 hours I think I can safely say it's better than 3.5.8. I used my phone a lot today...

100+ texts
~150 calls (I'm in sales, my calendar and phone are my $$)
2 gmails constantly syncing (G+, email, music and calendars)
twitter updating every 10 minutes
Browsing in between calls
GPS on for about an hour

Off the charger this morning at 8:15 and I'm sitting on 44% (WiFi 90% of the day, no LTE-it's the devil :p)

If you're on 3.5.8 and think it can't be beat I'd suggest giving this a try. Imoseyon is the best kernel maker I have ever had the pleasure of knowing (yea, we're twitter and G+ friends ;) haha)
 
Hey worm. The screen shots you posted in the "lets see your screen" thread you have the center clock. I was under the impression the center clock mod didn't work with Shift Theory or with LCD density changed, care to share how?
 
DT's framework doesn't work, but if you use CM7 fw it works fine. I lower my density to 205 and I haven't had any issues with it. The only thing that happens is notifications come in they overlap the clock since it's in the middle. To me it's not an issue, others it may bother. To each his own
 
Also, make sure you wipe cache and dalvik before flashing. If for some reason the patch.zip doesn't work the first time, reboot>recovery>flash undo patch>reboot>reboot>recovery>flash patch.zip>reboot>enjoy center clock
 
Okay, would I just kang the framework from /system from the CM zip and add paste it to /system or is it framework res apk and/or framework jar?

We are getting to the areas where I have caused bootloops on my OG Droid trying to frankenstein a rom together.
 
I assume you're going to use the patcher I linked in thread I started?

If yes, just pull framework-res.apk from system/framework. Place that fw in the input apk folder the patcher creates after you extract it.

I'm off to bed, PM me if you get stuck and I'll get at you in the morning

PS don't know if you saw, but a new CM7 is out
 
Anyone noticing huge battery drains on shift theory when using 3g and 4g connections. Half my battery is almost depleted after 2 hours! But on wifi the phone is crazy and lasts 12 hours on average. Anyone know how to fix this problem? I'm sure most of you guys aren't connected to a wireless router the entire day. I have been switching between the jd eclipse kennel, immoseyon, and others and have gotten the same results.
 
I can't comment too much I stay in airplane mode most the time I am not on WiFi, usually it is a kernel thing. I take it you are using the ones you can get in the store? You may want to try IMO's new release 3.5.12 I am testing it out today seems okay. I haven't liked the kernels that DT modified.
 
I can't comment too much I stay in airplane mode most the time I am not on WiFi, usually it is a kernel thing. I take it you are using the ones you can get in the store? You may want to try IMO's new release 3.5.12 I am testing it out today seems okay. I haven't liked the kernels that DT modified.
How can you spend so much time on airplane mode? What if someone is trying to call you?
 
Back
Top Bottom