Related
Hey guys!
Because there aren't very many ROMs for our 4X HD, I decided to port Slim Bean from HOX! There are no problems flashing this ROM but anyhow it doesn't boot. I would really like to give you my logcat, but taking a logcat didn't work, too. Maybe there are some developers, who can help? I would really like to see Slim Bean on 4X!
DOWNLOAD:
http://www.mediafire.com/?oqcrkreeqdcerv4
If you have ideas, how to fix boot problems, please tell me what I have to do, or reupload a fixed version!!
Thanks for trying, hopefully someone can help you fix it
Sent from my rooted P880
Thxxxx
Enviado desde mi LG-P880 usando Tapatalk 2
To the op.
What kernel did you use?
Sent from my LG-P880 using Tapatalk 2
babymatteo said:
To the op.
What kernel did you use?
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
I tried with stock cm10.1 kernel and with arararagi's kernel for cm10.1
Maybe i will try it with kholks kernel
EDIT: Doesn't boot with kholks kernel, too
It might not be the kernel.
Sent from my LG-P880 using Tapatalk 2
I think there are some files argueing at boot But without logcat i can't find out which :/
Need!
Sent from my LG-P880 using xda app-developers app
I've got bootloop on my Paranoid 3.X for our LG.
It booted once when I copied nearly all files from HOX rom ( of course aprat form kernel, vendor and some others) but it was unstable and stuff. I'll relase it in a week when it's working. My advice to you is to start from copying nearly all files form HOX rom ( it's so similiar to our LG) and gradually replace needed files from CM 10.1 to fix bugs, make wifi work and stuff.
I had succesfully booted paranoid but it was not usable, had FC's all the time. And when I ported it using standard file copy scheme it gave me bootloop. I'll try to find this sweet spot and will relase it.
Keep up your work, any new roms are aprecciated.
Well, how about compiling, not porting?
One thing I have seen before is people port a ROM for quickness then build it from source while we enjoy the port. Nothing wrong with porting if its a good ROM and its done properly, would do one myself if I knew how
Sent from my rooted P880
Now that my 64 bit Arch machine is working flawless maybe I'll start digging into compiling stuff from source But I will probably fail hard (baaasiiic C/C++ knowledge) let's hope not. But I don't see any sense in making people compile from source instead of porting. If they could do this they would ! But not everyone is a real dev , so be happy with ports they provide us !
Hey nice that more people care about our device! I know it's a little bit OT but I tried to port paranoid from hox to 4X and it also hangs at boot up (bootanimation is shown) ...
I used this tutorial: http://forum.xda-developers.com/showthread.php?t=2232773
There had been no errors in cwm while installing!
I wiped data /cache partion /dalvik cache and format system before flashing....
maybe someone can help me/us
regards nbock
FD1999 said:
Sorry,
we can't tell you much about it. We need the ROM to check if you made a mistake.
From which device did you ported it? Does it has the same screen?
If not, then you need to resize every APK in the ROM or take a Paranoid ROM from a device which has the same screen.
Gesendet von meinem LG-P880 mit Tapatalk 2
Click to expand...
Click to collapse
I know, but my internet is slow, now it finished uploading! Here is the Link: https://www.box.com/files/0/f/839004648/1/f_7762315260
It's portet from HOX (same resolution also xhdpi) and it's paranoid 3.10! Both Roms are 4.2.2 (it's first cm nightly release for 4X as Base!)
HOX has also same cpu and gpu as 4X (tegra3) and so I guessed that it would be the best device to port from!
I tried to logcat while bootup, but adb don't recognize 4X HD (adb drivers uninstalled and reinstalled again!)
I wiped data factory reset /cache partion /dalvik cache and format system before flashing and data /cache after flashing...
No errors in cwm while installing...
I also tried point 8 from tutorial to copy libandroid_runtime.so to base rom and I tried to copy libandroid_servers.so and
libmedia_jni.so to base rom (thanks to tobixdev), but nothing helped - same: stuck at boot!
hope somebody can find the fault and fix it !
regards nbock
hello all, I've just picked up a razr i as a temp standin while my xperia Z is away under warranty repair.
(it was cheap enough to keep too play with afterwards)
is there any reason why no-one has started on CM /PA yet? I've looked through all the posts and can't see anything remotely like a real custom rom..
I'm happy to start working on this (will probably leave it till my Z is back in use though), but would like to get a decent team together to work on it, rather than do it on my own, which is what I've done in the past for a few devices and burnt myself out!
if you're interested then let me know
DO NOT POST
Code:
+1
and me
or
let me beta test !
I want people with a more technical bent than a lot of the users on here to get involved.
for those people, is there anything I'm missing that would stop us building for this?
we have kernel source, and omars kernel looks fairly decent basepoint looking at his git, and some source from motorola that looks sloppily put together.
we can flash with fastboot, and even using blobs it doesn't look too arduous to get at least a 4.1 based build going, so am I missing something?
I'm pretty open on how I work, but I don't tolerate people demanding stuff, or expecting perfection, this will be a W.I.P for a very long time (especially if done on my own).
As far as i know, the problem is on intel processor libs... That's what i've read somewhere around here
Aosp and cm build with some modifications. The phone boots, but in a boot loop on my build. Haven't solved that and will not solve it I think. I have some skills in building, modifying and debugging, but not enough... To get it working. Give it a shot, we can help everyone to get past some certane problems we already solved.
Sent from my GT-P5110 using XDA Premium HD app
Hazou said:
Aosp and cm build with some modifications. The phone boots, but in a boot loop on my build. Haven't solved that and will not solve it I think. I have some skills in building, modifying and debugging, but not enough... To get it working. Give it a shot, we can help everyone to get past some certane problems we already solved.
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
do you have a record of what you've already done (other than the github obviously)?
I couldn't find anything searching ..
anerik said:
As far as i know, the problem is on intel processor libs... That's what i've read somewhere around here
Click to expand...
Click to collapse
fards said:
hello all, I've just picked up a razr i as a temp standin while my xperia Z is away under warranty repair.
(it was cheap enough to keep too play with afterwards)
is there any reason why no-one has started on CM /PA yet? I've looked through all the posts and can't see anything remotely like a real custom rom..
I'm happy to start working on this (will probably leave it till my Z is back in use though), but would like to get a decent team together to work on it, rather than do it on my own, which is what I've done in the past for a few devices and burnt myself out!
if you're interested then let me know
DO NOT POST
Code:
+1
and me
or
let me beta test !
I want people with a more technical bent than a lot of the users on here to get involved.
for those people, is there anything I'm missing that would stop us building for this?
we have kernel source, and omars kernel looks fairly decent basepoint looking at his git, and some source from motorola that looks sloppily put together.
we can flash with fastboot, and even using blobs it doesn't look too arduous to get at least a 4.1 based build going, so am I missing something?
I'm pretty open on how I work, but I don't tolerate people demanding stuff, or expecting perfection, this will be a W.I.P for a very long time (especially if done on my own).
Click to expand...
Click to collapse
hello the problem is that no source AOSP (Cyanogen or AOKP) have x86 libraries and formats, visit www.androidx86.org
if you need a beta tester let me know
The app also must be compatible with x86
The problem I faced was that at the moment of booting it kept restarting netd -- which is odd seeing how the Kernel iptables/ipchains and net configuration is the same on Motorola's one. [info]
I even tried adding and compiling extra modules on the Kernel without much luck -- and it was not the typical ramdisk *.rc files fix here.
Hmm I presumed that with the amount of x86 development boards about there would be a load more work on bringing cm across.
I'll start to have a look at it in depth in the next couple of weeks.
Sent from my XT890 using Tapatalk 4 Beta
On my github I got some work and fixes. Not all of them though. Someone's aren't uploaded yet
Sent from my XT890 using xda app-developers app
Is it easyer to make miui v5?
RAZR i xt890 Tapatalk 2
choppertriker said:
Is it easyer to make miui v5?
RAZR i xt890 Tapatalk 2
Click to expand...
Click to collapse
Harder cause it's not only based on cm10 it's alto different port
For MiUi 4.0 there was the possibility to make a stock based Miui Rom,
There even was one for our Razr i, even though it wasn't very popular.
Is this possibility gone with v5 or is there any other reason not to?
greetings
Killigrew said:
For MiUi 4.0 there was the possibility to make a stock based Miui Rom,
There even was one for our Razr i, even though it wasn't very popular.
Is this possibility gone with v5 or is there any other reason not to?
greetings
Click to expand...
Click to collapse
v4 is different, cause all the porting guides are adapted for it, plus there's miuiv4.1 for razr which is easily portable i guess, but v5 is a whole different matter cause it's based on cm
I will be very happy if anyone port miui 4.1 for our razr, i used it before, on my old phone
If anybody dev could do it i think many ppl will be happy as i.
Wysyłane z mojego XT890 za pomocą Tapatalk 2
Oh yes! Please port miui to razr i. :thumbup:
RAZR i xt890 Tapatalk 2
Personally I will never touch muios with a bargepole
Sent from my GT-N8010 using Tapatalk HD
A real cm or pa build would be awesome! I hope you guys make my dreams come true
Any news fards?
Enviado desde mi XT890 usando Tapatalk 4 Beta
Nope sorry, not yet. been trying to get an aosp build booting from the Motorola code, but it's not happening with that yet. never mind any further progress
Sent from my C6603 using Tapatalk 4 Beta
fards said:
Nope sorry, not yet. been trying to get an aosp build booting from the Motorola code, but it's not happening with that yet. never mind any further progress
Sent from my C6603 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Dont worry bro, i have all my hope that one day we gonna have cm or pa
Enviado desde mi XT890 usando Tapatalk 4 Beta
I got Intel's AOSP Android (4.1.2) to build and then made some binary blob overlays on top. It show the Motorola animation logo on the Phone and then it starts flickering -- I have yet to plug adb to it, but I need to go to sleep soon.
Experimental File, adb enabled at boot: RazRi_AOSP_A001.zip [Flashes boot animation, this is using Motorola's *.prop files, which shouldn't be]
Experimental File, adb enabled at boot: RazRi_AOSP_A002.zip [Have not tried this one, this has safe cflags and default build.prop]
Source: https://github.com/oxavelar/android_device_motorola_intel_smi
Q: Anyone with two phones who knows what to experiment with? I put the instructions to build on the github readme at the moment.
Hello guys
First, big fat disclamier:
THIS IS NOT WORKING. Please don't try this for fun, only if you're willing to put in some time to help me get this fixed.
@djolivier and @letama worked out a way to get CM10 running on Xperia S with locked bootloader, loosely based on the work @atis112 did for Xperia U.
For the past couple of days I've been trying to port it to our beloved T.
It does sort of boot but there is nothing on screen. Logcat is working however and so is adb shell (though no su) so we have some way of debugging.
At the moment there is a working recovery (CWM 6.0.4.6 for locked BL by @davidmarco), enter it by pressing vol+ when the led is blue (it will turn green, then red). Here you will have an su shell and you can get dmesg and /proc/last_kmsg.
Please read the thread by djolivier to get an idea of how it works. In the last couple of pages you will find everything I have tried so far and some insightful answers from letama.
So the main thing now is to hunt down which are the libs/drivers we need.
I will try to get some more info into this thread asap but first I wanted to get it up so those of you who think they can help can get going.
Download
cm10_lb_mint_b12.zip - 188.72 MB
This includes the .489 stock kernel, which is probably the best for compatibility.
XDA:DevDB Information
CyanogenMod for Locked Bootloader, a ROM for the Sony Xperia T
Contributors
TiMiN8R, letama, djolivier
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-08
Last Updated 2014-01-08
Reserved
I think someone starting this off is a great idea, when i have some free time i'll try to offer you some help mate.
But need to get up to speed with it all from djolivier's thread before anything else. But i'm happy to offer some help when i can, if that be testing, or general de-bugging.
This is awesome.keep up Timn8r
Sent from my LT30p using XDA Premium 4 mobile app
How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app
WhiteNeo said:
How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
Letama already helped me a lot over in the other thread, getting it up to this point. But now we need to find some very device specific stuff, that's best left to the people who actually have the device to test and debug. My time is limited this week and I don't have a need for this since mine is unlocked, it's just for the sport, so I figured, let's get some other people in on the action
Sent from my Xperia T using XDA Premium 4 mobile app
now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?
oddeceed said:
now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?
Click to expand...
Click to collapse
Yes that's just about right. We cannot change the drivers in the kernel but what we can do, and what I've been trying to do, is trying to match the drivers in the rom with the kernel, i.e. swapping out CM drivers for drivers from the stock .489 firmware. But there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
letama said:
There is no easy way to solve that I'm afraid. You can try to play with dlls (check this for a list), but it has big chances to fail. The proper way to do that is to get fxp repo, patch hal to match stock kernel and recompile cm.
Click to expand...
Click to collapse
If @Rimmer1966 wants to help he is welcome of course.
TiMiN8R said:
... there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
Click to expand...
Click to collapse
i know less than you and stuck on windows 8.1 which makes it even harder for me to do anything to help .... i hope that this can get up and running ..... providing you can get screen and touch working its more than enough proof of concept of what can be achieved and if enough different devices get going this way then maybe just maybe teams like CM will revert back from thier custom kernel (which i dont like) and start using stock kernels in builds (we can all dream right?)
Any updates on this? I can help as a beta tester or help with building on my pc.
masterjet said:
Any updates on this? I can help as a beta tester or help with building on my pc.
Click to expand...
Click to collapse
Not much going on on my end. I've been running on the leaked stock 4.3 for the last few days. I did have a little go on using the kernel from that rom to boot CM10.2 but I've not made much progress, seems that SELinux is throwing a spanner in the works.
If anyone wants to have a go, here's what you can do. Get the stock .489 here.
We should try swapping out .so in /system/lib/hw one at a time. You can do this by booting to CWM, mount /system and adb push, chmod 0644 the file and reboot. Get a logcat, reboot to CWM and get dmesg and last_kmsg
Code:
adb logcat > logcat
adb shell cat /proc/last_kmsg > last_kmsg
adb shell dmesg > dmesg
Lather, rinse, repeat. It is a slow and tedious process, so the more the merrier
TiMiN8R said:
I replaced hwcomposer.msm8960.so, that seems yo have fixed it. Also tried a couple of others that didn't work: gralloc.msm8960.so (can't start), copybit.msm8960.so (brought back the camera probs). Still no screen.
Most prominent spam now is
Code:
smd_pkt_open: DATA5_CNTL open failed -19
I also noticed this in logcat
Code:
I/clearpad_fwloader( 681): hanlde_arg: option = [default]
I/clearpad_fwloader( 681): hanlde_arg: saved.module_id = [0x32]
E/clearpad_fwloader( 681): read_sysfs: Unable to open /sys/devices/virtual/input/mice/name
E/clearpad_fwloader( 681): read_sysfs: Unable to open fwfamily
That is the touchscreen. There is indeed no /sys/devices/virtual/input/mice/name. I'm not sure if it is related to the no video issue but it's a problem nonetheless.
Click to expand...
Click to collapse
Thread is dead? No updates, no progress?
masterjet said:
Thread is dead? No updates, no progress?
Click to expand...
Click to collapse
Seems a bit of a dead end. Our stock kernel just seems to be to different from the stock kernel.
No-one else seems to want to pitch in and try some stuff out.
Might have another go with 4.3 when the official Sony's finally out.
it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?
like i mentioned before
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow
lordyka said:
it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?
Click to expand...
Click to collapse
If you had read the other thread, you would have known that I've already tried a lot of .so's from stock firmware but nog all of them work. This is the hard part, finding the ones that work.
jewkhok said:
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow
Click to expand...
Click to collapse
Well the first part, the hijacking, is exactly what does mod is doing. With regards to the 2nd-init program, I'm not sure that init itself is the problem. The "only" problem we have is finding drivers/libs that are compatible with both CM and stock kernel. But I could be off though. If someone wants to build us a 2nd-init go right ahead
Wow just came back to the T forums to see how things were going and I see this! Hopefully Tim can port it I'm sure he can
Sent from my XT1058 using Tapatalk
I honestly don't think 2nd init would make a big difference, as TiMiN8R has already stated, the problems are the drivers. You can now either ask FXP to use drivers from the Sony 4.3 Stock kernel or do it yourself...
Good luck on this, you'll surely make it.
Gesendet von meinem Xperia S mit Tapatalk
got the source codes?
I'm thinking about doing the same with Z1, wouldn't mind take a look at your work
If you asked me: here are the sources.
Gesendet von meinem Xperia S mit Tapatalk
Hello, if any developer can build drivers for solana 4.4.x, I can build any rom what u want, I think that the DROID RAZR XT910/912 have similar hardware, and camera and wifi and some others things, but I don't know how to build kernels, so if anyone knows how to, or anyone build a kernel(and necessary files for Android 4.4.4) please tell me and inmediatly I'll build a lot of roms for our device.
Sorry for my English.
Regards, Tony
PD: And if anyone knows where are the repos of Liquid 4.4 i'll be very pleased
help is here...
tonyt. said:
Hello, if any developer can build drivers for solana 4.4.x, I can build any rom what u want, I think that the DROID RAZR XT910/912 have similar hardware, and camera and wifi and some others things, but I don't know how to build kernels, so if anyone knows how to, or anyone build a kernel(and necessary files for Android 4.4.4) please tell me and inmediatly I'll build a lot of roms for our device.
Sorry for my English.
Regards, Tony
PD: And if anyone knows where are the repos of Liquid 4.4 i'll be very pleased
Click to expand...
Click to collapse
dont know if i can build a kernel but i can offer u my assistance in probably building a rom. there is already a kitkat rom for the D3 but the wifi & storage doesnt work, can u fix that? i'll give u the link to my rom site where lyes all the D3 roms look for the ls kk rom and maybe u could take that and maybe build a new one from it, the rest are jellybean roms maybe u can use that idk. https://www.mediafire.com/folder/b0gq735hrqxx6/Droid_3_ROMS
I'll build a rom for Solana(droid3) but I don't have the phone anymore, so if anyone wants to be a tester I'll upload it. Please note that I don't have the phone anymore so if this brick your phone I'm not responsable, in order to not to brick, please use slot-1 or slot-2, but not stock(in this way you can evade a brick).
anyway, those who wants to try this please tell me and when the rom finish building I put the link.
and another thing is:
I don't know a lot of English especial words, so I can't understand this:
http://forum.xda-developers.com/showthread.php?t=1943625
because we need a new recovery, we have a older release, to build the SAFESTRAP you can use this:
https://github.com/stargo/android_bootable_recovery
https://github.com/stargo/android_packages_apps_Safestrap
this is the lastest but I don't know how to build it.
If you want to use Lollipop anyone have to compile this SafeStrap.
tonyt. said:
I'll build a rom for Solana(droid3) but I don't have the phone anymore, so if anyone wants to be a tester I'll upload it. Please note that I don't have the phone anymore so if this brick your phone I'm not responsable, in order to not to brick, please use slot-1 or slot-2, but not stock(in this way you can evade a brick).
anyway, those who wants to try this please tell me and when the rom finish building I put the link.
and another thing is:
I don't know a lot of English especial words, so I can't understand this:
http://forum.xda-developers.com/showthread.php?t=1943625
because we need a new recovery, we have a older release, to build the SAFESTRAP you can use this:
https://github.com/stargo/android_bootable_recovery
https://github.com/stargo/android_packages_apps_Safestrap
this is the lastest but I don't know how to build it.
If you want to use Lollipop anyone have to compile this SafeStrap.
Click to expand...
Click to collapse
i can test it
dreikk91 said:
i can test it
Click to expand...
Click to collapse
The link is this: https://mega.co.nz/#F!vc0nyYZB!xXaGdS0Xyvy4zZq7U4FdJA
but the file will be online in about 2 hours, If the zip didn' flash correctly please use the "meta-inf" folder that uses LS KK(for solana obviusly)
LS KK(to extract the meta-inf):
I think that camera wont work, but I only want to see if kernel works
dreikk91 said:
i can test it
Click to expand...
Click to collapse
I can test it too. But since I know nothing about android applications compilation, all I can do is just flash a zip prepared by someone else, and report it behaves.
By the way, thank you. I thought Droid 3 development died. If only somebody was able to provide working camera modules...
rabinhood said:
I can test it too. But since I know nothing about android applications compilation, all I can do is just flash a zip prepared by someone else, and report it behaves.
By the way, thank you. I thought Droid 3 development died. If only somebody was able to provide working camera modules...
Click to expand...
Click to collapse
I only know three developers that can do it, Hashcode and Dhacker and @dtrail1 but Dtrail is not developing now
hi,i test AOSB, the kernel does not boot, after the SS logo nothing happens. To install had to take a meta-inf from LS KK
After some changes I can to run your build. Everything works fine, except that the home button is not properly assigned
HD codecs do not work
seems to be a problem in the modules arm_kexec.ko kexec.ko and uart.ko
the kernel just does not work
By google translate:cyclops:
Droid3 is a god qwerty device too bad no Roms here...
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Androide3 said:
Droid3 is a god qwerty device too bad no Roms here...
Click to expand...
Click to collapse
I am also disappointed a bit. I came from Milestone 2, which is older, but still under development, even though it rests in 'legacy devices' forum. But existing ROMs for Droid 3 are fast and stable - i.e. Minimoto which I'm using now. No KitKat? Yeah, but who cares for KitKat?
I would love to see a 4.4.4 rom for the droid 3 or a 5.0 rom. I will gladly test.
cm11
Hi, compiled from source cm11
As usual is not working the camera and HD codecs
Because of old safestrap had to change the updater-script, so do not be surprised inscriptions liquid-smooth at steady
By the way would do well if someone compiled new safestrap
https://yadi.sk/d/J1fCNC3MdkrdZ
By Google translate XD
dreikk91 said:
Hi, compiled from source cm11
As usual is not working the camera and HD codecs
Because of old safestrap had to change the updater-script, so do not be surprised inscriptions liquid-smooth at steady
By the way would do well if someone compiled new safestrap
https://yadi.sk/d/J1fCNC3MdkrdZ
By Google translate XD
Click to expand...
Click to collapse
Exellent can yo send me the device, and kernel files? The problem is that safestrap is using kexec kernel, so we can't compile like otee omap4 devices, anyone have to talk to @stargo to build a new safestrap
Enviado desde mi iPhone utilizando Tapatalk
tonyt. said:
Exellent can yo send me the device, and kernel files? The problem is that safestrap is using kexec kernel, so we can't compile like otee omap4 devices, anyone have to talk to @stargo to build a new safestrap
Enviado desde mi iPhone utilizando Tapatalk
Click to expand...
Click to collapse
Device files is here https://github.com/dreikk91/android_device_motorola_solana
Kernel here https://github.com/STS-Dev-Team/android_device_motorola_omap4-common
You can also use my defconfig https://yadi.sk/d/ZVKjeaMJdksTr
dreikk91 said:
Device files is here https://github.com/dreikk91/android_device_motorola_solana
Kernel here https://github.com/STS-Dev-Team/android_device_motorola_omap4-common
You can also use my defconfig https://yadi.sk/d/ZVKjeaMJdksTr
Click to expand...
Click to collapse
Okay, thanks a lot!!, let me see what can I do, this repos may work for CM12, but first we need the new SS, to build it see this:
https://github.com/stargo/android_bootable_recovery
https://github.com/stargo/android_packages_apps_Safestrap
Would be nice to have cm12 on Droid 3
corby2geek said:
Would be nice to have cm12 on Droid 3
Click to expand...
Click to collapse
yes, it would be nice, but without the new safestrap will not work
Alternatively, you can compile the CM12 for droid 3 and install it on another device with a new safestrap and then upload system.img here
Anything new on a new ss and cm12?? I would love to see lollipop for the droid3. I currently run liquid smooth kk, not too bad.
dreikk91 said:
Hi, compiled from source cm11
As usual is not working the camera and HD codecs
Because of old safestrap had to change the updater-script, so do not be surprised inscriptions liquid-smooth at steady
By the way would do well if someone compiled new safestrap
https://yadi.sk/d/J1fCNC3MdkrdZ
By Google translate XD
Click to expand...
Click to collapse
I like this better than liquidsmooth btw what gapps to use??
Josephdbrewer25 said:
I like this better than liquidsmooth btw what gapps to use??
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2240652
I wonder why on kernel 3.0.8 do not work HD codecs. Tried to run on kernel 3.0.31 cm11 system does not work very well, but the codecs are working properly. I can not understand how you need to do to earn codecs
Welcome to the official thread for the Lollipop roms for our Optimus 2x
As to start, this thread is exclusively for the developers who are interessted/working on on the Lollipop ports for our Optimus 2x
We had alredy some build like the OmniRom , CM12 and even ParanoidAndroid.
This thread is exclusively for discussions for the developers and for the testers to test the new made roms so I will update the links as the roms get made. So I am only posting here the links of the latest version, to get the versions from the past you wil need to browse throught this thread
Update 05/6/2016
Gucky did it again! New build for CyanogenMod 12.1 is up, and now with fixed camera! When I get the full list of working features and bugs, I will upload it here. Thank you Gucky for your massive help and contribution to this community. This device is very old after all, and you still find the time to tinker on it. No words really. Respect!
CM12.1 : https://sourceforge.net/projects/lg...cm-12.1-20160531-UNOFFICIAL-p990.zip/download
WARNING the Rom is still not stable, but we are close!
ParanoidAndroid: https://s.basketbuild.com/devs/Puri/p990/AOSPA(lollipop)
Take in mind that all these roms are unstable besides the CM12 rom,but it still has some major bugs which we as a group will fix.
As in all of this, stay tuned for updates
Good job my friend
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
um
gucky01 said:
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
Click to expand...
Click to collapse
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Could you please share your sources.
TheMysteryouse said:
Hello everyone.As you might know me from some threads where i comment some stuff.Anyways, since Lollipop was announced i was obssesed with it and my wish was that i would be the first one to make the version availble for our device.
Well i kinda did it....KINDA of course but we need some help if we wanna make it work.I call ALL of the developers for our device to work together to make it work.We are so close to get it fully booting.I made it boot to the animation and now where the help comes in use.We need some developers who can enable ADB on our device in the bootanimation.TO be honest i dont really know anything about sources and that stuff but i know some things.With the help of @tonyp and @timduru which I am the most thankfull of that gave me hope to make this.So here we go!
WARNING!!!
ONLY FOR DEVELOPERS
No one should download and flash this rom because you will get stuck in the bootanimation and will need to install previouse rom again and install everything over...blah blah blah.
Also the link to the rom is here ----> https://www.dropbox.com/s/fwhg08ux7qhtgsh/5.0 test.zip?dl=0
So if someone gets it working, please pm me in the progress. Cheers
Click to expand...
Click to collapse
TheMysteryouse said:
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Click to expand...
Click to collapse
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Oh
Hugo-PT said:
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Click to expand...
Click to collapse
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
TheMysteryouse said:
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
Click to expand...
Click to collapse
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
nope
gucky01 said:
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Click to expand...
Click to collapse
nope, didn't touch anything other than the updater script i think and the build prop because i wanted fully stock experience
I can be your tester my phone got a battery problem so im having fun with flashing roms
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Well, it might be that he used KatKiss from timduru for the TF101 which has a Tegra 2, but still our phone uses the Tegra 2 AP20H, while the TF101 uses Tegra 2 T20. Small difference in the chipset, but still a difference. Easiest would be to port from the Galaxy R or Captivate Glide, but they too struggle with Lollipop over in their forum. Anyway, TheMysteryouse used timduru's AOSP rom, so maybe it would be easier building the whole thing from the demo CM12 sources available.
nonono
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Nope, this rom has NOTHING to do with the tegra 3 rom.I used the rom for TF101 tablet which is tegra 2 but had a cmall chipset difference.So yeah I am still trying to do some things like searching the framework sources from tony to see if he has a code in the build.prop which directly enables ADB from the boot, but cant really find it.Anyways try your best and so the others.Cheers
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Any video or screenshot? xD
Sorry for nob request, but working well or not, its great to our comunity
p.s. if need tester in future, you, TheMysteryouse or DJNoXD.
Im ready for
...WoW!...That´s Good News...Thank You for All of You, Guy´s...
gucky01 said:
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Click to expand...
Click to collapse
Awesome news buddy! Lollipop on first power dual core android device! Switch to 1+ One as a primary phone for some reason but I will continue to follow and supporto you!
That is great!!! ))))))))
Ok. I have to go one step back. The rom is not ready for the testers and I'm too tired to test more. For those, who want to repeat my steps or want to finish...
I replaced the files in Mystery's rom with my own Kitkat ones. The first half, than the second. Now I could get it to finish the booting process. This steps I went on and on. So I could reduce the problem to the framework-files in "system". If you replace all of them, it boots up with some error messages.
I think we have to reduce the 40 files inside more and more to find the reason for the bootloop.
All the best to you,my friends!
Damm this is great a device from 2010 receives android L. 4years later. If I can borrow the old optimus 2x from my father then I could also look into the problems if it's not booting yet then. Till then continue your work.