Last edited:
[ROM][Pre-Pre-ALPHA] Droid A855 ICS Build Attempt
- Thread starter kfazz
- Start date
-
- Tags
- droid a855 ics alpha
Thanks! But, i actually have a Droid. was worried that was why the rom didnt work. i guess its just broken right now? nobody has confirmed yet if this will or wont run (At its current build)
EDIT: Also, not sure if it matters, but they got the Camera functional on the Droid X, Bionic, Etc. Perhaps the source over there can help get it running here?
Thanks twisted for your hard work. I wish those who come to this thread asking for a handout would spend as much effort reading up on it as you do getting this rom working.
Folks, the title of this thread says Pre-Pre-ALPHA which means it is not a daily driver, and if you want to know which one works and which one has the most stuff working, please, please take the time to carefully read the whole thread. For now it seems as though the jan05 in the OP has the most stuff working, then you need to read how to strip down the gapps and how to make the market work properly. However twisted seems to be working hard on totally getting everything working, but as of yet his stuff won't boot.
This is not aimed at all the posters in this thread, I hope that is obvious.
Finally, as far as mtdblk3 or mtdblk4 I have found in my limited experience that
works just fine. Now I need a life for even remembering that one, hehehe.
Folks, the title of this thread says Pre-Pre-ALPHA which means it is not a daily driver, and if you want to know which one works and which one has the most stuff working, please, please take the time to carefully read the whole thread. For now it seems as though the jan05 in the OP has the most stuff working, then you need to read how to strip down the gapps and how to make the market work properly. However twisted seems to be working hard on totally getting everything working, but as of yet his stuff won't boot.
This is not aimed at all the posters in this thread, I hope that is obvious.
Finally, as far as mtdblk3 or mtdblk4 I have found in my limited experience that
Code:
mount -o remount,rw /dev/mount/null /system
Last edited:
Sorry for an intrusion here, but:
hwcomposer depends on dsscomp (kernel). At omapzoom, there is a work in progress on hwcomposer/dsscomp for omap3 that will not depend on omap4's tiler. But that work is still highly unfinished.
Also, that dsscomp depends on ICS release of SGX PVR kernel driver/userspace libs. But there is no ICS release for SGX 530 revision 121. So far, there's only SGX DDK 1.8 rowboat release that is only for revision 125. Although there is a hope for rev 121 ICS release sometime in the next quarter, it's certainly not available at this time.
So, how do you plan to overcome these issues? You're teasing people with "getting really close", but... are you? Really?
Some links of interest:
http://review.omapzoom.org/#/c/18688/
http://review.omapzoom.org/#/q/status:open+project:kernel/omap+branch:p-android-omap3-3.0,n,z
http://e2e.ti.com/support/embedded/android/f/509/t/165482.aspx
Last edited:
twistedumbrella
Recognized Developer
- Sep 3, 2007
- 10,994
- 10,398
You're talking about building a graphics acceleration hwcomposer for updated 121 drivers. I am talking about the default hwcomposer and updated driver support for 125. So yes, I am. Thanks.
Sent from my ADR6400L using Tapatalk
I see, you mean the software emulation of hardware composer.
And I meant the real hardware composer for omap3 devices.
But what means the bit about 125? The hardware used in sholes is SGX530 revision 121. Drivers/libs for SGX530 rev 125 are of no use on OMAP 3430 device...
Last edited:
twistedumbrella
Recognized Developer
- Sep 3, 2007
- 10,994
- 10,398
Backward compatibility. If everything went off only the exact revision it was made for, there would be no wifi, sound, etc for any older phone on ICS ever. My thunderbolt uses graphics drivers from a 3.0 kernel made for a Samsung Galaxy. I don't see it being that different from the Droid using Droid2 libs, since in the last working version I released it already did.
Question to Umbrella (Or anyone who knows?)
What is this leankernal 184Mhz? do i install it? Will it give any improvement on my CM7 rom? the worst that could happen would be that id need to reinstall the CM7 rom yes? :S or is it only for your upcoming rom?
What is this leankernal 184Mhz? do i install it? Will it give any improvement on my CM7 rom? the worst that could happen would be that id need to reinstall the CM7 rom yes? :S or is it only for your upcoming rom?
twistedumbrella
Recognized Developer
- Sep 3, 2007
- 10,994
- 10,398
anyone have a link to the last twisted build that boots? i really want to try it out and see the difference
twistedumbrella
Recognized Developer
- Sep 3, 2007
- 10,994
- 10,398
Sadly, even I don't have a link to it. I am still trying to figure out what got corrupted that is preventing a successful boot. Looking into all these ifdef items for qcom, since it seems some of them are screwing with other builds.
twistedumbrella
Recognized Developer
- Sep 3, 2007
- 10,994
- 10,398
Argh... I was hoping my logcats would help out on that.
Well in a way it did. It confirmed it is the nativeframebuffer that is tanking, but I am not sure what isn't being called during the build that should, but i also found I some pretty decent errors on all devices that may have had a part in it.
well, im going to try to dive into developing and building roms so hopefully i can be of more help and even build from your github source...that is if i can get everything set up right
and would dmesg provide better data than logcat?
in the meantime, thanks for picking up where kfazz left off, and i think cushzero is going to contact you about the build of ics he is trying to build too
and would dmesg provide better data than logcat?
in the meantime, thanks for picking up where kfazz left off, and i think cushzero is going to contact you about the build of ics he is trying to build too
http://www.github.com/TwistedPlayground seems to be down at least from my phone for the last few days. Any body else seeing that? Or have a link that works?
Thanks for all your efforts.
Thanks for all your efforts.
twistedumbrella
Recognized Developer
- Sep 3, 2007
- 10,994
- 10,398
It's dead for now. Too much going on and changing accounts. It will be back as soon as it is cleaned out.
Sent from my ADR6400L using Tapatalk
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
74new build: http://www.mediafire.com/file/guo6leourklgzgq/cm-9-20120703-UNOFFICIAL-sholes.zip
gapps: http://www.mediafire.com/?ax46kp0yrl85ynn
___________
Don't flash any other kernels. they won't work.
changes:
hexed defy camera libs
HD profile 854x480 green lines in gallery, plays fine on pc
SD profile 640x480, plays fine via gallery
* camera saving null jpegs fixed
* camcorder working
* enabled TLS register user in kernel and userspace
* enabled 1% battery charge display
* lid switch reporting fixed again (haha)
* updated wifi drivers and firmware
* usb storage and adb work
* probably something i forgot
compiled kernel with gcc4.5, userland with linaro gcc 4.7 and -O3
still broken:
camera flash
gps (it was working before. RDS_SOCKET permission issue??)
speakerphone and bluetooth mic routing
HW decode
native tethering
if you like my works, feel free to buy me a beer13http://www.mediafire.com/file/sndcftxoq9g51gd/cm-9-20120712-UNOFFICIAL-sholes.zip
http://www.mediafire.com/file/uuhjaczqiqudqll/deprimed_160mhz.zip
http://www.mediafire.com/file/um9adenv025ip5d/deprimed_180mhz.zip
http://www.mediafire.com/file/k7agmab0uvuf274/deprimed_200mhz.zip
build default is core @ 180 (sgx @ 120)
3 kernels:
core 160 hi 80 low sgx 107/53 ~ stockish speeds
core 180 hi 90 low sgx 120/60 ~ moderate performance increase, good batt life
core 200 hi 90 low sgx 133/60 ~ "battery waster" fast! definitely wont work on all phones. it works on my droid built 9/11/2010, but the other one built 7/19/2011 doesn't.
other changes:
touchscreen? idr if that was in 7/3 build
camera stuff
sw dec
added a few missing bluetooth files
not really much else9overclock breaks camera, backported milestone mt9p012, hp3a, and isp drivers
this fixed camera and camcorder with sgx overclock, and i'm getting higher fps while recording
was 15 , now 20 to 24.
isp now uses an additional 6mb of ram, but i think it's a good tradeoff.
true 720p recording may be possible now
Edit: still freezes... hmm.
Edit:
odexed build is still unstable, it locks up occasionally when the phone goes to sleep, and usually doesn't come back.
no errors in logs, nothing i can check looks out of the ordinary, happens with and without gapps, completely mystifying.9today i ws able to hack in the defy qtouch-obp-ts drivers and enable 5 point multitouch
the new drivers came with new firmware. previously ver 19, new ver 22.
this actually got flashed to the touchscreen controller, it's a one way process, unless someone can dump v19 from their phone.. but
the new ver is compatible with old kernels too, so i don't think it's a big deal.
i also modified the way the driver reports touch events based on moto stingray qtouch driver
this is compatible with ics and jb without hacks.
ics progress: testing an odexed build. it's 20mb larger, but uses 20mb less ram and it's fast! now half of system/app lives on /data
jb: boots. touchscreen is ... weird. no radio audio sensors lights anything really.9figured it out well maybe i don't quite understand it, but it works
problem was in sram34x.S
apparently newer kernels don't modify sdram AC timings because sram code can't guarantee no one is using sram when the clock change occurs, which causes random crashes, or in our case, no boot.
i've also rebased my kernel on deprimed and so far all is good.
still need to test battery life, it's probaly worse, but better than previously posted builds
screen off: ram @ 80Mhz sgx at 53Mhz
screen on: ram @ 200Mhz sgx @ 133Mhz
Edit2 warning was caused by dsp opp2 not being able to be set
dropped dsp opp2 to 160.
