Related
i had a motorola defy with locked bootloader. There were no hope for updates and for custom roms. Till dev (quarx) did it. Now defy has jelly bean (cm10). Lets search for devs and make a donation app, so they can buy our phone add develop one great rom.
Great idea, but do we have enough people? No one will buy the phone if we can donate only ~100€
well, not to develop ROM, but better to sacrifice their/his phone to try unlocking bootloader..
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP880
we've now source code, i think it'll help us
reas0n said:
well, not to develop ROM, but better to sacrifice their/his phone to try unlocking bootloader..
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP880
we've now source code, i think it'll help us
Click to expand...
Click to collapse
Yes it will...well at least for a custom kernel i think. Still, drivers have to come from Nvidia. And everyone knows about their reputation when it comes providing open source codes and such.
ukramch said:
i had a motorola defy with locked bootloader. There were no hope for updates and for custom roms. Till dev (quarx) did it. Now defy has jelly bean (cm10). Lets search for devs and make a donation app, so they can buy our phone add develop one great rom.
Click to expand...
Click to collapse
incorrect, i made the Sense custom for Defy way before even CM9 was invented, but correct 2nd-init was working already then and no none really spend much investigating how to use it early on, but that was probably 1yr+ ago.
Dexter_nlb said:
incorrect, i made the Sense custom for Defy way before even CM9 was invented, but correct 2nd-init was working already then and no none really spend much investigating how to use it early on, but that was probably 1yr+ ago.
Click to expand...
Click to collapse
Quarx was the first one who figured it out, how to 2nd boot the cm7 rom on defy. maybe he could give some tips for devs in our comminity.
PS: i can remember your rom
hietsu said:
Great idea, but do we have enough people? No one will buy the phone if we can donate only ~100€]
what do you think, how large is our community approximately?
Click to expand...
Click to collapse
ukramch said:
hietsu said:
Great idea, but do we have enough people? No one will buy the phone if we can donate only ~100€]
what do you think, how large is our community approximately?
Click to expand...
Click to collapse
We're definitely not that big. I'd say theres no more than 15-20 that uses this phone and that would be interested in develpment advancement
Click to expand...
Click to collapse
ukramch said:
Quarx was the first one who figured it out, how to 2nd boot the cm7 rom on defy. maybe he could give some tips for devs in our comminity.
PS: i can remember your rom
Click to expand...
Click to collapse
i did mine in feb.2011 , Quarx did his first post of cm7 in april 2011, i do not know if that helps your memory. (i did check all his post on the topic) . I strongely believe i was utilizing 2ndinit on defy on a customrom, and i was introducing it here on o4x for now.
but to stay on topic, no one seems to have faith in a CM10 for O4X here, i tried to port, but that never went well, and compiling only helps so far as the ril driver is documented by LG here.
but the rest should be straight forward, since we share chipset with OneX which got quite far now.
btw,
i did post my CM10 rom as nandroid backup using 2nd init , so your request is already existing on o4x, just not with a phone functionality.
Dexter_nlb said:
i did mine in feb.2011 , Quarx did his first post of cm7 in april 2011, i do not know if that helps your memory. (i did check all his post on the topic) . I strongely believe i was utilizing 2ndinit on defy on a customrom, and i was introducing it here on o4x for now.
but to stay on topic, no one seems to have faith in a CM10 for O4X here, i tried to port, but that never went well, and compiling only helps so far as the ril driver is documented by LG here.
but the rest should be straight forward, since we share chipset with OneX which got quite far now.
btw,
i did post my CM10 rom as nandroid backup using 2nd init , so your request is already existing on o4x, just not with a phone functionality.
Click to expand...
Click to collapse
Sorry, i had my defy since may 2011. then you are right. at the beginning there were also phone functionality problems, we shouldn't loose faith
babymatteo said:
Yes it will...well at least for a custom kernel i think. Still, drivers have to come from Nvidia. And everyone knows about their reputation when it comes providing open source codes and such.
Click to expand...
Click to collapse
I have downloaded the file and it is .zip file .. It has two files that are kernel and platform files >> Good news
Now, I can see all the files for our O4X and everything is clear . We can make modification for it and install it by CWM
I hope you guys all the best with development . The kernel file has the drivers for our O4X
Best regards,
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
Please, look at the information of tegra 3 and open your eyes as much as you can at the official website
http://www.nvidia.co.uk/object/tegra-3-uk.html
Maybe you need it sooner or later ..
Best regards,
IMHO
As long as the kernel is not signed u cant really use it. i dont remember anyone using 2nd init on milestone for a custom kernel.
they actually just adapted CM for the old kernels wich is a lot of work i think... And that could be done for our 4xHD as well the problem is
actually that u need the devs for it.
And i think no dev really wants 2 work on a standart phone unless he has it and really wants to keep it and mod on it.
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
Hi, Today the Google edition kernel became availble one htcdev.com
http://www.htcdev.com/devcenter/downloads
can I use this on my regular HTC One? if yes how can I do it?
Thank you
Roms will be out soon enough after a dump is given ...but for the time being we have kernel source so devs can implement Google's fixes into their Roms to make pretty much bugless roms
a box of kittens said:
Roms will be out soon enough after a dump is given ...but for the time being we have kernel source so devs can implement Google's fixes into their Roms to make pretty much bugless roms
Click to expand...
Click to collapse
Thank you, I'll wait for the ROMs Then.
When we will have available an android 4.4 rom ? Is someone working on this ?
SilentGTX said:
When we will have available an android 4.4 rom ? Is someone working on this ?
Click to expand...
Click to collapse
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
penguin449 said:
Hey, well we can get some pre-alpha 4.4 AOSP builds maybe, but these will definitely have bugs, i do believe adam has built a 4.4. omni rom but i don't know much about bugs/boot status etc.
We are still waiting for cyanogenmod to merge sources, however they have stated that they are in no rush to start dishing out 4.4 roms as they have only just sunken their teeth into 4.3 Roms, we will get them eventually, however any builds within the next few days will have little customization or lots of bugs, patience is all we have till then
I hope this answered your question, also, this needs to be in the Q&A section next time bro
Good evening.
Click to expand...
Click to collapse
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
SilentGTX said:
Yeah thank you very much , it was very helpful , sorry for the wrong section . I can't wait for Android 4.4 ROMs :fingers-crossed: Good evening .
Click to expand...
Click to collapse
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
JoinTheRealms said:
Please understand that all the great things you've been hearing about android 4.4 wont apply to us for quite some time, what i mean by this is all the efficiency/ performance improvements will be somewhat mitigated buy bugs and firmware incompatibilities, these things take time for devs to work through, 4.3 still isnt mature enough on this device to call it stable.
I just don't want people to get overly excited by a 4.4 port, its improvements will come gradually.
Click to expand...
Click to collapse
I understand , of course , but still I can't wait :victory:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
JoinTheRealms said:
4.3 still isnt mature enough on this device to call it stable.
Click to expand...
Click to collapse
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
~MaX~ said:
im using pa 3.99 rc2 wich is 4.3 and it is perfectly stable, has great performance and no big bugs, i use it as a daily driver and it is the most perfect rom i used on my p880 till date
Click to expand...
Click to collapse
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
JoinTheRealms said:
Yes they are functionally stable to a user, but to call a rom stable (at least by Cyanogenmods standards) requires more than that.
Click to expand...
Click to collapse
please define stable then
~MaX~ said:
please define stable then
Click to expand...
Click to collapse
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Well.... Thank you
That's Well explained
I hope you are working on 4.4 rom
laufersteppenwolf said:
Gonna join this group, too
4.4 sure is on its way for our device, BUT:
Google is removing more and more support for our device, as it already is pretty old. So we need to re-add everything.
Even if it's booting, we still need a lot of work in order to get the most important stuff working (like SurfaceFinger, Audio, and ofc also data/RIL)
So regarding 4.4, all I can say is: Have patience
BTW, Thread moved to Q&A section
Click to expand...
Click to collapse
i'm really excited to see you releasing the 4.4 rom Aosp or custom, anyway your work is cool
You guys really doing great work here so l know that stable 4.4 will come eventually
Sent from my HTC Explorer A310e using Tapatalk 2
JoinTheRealms said:
Doesn't use dirty patch code to fix issues in source, usually done to get a release out quicker, between release candidates to stable this code is refined.
Click to expand...
Click to collapse
Sometimes it's still necessary to do. This is the case with our EGL libs for example. The best would be getting an update from LG, but this is very unlikely to happen. I got 4.3 BSP partially working, updated all graphics-related libs to 4.3 from grouper, but it broke a few things. Porting the full BSP might not be even possible.
Regarding Omni 4.4, I gradually found probably all needed patches for it, will see when I get to computer.
Sent from my OmniROM-powered LG Optimus 4X HD
Hi everyone,
Are there still any kernel developers present for our device?
It would be possible to have Xperia Sony SP 4.4.4 Kitkat, but we need to develop a kernel for that.
DeathZeroFx is also busy making it, but I was wondering if there are more people who are interested.
Deleunes254 said:
Hi everyone,
Are there still any kernel developers present for our device?
It would be possible to have Xperia Sony SP 4.4.4 Kitkat, but we need to develop a kernel for that.
DeathZeroFx is also busy making it, but I was wondering if there are more people who are interested.
Click to expand...
Click to collapse
We already have many people working behind the kernel building. Sad to say, its very difficult to port it as its closed source
Furrydaus said:
We already have many people working behind the kernel building. Sad to say, its very difficult to port it as its closed source
Click to expand...
Click to collapse
Hmmm...I hope you and other devs will succeed :s It would be awesome to have that kernel and thus a stock 4.4 rom
Deleunes254 said:
Hmmm...I hope you and other devs will succeed :s It would be awesome to have that kernel and thus a stock 4.4 rom
Click to expand...
Click to collapse
You can ask the kernel developers. If i recall there was one that was trying to do what you're doing. Its In-progress. You should look for GamerR or smtgh
Deleunes254 said:
Hi everyone,
Are there still any kernel developers present for our device?
It would be possible to have Xperia Sony SP 4.4.4 Kitkat, but we need to develop a kernel for that.
DeathZeroFx is also busy making it, but I was wondering if there are more people who are interested.
Click to expand...
Click to collapse
Since we do have cm11(4.4.4) I don't understand what changes are needed as the base kernel would remain the same(3.4.y). Atmost it would need ramdisk changes. Drivers and blobs are @4.3 and since proprietary can't really change.
Furrydaus said:
We already have many people working behind the kernel building. Sad to say, its very difficult to port it as its closed source
Click to expand...
Click to collapse
Kernel is open source what's this about porting the official 4.4 Xperia rom ?
Dark Passenger said:
Since we do have cm11(4.4.4) I don't understand what changes are needed as the base kernel would remain the same(3.4.y). Atmost it would need ramdisk changes. Drivers and blobs are @4.3 and since proprietary can't really change.
Kernel is open source what's this about porting the official 4.4 Xperia rom ?
Click to expand...
Click to collapse
Libs and stuff that im too lazy to care about XD
Furrydaus said:
You can ask the kernel developers. If i recall there was one that was trying to do what you're doing. Its In-progress. You should look for GamerR or smtgh
Click to expand...
Click to collapse
Thanks for answering. I knew about the one of Gamer R but he seems to have abandonded the project, cause there hasn't been a post update for months...
You think it would be possible mr Furrydaus?
Deleunes254 said:
Thanks for answering. I knew about the one of Gamer R but he seems to have abandonded the project, cause there hasn't been a post update for months...
You think it would be possible mr Furrydaus?
Click to expand...
Click to collapse
Its propably cos of all the lollipop hype and things. I think we will wait till Sony release their Lollipop Stock Firmware. Thatll be more exciting that the kitkat version
Furrydaus said:
Its propably cos of all the lollipop hype and things. I think we will wait till Sony release their Lollipop Stock Firmware. Thatll be more exciting that the kitkat version
Click to expand...
Click to collapse
Allright! Thanks for keeping me up to date!