yashsingh1/xdaforums huggingface dataset:
[Motorola Droid Android Development] fash99:
All I can say is that it is fast. Yes sometimes reaches 0 MB RAM but this rom is not yet complete or stable.

Try the script and let us know your experience
[Motorola Droid Android Development] firefurby:
Success

Flashed each of the zips in order just to be sure. Went into a boot loop for about 5 cycles. Finally got out. Everything seems to be working nicely. Still going through some testing, but looks good.
[Motorola Droid Android Development] philo_enyce:
i had a similar issue, tried an install, got the boot loop, tried a few more times, no dice, tried to go back to steel droid and no response with the screen. i re-downloaded the build, booted into recovery and went into advanced to wipe system in addition to data and cache, re-flashed and low and behold, the thing booted and the touchscreen works again.

not sure what or why, but just happy to have a working droid. i haven't installed the gapps or even played with it, but wanted to get it out there that i had the same issue and seem to have resolved it.

good luck with yours!
[Motorola Droid Android Development] kfazz:
like my ics builds, i recommend formatting system before flashing.
[Motorola Droid Android Development] philo_enyce:
so i've had it be a bit iffy about rebooting, it seems to be inconsistent about the boot loops. it's possible, but not something that i've been able to nail down, that rebooting while not attached to a pc is better than doing it while attached, but i really can't say for certain.

it's definitely weird, but when it boots, damn that's cool :)
[Motorola Droid Android Development] Kyle Chen:
When I update my rom or restore a bunch of apps do I need to re-supercharge?
[Motorola Droid Android Development] ColibScz:
FYI for anyone experiencing this, I tried to flash as well, boot looped, and am trying to go back to BB just to charge up and use Dropbox to get a different APK, and my touchscreen is unresponsive as well. Will be trying the above steps and will confirm if they work for me.

---------- Post added at 02:08 PM ---------- Previous post was at 01:24 PM ----------

Boo... :(

Still stuck in boot loop...Reformatted everything after going back go BB and losing my touch screen. I then tried installing another, different zip from the thread, and that's boot looping now. I think I'm going to have to format, try to go back to BB again, and hope that with a full format the touch screen works. I'm so disappointed! Can anyone offer anymore ideas that I can try before giving up??
[Motorola Droid Android Development] kfazz:
to everyone with touchscreen problems, does my ics build work?
[Motorola Droid Android Development] ColibScz:
Can you drop a link for it? I had ICS on this before, but it was some crazy pre alpha version, not sure if it was even yours. I'll try your ICS version now if you can show me the way!
[Motorola Droid Android Development] philo_enyce:
i have had boot loops regularly after every reboot, however if i pull the battery after a few loops and try again, after a few cycles (loops, pull batt, loops, pull batt, and so on) it somehow boots. i'm using the latest build with the gapps from the main post.

keep at it, with any luck you'll get it running!
[Motorola Droid Android Development] kfazz:
did you ever get past the bootloop?

i think ts problkem is a conflict between sgx overclock and touchscreen driver causing the ts chip to get stuck in a strange state

try this build:

http://www.mediafire.com/download.php?sndcftxoq9g51gd

then flash this kernel:

http://www.mediafire.com/download.php?uuhjaczqiqudqll

if that works then try jb again, or any other rom, it should work fine
[Motorola Droid Android Development] ColibScz:
You're an absolute genius. Now then, if I'm going to try JB again, maybe I'm wrong, but I feel like I should try the latest one in the OP. Would you think that'd be my best shot as well?
[Motorola Droid Android Development] neilrl79:
I'll give it a shot, tho I SBF'ed and still couldn't get touch screen working. I'll mess around with it later. A new touch screen runs around $12 bucks on ebay so worse case isn't too bad.
[Motorola Droid Android Development] kfazz:
sbf to stock won't do anything as far as touchscreen is concerned.

so none of my jb builds ever fully booted for you? a complete boot (even 1 time) should reset the ts chip and it should work.

idid you erase system partition before flashing jb?

i've posted a slower more conservative kernel in the OP that shouldn't bootloop

that should fix your ts problem
[Motorola Droid Android Development] kfazz:
yes, latest one has the most bug fixes
[Motorola Droid Android Development] neilrl79:
No I never got a full boot tho I stopped trying when my touch screen stopped working. I'm going to try it again later today and see what happens. Of course that will be after I re-root and install cwm again.
[Motorola Droid Android Development] BriCo84:
So far nothing has worked for me. Boot loop EVERY time. I have tried everything, including on the last run, formatting everything (system, factory reset, cache, delvik cache), then installing the new kernal. Then the latest jb zip, then gapps, still boot loops.

Anyone have any other ideas...
[Motorola Droid Android Development] neilrl79:
I just re-alized that I may have screwed myself... if I can't unlock it to turn on debugging, then can I even root it at this point?
[Motorola Droid Android Development] ColibScz:
Here is what has FINALLY, and JUST NOW worked for me!

-Format system/data/cache

-Install the ICS recommended to me by kfazz on page 6 of the thread, then before booting, install the kernel he recommends.

-Make sure it boots into ICS cleanly.

-Format system/data/cache

-Install the JB rom, then before booting install SAFE KERNEL from the top of the thread as well.

Should be up and runnin!
[Motorola Droid Android Development] kfazz:
you could use use sbf_flash to flash clockworkmod recovery via linux or mac

or rsd lite on windows

see here:

http://wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide

and if sbf_flash complains about the cwm sbf file being invalid

get this:

http://download.clockworkmod.com/recoveries/recovery-clockwork-2.5.0.1-sholes.img

and this:

http://cmw.22aaf3.com/sholes/recovery/MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf

./sbf_flash -r --recovery recovery-clockwork-2.5.0.1-sholes.img MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf

(this flashes cwm with ram downloader from SPrecovery sbf)

as soon as the phone reboots hold x to get into recovery otherwise stock system partition will re flash recovery every boot
[Motorola Droid Android Development] ColibScz:
Try this process:

-Format system/data/cache

-Install the ICS recommended to me by kfazz on page 6 of the thread, then before booting, install the kernel he recommends.

-Make sure it boots into ICS cleanly.

-Format system/data/cache

-Install the JB rom, then before booting install SAFE KERNEL from the top of the thread as well.

You shouldn't need your touchscreen for any of it, and once you boot in to ICS that first time, my guess is your screen will work anyway.
[Motorola Droid Android Development] kfazz:
he sbf'd back to stock, so he needs to get CWM back before he can do that
[Motorola Droid Android Development] neilrl79:
Cool, it's been so long since I've done anything on the DROID that i forgot most of this stuff. I'll give it a try and post back my results. Thanks.
[Motorola Droid Android Development] BriCo84:
Unfortunately this did not work for me....I got to the 3rd step "Make sure it boots into ICS cleanly" and ended up with the same result as with JB. It just goes in to an infinite bootloop.

Any other ideas....this is very frustrating.
[Motorola Droid Android Development] kfazz:
flash ics and 160 kernel in the same recovery session

did you wipe system before flashing ics? try formatting boot too.

also after you flash pull battery for 5 secs, and then let it attempt to boot.

if that still doesn't work, restore a backup and pull /data/dontpanic/apanic_console

throw it on pastebin and i'll try to see why your phone is bootlooping

Edit try this kernel: http://www.mediafire.com/file/do6yfe1c79v7xj7/jb_safer_kernel.zip

it's for jb but may work on ics. it doesn't reprogram core clock at boot and uses exact stock

(160.5/80.25mhz) timings.
[Motorola Droid Android Development] fash99:
You can test this http://androidforums.com/droid-roms/598966-droid-altonus-ics-rom.html and after install JB. I did this and had no problems with the Rom Jb of Kfazz.

Sorry for my bad English.
[Motorola Droid Android Development] Rpatton:
Thank You

Wow the support really picked up for this thanks alot for the links to the ICS got it working followed the previous support and got JB to boot its nice and smooth great work OP keep up the work You have brought life back to my Old OG moto droid

Thanks Again

Note

No Move to SD everything i try and move (because of low space ) does not move fails

still playing will report other bugs

Move to sd card is a big deal with low space i haven't crashed it yet seems stable
[Motorola Droid Android Development] Kyle Chen:
Just curious, how many different ics roms does this phone have? thanks

I'm on jb right now but I just wanna test that rom out lol
[Motorola Droid Android Development] Shredder87:
You think the phones build date has anything to do with these touchscreen issues? Mine was built around January last time I checked.
[Motorola Droid Android Development] fash99:
I have installed and tested 2. Kfazz ROM, and the EManU3LXX ROM (where he continues to work and promises to be very stable) :good:
[Motorola Droid Android Development] kfazz:
look at his screen shots, guess where he got his kernel? :D

idk if he's building from source or just modding my ics rom, but the more the merrier
[Motorola Droid Android Development] Kyle Chen:
lol yea.
[Motorola Droid Android Development] kfazz:
doubt it, afaict they all have the same chip. it's some atmel qtouch, mxt but not one of the ones thats publicly listed, maybe custom for moto. it's reffered to as a09AS.

it's used in some of the other droid family devices too.

i think it's the sgx overclock causing the phone to deadlock while the touchscreen driver is bringing up the chip (it reflashes the chip on boot in case the contents change, as the eeprom can get corrupted by ESD (according to the source anyhow)) ** actually it only reflashes once? it checks eeprom every boot though, but checksumming function is wrong. once the flash is successful any rom will work, stock 2.0, 2.2, gb, whatever

what's strange to me is that no one had any problems with it on the ics build, the kernels are pretty much identical between ics and jb.

i had this problem exactly once during developement, when i tried to boot my 200 ics kernel on my test droid which only will run @180. from what i could tell the phone crashed after qtouch driver put ts chip in bootloader mode, but before flash completed.

once i flashed a kernel that booted fully i had no problems.

In theory the safer kernel should work for everyone, as i reverted all my clock changes.
[Motorola Droid Android Development] kfazz:
i just realized safe and safer kernels have max cpu at 1000.

maybe these droids can'thandle the cpu overclock.

heres a kernel with max cpu at 800

all the cm kernels support this, it uses stock voltages.

maybe this will work if those don't

http://www.mediafire.com/file/926lgj8qu2a8l8s/jb_safest_kernel.zip
[Motorola Droid Android Development] fash99:
True, I had not realized that. Sorry, the credit is all yours. Hope I did not bother with the previous comment. You're the best. :good:
[Motorola Droid Android Development] kfazz:
it's cool

i can't take all the credit, my work is based on lots of other developers'. and cyanogenmod, google, moto, linux :D

what did newton say? "i stand on the shoulders of giants" something like that
[Motorola Droid Android Development] fash99:
:cyclops: :good:
[Motorola Droid Android Development] neilrl79:
Well to update..... I sbf flashed cwm to my droid then formatted system, wiped data and cache the flashed the rom, minimal gapps and safer kernel and it booted right up with a working touch screen! Thanks kfazz!
[Motorola Droid Android Development] kfazz:
Awesome! do the other kernels (the one in the rom and safe) still bootloop for you?

Does everyone else who had touchscreen issues have them sorted?
[Motorola Droid Android Development] cr08:
I had tried out JB yesterday and bootlooped on the M logo. SBF'd to stock with completely unresponsive touch screen and phone and acore FC's. Found the recent posts here, re-flashed CWMR and subsequently the JB build. Same bootloop. Back into CWMR and flashed the 'safe' kernel and booted just fine with a working touch screen.
[Motorola Droid Android Development] neilrl79:
The one in the rom bootlooped. Now that I think about it, I'm pretty sure I used the SAFE kernel, not safer.
[Motorola Droid Android Development] joeroid:
overclock

Don't think over clock is a problem all other Roms I have run (and there have been too many to count) everyone of them ran fine at 1200-1250mhz using deprimed kernel
[Motorola Droid Android Development] neilrl79:
If I recall correctly I used to overclock to 1200 all the time on CM and UltimateDroid.
[Motorola Droid Android Development] peeyourownpants:
I was able to drop out ~7mb of those and nonessentials in the 8/26 build and it's working fine.

And as one of the people to have reported a successful boot, I should repeat that with the 8/24 and 8/26 builds I have yet to have it boot on the first try, but I just let it run the loops until it boots all the way. Sometimes I've left it running when I went to bed do I'm not sure how long it can take but it's always booted for me.
[Motorola Droid Android Development] zerokoo:
only issue i had after flash jb was when i went back to ics lost the lock screen LOL but aside from that im on jb again and its great nothing broken on my ends bluetooth audio is not working but i can use my phone as a remote for my laptop with Bluetooth 3.0 with edr LOL it runs ot but no gripes just wish ram wasnt so tight but swap it works well to help that :)

---------- Post added at 06:17 PM ---------- Previous post was at 05:52 PM ----------

also if anyone has noticed you tube and you ui stuttering go into performance and look at the cpu governor it is on conservative set it to on demand or whatever it tends to work better not sure why but the cpu caps at 1000 mhz on conserv and stutters on youtube but using on demand when it hits 1k it works better and no stutters :) also found when i dont use supercharger its better as i have 69 megs of free ram when i super charge it gos to 0.00 LOL
[Motorola Droid Android Development] neilrl79:
Is gps working for anyone? I can't get Mytracks to lock on to gps and my main goal for the droid is to use as a tracker/gps for rides on the Buell.
[Motorola Droid Android Development] kfazz:
nb: so far jb has had about 1000 downloads and 5 reported problems with touchscreen.

edit: gps is known not working. doesn't work on ics either, long story there.

the ril i'm using on these builds doesn't interact well with droid baseband. (just for gps)

and there's no jb gps shim libraries that i know of yet.

the ics ones cause... bootloop.

so it'll probably be a while before it works.

my test droid is running different baseband firmware that works with the ril, but this change is irreversible and breaks sbfing back to stock (radio dies until it's reflashed) so i'm not releaseing that.

i've talked with mbm, tried qualcomm tools, rsdlite, all sorts of things, it's a one way change.

pretty extreme just on the chance it fixes gps lol

i'm not saying it's never gonna happen, but it'll probably be a while.

some people have reported gps as working on some of my older ics builds but it never worked for me.
[Motorola Droid Android Development] joeroid:
GPS worked fine for me on ics build 7/12 not working on JB though
[Motorola Droid Android Development] slaZzz:
GPS seems to work fine for me on ICS too, though it's from Google maps. I never looked into whether it's from the actual GPS or just cell site positioning.

BTW, sorry to trouble you. Can you enable ext4/zram kernel modules in your next update? It's currently disabled and the modules in the build is compiled against the ICS kernel. I've tried quite a few things, but at the end concluded I couldn't get the older kernel modules to work with the JB kernel or get the ICS kernel to boot the JB build. Thanks in advance!
[Motorola Droid Android Development] joeroid:
Just loaded TLS kernel no GPS but I put GPS.sholes file back in system and phone boots no problem and seems faster and smoother
[Motorola Droid Android Development] neilrl79:
Damn, I was really hoping for "quick fix", oh well. On the other hand I'm really impressed with how this rom is running... fairly smooth(at least as smooth as whatever official rom was on my DROID) and as i far as I can tell gps is the only thing not working.
[Motorola Droid Android Development] Kyle Chen:
I can confirm GPS worked on your ICS builds from 7/3 and 7/12. I was able to use google maps to navigate to several places. Maybe it depends on the Droid phone?
[Motorola Droid Android Development] ASAM123:
GPS worked for me on ICS too. I haven't tried it on JB yet.

Right now, I primarily use 3 different nandroid backups. Jellybean mostly, ICS and Liquid Smooth Gingerbread for other tasks/apps.
[Motorola Droid Android Development] Son et Lumiere:
This runs surprisingly well on my Droid, even faster than GB did but it maxes out the memory so there's lots of refreshing. If only the OG had at least 512 MB.

Is there a reason Google Now is missing?
[Motorola Droid Android Development] lwilli:
Another TouchScreen Report...

jb bootloops the M logo... flashed steel droid back and no touchscreen... will try safe kernel and ics build... I'll report the results...

THE RESULTS....

ok thanks kfazz that fixed touchscreen without a doubt...

My only question now is how can I make jb work with this phone...?

Should I use the bootloop fix with the safe kernel...? or just wait for another build...>>??
[Motorola Droid Android Development] ASAM123:
Can I install a boot logo on this rom on data/local? thanks
[Motorola Droid Android Development] firdausmbois:
its almost everything working until i install gapps it significantly slow :) and i cant install apps now

*its fixed after full wipe & reinstall gapps
[Motorola Droid Android Development] djrakun:
will the volume rocker turn the screen on in this ROM? my power button is broken so unfortunately I can't flash this unless the volume rocker can wake the device, otherwise, a battery pull is the only way to wake the device up
[Motorola Droid Android Development] kfazz:
both my ics and jb builds support this, but it is disabled by default. it's under settings->Display->Volume Rcker Wake

i recommend trying the ICS build first, in case you run into touchscreen problems,

as fixing it without the power button working would be a test of patience.
[Motorola Droid Android Development] kfazz:
i just flashed my activated droid to jb.

it bootlooped.

safe kernel worked.

this is the contents of /data/dontpanic/apanic_console:

http://pastebin.com/YmhFc8e9

the crash seems to be cpcap related

BUG() at cpcap_uc.c line 335

i'll upload a new build after work with safe kernel as default.

Edit: could be this: Modules linked in: xt_owner2 xt_quota2

i didn't recompile those for the jb kernel
[Motorola Droid Android Development] mgross029:
kfazz,

Thanks again for all the great work!

I've been trying to get any of the builds loaded to my test phone but they would not boot. I then took the plunge and put it on my activated Droid over top of my ICS install and it booted without a problem. So now I'm wondering if my AOKP ports won't boot for this similar reason. I am going to attempt to use your Safe kernels to see if I get any better results. I was able to load ICS and GB on the deactivated phone without a problem, so it's not the phone from what I can tell.

I had GPS working on ICS builds without doing anything. I have since added the shim from ICS and now see some data coming back in logcat, but it appears to be agps related and no true GPS signal as of yet. I have noticed as another poster mentioned that the interface became a little smoother after adding the shim from ICS.

Bluetooth, is kind of funny because in ICS the Media routing working and I was able to stream music and In-Call audio was not working at all. Now with JB the In-call audio is working great, but the media routing defaults to speakers.

EDIT: Something I forgot to mention. When I put the phone into the CAR DOCK the media audio doesn't even route through the speaker it stops completely, but as soon as I remove the phone from the Dock the audio comes back to speaker. I'm thinking the magnet in the CAR DOCK is now activating another process/audio routing scenario. Haven't been able to capture logs from this scenario just yet.

Not sure if this helps or not but I stumbled upon this TI page regarding the WL1271 and there was a portion in here which speaks to uim-sysfs, which is from what it states is a shared transport user space mgr service for Bluetooth, FM and GPS. I've looking in the source and hardware/ti/wpan/ti_st exists so the uim_sysfs could be included in the sholes.mk file. Not sure if this is one of the key services we need to have running to make all of these services work together.

Here is the link... Some good info that we could possibly use if you haven't seen it already.

http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide

I've also noticed some libEGL errors in the logs which may or may not be causing some various display problems. Here are two lines from logcat that appear together.

08-29 07:37:26.622 D/SurfaceFlinger( 1024): About to give-up screen, flinger = 0x2a008af0
08-29 07:37:26.653 E/libEGL ( 1024): validate_display:209 error 3008 (EGL_BAD_DISPLAY)

Also, there are a lot of E/Trace errors in logcat, but I'm not sure this has something to do with an APP which is installed.

08-29 08:46:27.375 E/Trace (12842): error opening trace file: No such file or
directory (2)

Hope this is helpful.

I can provide some kmsg and logcats pastebins if you would like. Just let me know and I'll PM.