Related
THIS THREAD IS DEPRECATED.
This project has move down, out of the alpha stage, to here:
http://forum.xda-developers.com/showthread.php?t=1950453
This thread is here for documentation purposes only! There are better builds at the new link, more detailed instructions, and support. Please direct your attention there! Thank you.
Warning! Flashing this may/will delete your /efs, which will causes major issues if you ever decide to return back to stock, so make sure you make a backup! If you don't know how, frankly you shouldn't flash this, as you need at least some experience just in case something goes wrong.
Team SuperNOva:
Oisis (helped us get over the final issue)
Zaclimon (first kernel dev, did a LOT of the preliminary work)
Neyodmium (helped us sort out that SGS sources that CAN be used for the 4.0, and helped pinpoint what needed to be replaced/fixed)
Me, hanthesolo (Rom dev, I will be providing updates, support, and other smaller things, so they can concentrate on the kernel, while I fix up the ROM)
The Back Story:
Firstly, excuse my cheesy biblical writing, I just have always wanted to write something in that format .
In the beginning (march 2012), there was hanthesolo. He saw the Galaxy Player forums, and all that he saw was good. This man started creating new work for the Gplayer forums, a and gained a small following. There was just one issue that concerned him: NO ICS!
In light of this, this man created a thread, to collect all ICS development, into one easy-to-read forum. Other began to follow him, zaclimon, Ijimaniac, and several others. Ideas flew fast and furious, but hope was waning quickly. A kernel would have to be created from scratch, a monumental task that had not been undertaken by any man so far.
All was quiet for awhile, and people began to slowly fade out, until only hanthesolo and zaclimon remained, slowly trading ideas and guesses over several weeks. Then a new disciple arrived: neyodmium. This korean (?) developer brought a different kind of kernel experience to the trio, and development began in earnest, with zaclimon and neyodmium trading work, while hanthesolo contributed where he could. One unsurmountable issue arose: this magnificient kernel, the likes of which had never lit up these forums before, would merely boot into recovery, not into Android.
Then Oisis came around, hearing our desperate cries for help. Like a moses, he guided his flock in the right direction, squashing issue after issue, until a monumental day arrived: August 13, 2012. On this day, ICS was finally created in Cyanogen's own image, and it was good.
Then increased development began, with hanthesolo squashing CM9 bugs, while zaclimon, neyodmium, and Oisis working feverishly on the kernel.
But an issue occurred, a wrench in the works. Thine enemy's name is GL, SuperNOva. GL would not cooperate, acting as a barrier between usable ICS, and frustrated efforts to fix it. But one day, the magical variable was flipped, and the builds booted! About this time there was a github mishap involving a bad I9000 push that stopped things for about a week, but that's another story.
What happens next? I dunno, but I will update this story when it happens .
NOTE: This does NOT represent anyone's political or religious standpoint, or the way anyone is viewed. It was created as a humorous way to explain our situation to users.
The fix list:
ROM:
Bluetooth (should be easy)
HW acceleration (easy, just neds to be implemented)
Camera (will take awhile)
Kernel:
HW acceleration (Oisis is working on it)
Drm manager (needs to be fixed before market can be used!)
US home button
Boot to recovery (very annoying when trying to flash builds)
Camera (?)
Changelog:
Build#1:
Initial release, basically everything is broken.
Build#2 changelog:
Finally fixed bootlooping that was plaguing our github
fixed ALL GL crashing and oddness
Fixed/improved sound (if it was broken)
Fixed Browser (slow, but usable)
Waiting on a new kernel to readd GL and/or HW acceleration.
FM radio! Just download the spirit FM app, you can find it for free on XDA
Build#3 changelog:
Fixed av codecs (videos should play just fine now, as well as youtube)
General code cleanup and optimizations
Build #3.5:
Performance improvements and some code cleanup.
Download links:
Build#1:
CM9: http://www.broken-arrow.pl/oisis/aokp/YPG1-CM9-OiSiS-build-02.zip
Kernel: http://zhshibenzhu.host22.com/tuchuang/cm9_kernel.tar
Build#2:
CM9: http://www.mediafire.com/download.php?lu33uubm6der2j9
Kernel: Flash the one above.
Build#3:
http://www.mediafire.com/download.php?96yk0e3y8cqzj1b
New kernel: http://forum.xda-developers.com/attachment.php?attachmentid=1298676&d=1346633739
Build #3.5: http://www.mediafire.com/download.php?oscyfde4w364dj6
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
If you get stuck in recovery, flash a GB kernel, it will boot into recovery, simply hit "reboot". When it bootloops, boot into download and flash the CM9 kernel.
Resources:
Manifest.xml (so you can just simple "repo sync" instead of git pulling every time we have a new commit):http://forum.xda-developers.com/attachment.php?attachmentid=1278615&d=1345762041
Wiki link (please help improve it!): http://forum.xda-developers.com/wiki/YP-G1
Github repo: https://github.com/TeamSupernovaSGP
NOTE: this is just the modded files. You need to full CM9 source before you can compile!
Contact us at: [email protected]
Please only emails us with valid questions or useful support!
port kernel 3.x from Galaxy S to SGP4.0 should be easy, coz hardware parts are almost the same, but SGP5.0 conpoments arent the same, the way for SGP5.0's 3.x kernel should be harder.
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Would it not be easier to port over a rom, as the hardware is the same? It would at least be more helpful, because if we could create a guide, we could port other roms over very quickly!
Sent From my Galaxy Player running StratusRom using XDA
klin1344 said:
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Click to expand...
Click to collapse
I built it and I will test to see if it works (I'll use the newest kernel from cm7)
I am going out on a limb here...could we use the cm7 kerbel to help port a workable ics kernel for a galaxy s port? Once thats done cooking up a working rom should be easy and quick.
Sent From my Galaxy Player running StratusRom using XDA
One thing
Ambitious project hanthesolo
one thing: could i suggest that the title of this thread should be Operation: ICS for Galaxy Player 4.0 or something?
Okay, I may rename it. ICS is far more feasible than you think. Once we get a working kernel running (which will be soon) we can port ics over from the galaxy s (which would be best, as once it boots most features would work). I hope by the time school starts up ics will be functional as a daily driver. I may not be able to help a ton, as most of this revolves around making a working kernel, but I will try to help where I can.
Sent From my Galaxy Player running StratusRom using XDA
I can't get it to boot. (stuck at samsung logo) I think it would be better to build it from source instead of porting over.
Its stuck at the samsung logo because the kernel probably didnt work. It has happened to me before, we need to compile an ics kernel. The galaxy s one almost works, we just need to find out what makes it fail to boot.
Sent From my Galaxy Player running StratusRom using XDA
We can use the BML/STL partition layout in waiting for yaffs2. We can use entrophy's device tree as base for it(we can ask for help from him too)
https://github.com/Entropy512/android_device_samsung_infuse4g
Thanks for looking into that zaclimon! I will pm him and see if he would be interested. I willxupdate the opxwoth info from various people/sies as I get it.
Sent From my Galaxy Player running StratusRom using XDA
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
rozelle25 said:
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
Click to expand...
Click to collapse
I dont quite understand what you mean. Can you elaborate please?
Sent From my Galaxy Player running StratusRom using XDA
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
minipot said:
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
Click to expand...
Click to collapse
If it was that easy, webwould have ics today on our devices. The reason its been so difficult is that we need to combine/port githubs to create a working kerbel, which is a lot harder than it sounds. Thanks for the link! I will put it in the op.
Sent From my Galaxy Player running StratusRom using XDA
Im guessing u mean we could make a rom using that but first we need a kernel that qill work with it
Yeah. Porting a rom is easy, but getting a working kernel is not. Once we get a working kernel we can port as many roms as we please.
Sent From my Galaxy Player running StratusRom using XDA
Well I don't think it is that hard if we base ourselves from other devices trees like entrophy's one. I think he removed RFS from his initramfs which leaves him only ext4. Then he used a script that would convert the partitions to ext4 when installing CM9. I think it is the same things than with the mmc partitions (I think this is a part of why the 5.0 got ICS sonner than 4.0)
EDIT: And I think it's better to build it from source the first time. (instead of porting for the case of CM9 for example.)
Yeah, I was just talking comparatively. Has anyone begun working on this yet? I have been researching a LOT (the best thing I can do to help right now), but since my knowledge is limited on kernels, i cant help with that riht now
Sent From my Galaxy Player running StratusRom using XDA
Just like the Xpera P & Sola I've also considered to make a Thread....for the Port Jelly Bean to Galaxy Ace 2 from Galaxy SIII Mini :fingers-crossed:
It's know that our Galaxy Ace 2 is a device with Novathor u8500 SoC chipset
and right now, i'm pretty sure that Samsung will provide Jelly Bean for our device next year. But, we also know that there out is a device with our same chipset and Jelly Bean at launch. Yes, i'm talking about Samsung Galaxy SIII Mini. I have been talking with some users on their forum and i think some information can help us to port jelly bean to our Galaxy Ace 2
So, here are some files which can help us to make a working Jelly Bean Rom on our device:
1. I want to thanks nixonik member to provide a full system dump of SGSIIIMini in here System dump.
https://docs.google.com/file/d/0B-S6...d6cDVsb00/edit
2. Jelly Bean open source code for this rom, provided by Samsung.
in HERE http://d-h.st/c1n
Now that would be really great if some devs step up to initiate this.
You might get some More Info/Help at the Guys at Xperia U,Sola,P,Go threads
Xperia U thread - http://forum.xda-developers.com/showthread.php?t=2055883
Xperia P thread - http://forum.xda-developers.com/showthread.php?t=2057087
Xperia Sola - http://forum.xda-developers.com/showthread.php?t=2047945
Xperia Go - http://forum.xda-developers.com/showthread.php?t=2058766
Awesome awesome AWESOME...now this is some great news..let's show the galaxy w users what ace 2 is worth
EDIT: And be4 ppl start wondering and sayin stuff I said that cuz I had read some complaints on galaxy w forums about w deserving jb more than ace2
Thread cleaned.
Kindly do not flame the OP for opening collaboration projects which benefit the community.
Thanks,
Jonny
I think Ace 2 and SIII Mini's SoC are not EXACTLY alike but many of us expected to use the SIII Mini for the ongoing project of porting AOSP Jelly Bean to Ace 2 but we've had no luck since many believed that SIII Mini won't help that much with the port so the project has been stalled and we've been waiting for at least an update to the S Advance (or at least a leak we could port) or an official Ace 2 update. I don't really know where this is going but I don't really have my hopes up for Jelly Bean on Ace 2, well at least not until next year.
Dr01nE said:
I think Ace 2 and SIII Mini's SoC are not EXACTLY alike but many of us expected to use the SIII Mini for the ongoing project of porting AOSP Jelly Bean to Ace 2 but we've had no luck since many believed that SIII Mini won't help that much with the port so the project has been stalled and we've been waiting for at least an update to the S Advance (or at least a leak we could port) or an official Ace 2 update. I don't really know where this is going but I don't really have my hopes up for Jelly Bean on Ace 2, well at least not until next year.
Click to expand...
Click to collapse
We just need someone to modify the ram disk.
Sorry if i spam, but when JB is a problem for now, what abou ICS port?
Sent from my GT-I8160 using Tapatalk 2
forbidden8 said:
Sorry if i spam, but when JB is a problem for now, what abou ICS port?
Sent from my GT-I8160 using Tapatalk 2
Click to expand...
Click to collapse
Since jelly bean can't be ported...how is ics supposed to?(I guess)
mojito0 said:
Since jelly bean can't be ported...how is ics supposed to?(I guess)
Click to expand...
Click to collapse
Bcoz other device's, like xperia u and other xperia phones. They have same hardware like Ace2.If the S3 mini is not... dont know; just thinking.
Sent from my GT-I8160 using Tapatalk 2
forbidden8 said:
Bcoz other device's, like xperia u and other xperia phones. They have same hardware like Ace2.If the S3 mini is not... dont know; just thinking.
Sent from my GT-I8160 using Tapatalk 2
Click to expand...
Click to collapse
Ahh yeah sorry you're right, xperia u only has ics and not jb, my bad
That wouldn't work, their kernels are different, their libs, drivers, RIL interface and wrappers are also different. They don't even use the same chipset model and have a totally different board configuration with different components. Their specifications may appear to be similar on paper but it's a different story when it comes to internals.
And Jelly Bean requires Kernel 3.x, it's something that we don't have for the Ace 2 yet and porting a whole kernel from another device running the same chipset is almost impossible. Without kernel 3.x a whole load of things won't work, that obviously includes Vsync (which is totally incompatible with the current Kernel 2.6). We don't even have the device-specific JB sources for the Ace 2 so a lot of things won't work even if someone gets JB booting. Basically what needs to be done:
(1) Get it to boot with a custom 2.6 kernel/experimental 3.0.x (if built)
(2) Fix primary/critical hardware-specific code for the novathor chipset (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
(5) Fix camera HAL
Gonna be hard without the device sources.
Thanks for this little explanation yowanvista and yes it is gonna be hard and what about galaxy advance ? is this devise really different from ace 2 ?
yowanvista said:
That wouldn't work, their kernels are different, their libs, drivers, RIL interface and wrappers are also different. They don't even use the same chipset model and have a totally different board configuration with different components. Their specifications may appear to be similar on paper but it's a different story when it comes to internals.
And Jelly Bean requires Kernel 3.x, it's something that we don't have for the Ace 2 yet and porting a whole kernel from another device running the same chipset is almost impossible. Without kernel 3.x a whole load of things won't work, that obviously includes Vsync (which is totally incompatible with the current Kernel 2.6). We don't even have the device-specific JB sources for the Ace 2 so a lot of things won't work even if someone gets JB booting. Basically what needs to be done:
(1) Get it to boot with a custom 2.6 kernel/experimental 3.0.x (if built)
(2) Fix primary/critical hardware-specific code for the novathor chipset (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
(5) Fix camera HAL
Gonna be hard without the device sources.
Click to expand...
Click to collapse
oh my god! .... Jelly bean was working on motorola defy with 2.6 kernel and TOTALLY LOCKED bootloader....
espaciosalter20 said:
oh my god! .... Jelly bean was working on motorola defy with 2.6 kernel and TOTALLY LOCKED bootloader....
Click to expand...
Click to collapse
Sure it can, even my i9001 works with CM10 but Vysnc is broken (and will always be unless a proper Kernel 3.0.x is used). However it seems pointless to use a dated kernel with a whole load of compatibility patches and reverse wrappers here and there just to fill the gaps. It would be better to use a fully fledged Kernel 3.X with everything already set in place, proper drivers and libs without having to look elsewhere trying to port & adapt specific code for the Ace 2. We'll have the official JB sources next year so it's useless to hit your head against a wall trying to figure out how to make a half-baked kernel without the required pieces of code. With the new sources development will be easier, porting CM10.1 will easier too, it's better to wait imho.
JB for Galaxy S Advance is now available
i think this might help. Galaxy S Advance is now receiving JB update. DOWNLOAD LINK
Here's the news: LINK
Only **** ! nice !!!
we still don't have kernel sources to work on it;
mkel91 said:
we still don't have kernel sources to work on it;
Click to expand...
Click to collapse
samsung release source i9070 in opensource samsung web
Sent from my GT-I8160 using xda premium
hafidzduddin said:
samsung release source i9070 in opensource samsung web
Sent from my GT-I8160 using xda premium
Click to expand...
Click to collapse
I found only gb sources on the opensource.samsung website. Where you saw jb sources?
strofo said:
I found only gb sources on the opensource.samsung website. Where you saw jb sources?
Click to expand...
Click to collapse
i9070 is s advance not our devices. but we can use it
cocafe tell me he got i9070 source kernel jb
Sent from my GT-I8160 using xda premium
soo what exactly is this new kernel? I can't find changelogs anywhere, just the file to download o:
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
Hey guys,
So, I'm not a dev, but I'm dying for a port of CM9 for the P769. In the Original Android Development forum, there appears to be someone working on CM10, which is great and all, but we actually stand a chance of getting all the hardware working under CM9.
Just out of curiosity, I meandered over to LG's open source website and -- lo and behold -- quite clearly I see the source available for not just the P769BK, but other variants as well. I downloaded it, and it even includes instructions for building.
So... is this not the source we need for a CM port? Please, strike down my ignorance and let me know what's up.
https://wws.lg.com/global/support/opensource/opensourceList?types=MODEL&search=P769
That is what we need and the dev has it. We have a good chance of CM10 working because the source is available. So there is no big push for CM9.
kevev said:
That is what we need and the dev has it. We have a good chance of CM10 working because the source is available. So there is no big push for CM9.
Click to expand...
Click to collapse
Excellent! I was under the impression that devs needed 4.1 sources from the manufacturer to build fully functional CM10 images. The more you know!
orrorin said:
Excellent! I was under the impression that devs needed 4.1 sources from the manufacturer to build fully functional CM10 images. The more you know!
Click to expand...
Click to collapse
I'm not the most knowledgable about rom development and such, but it seems that if at least Android 4.0 source is available for a certain device, then it may be easier for devs to bring JB to that device and/or build a fully working JB rom for it.
Was doing some poking around myself today and noticed that LGP769BK(Optimus L9)_Android_JB_P769v20d.zip
was up on the LG open source page. Was able to DL it and upload to dev-host if they pull it down later but its listed there for now.
Don't know if I'm late to the game or not but I didn't find anything during my real brief search that it had been noticed yet
link removed because XDA hates me
Out of curiosity i have been compiling CM10.2 for the last 2 days, and it now compiles successfully 100% (after many repo sync), but the thing is, when it's installed it doesn't even go past the S4 Bootlogo.. that's just sad, it's like the init file (ramdisk) is wrong so I tried the one from the aosp 4.3 ge builds, but that also didn't work, but it's probably not that. I don't know what it is, but of course without any logcat it's hard to find.
even my AOSP 4.3 compiled build went further than that.. it just showed me a black screen cause of the wrong egl libs but it showed a logcat at least. with the major errors of libc being faulty etc. (but it went further than CM.. in the early stage when there were almost no cm patches for cm10.2 yet)
Oh and yes I did include the proprietary files, and found that some of them don't even exist on the original 4.3 rom, so that's kinda lame..
here are the missing ones:
lib/libqmi.so
lib/libqmiservices.so
lib/libqmi_cci.so
lib/libqmi_common_so.so
lib/libqmi_csi.so
lib/libqmi_encdec.so
lib/libqcci_legacy.so
lib/libqmi_client_qmux.so
lib/libreference-ril.so
lib/libril-qcril-hook-oem.so
lib/libsecril-client.so
lib/libtime_genoff.so
lib/libWVStreamControlAPI_L1.so
lib/libidl.so
lib/libivxdrm.so (was spelled wrong by cm, it includes capitals)
that's a lot of libs, does someone know if one of them could be responsible for not going past the boot logo?
I can upload my build if anyone wants it but it does nothing so it's kinda useless
Any useful is appreciated very much! :silly:
just wait awhile..
xZain69 said:
just wait awhile..
Click to expand...
Click to collapse
Yes I will of course, and I have no problem with that. I'm just curious what the reason is for it not to boot at all. I want to learn as much as possible about the android system so that includes this
kernel problem ?
show this
http://forum.xda-developers.com/showthread.php?t=2348733
Syncing CM10.2 Sources now
Most of the low end devices have got 4.3 booting like HTC Pico and Optimus L5 etc.
PS: In HTC Pico CM10.2 Rom only BT and Camera is broken so I am sure we can get a fully stable one in a few tries. Obviously, we have to fix bugs
This thread over here at m919 has got cm10.2 working, well sort of. Check this out. http://forum.xda-developers.com/showthread.php?t=2348733
~~~~~~~~~~~~~~~~~~~~~
I am always on the mobile app and am always 'trying' to help others and moderators on the forum and learning something new everyday. I make stupid posts sometimes, but I never repeat a mistake more than once. I may not be a developer, but I know alot of stuff, so feel free to messsge me any questions and I'll be happy to answer them to the best of my ability.
~~~~~~~~~~~~~~~~~~~~~
I'm starting a video game company with my friend where we will be making Android games. message me for more info or go here: http://forum.xda-developers.com/showthread.php?t=2290843
got it working