Related
haven't seen any thread about this. someone already tried setcpu on the arc how about the play?
i want to overclock my unit cause most of the psx games (ie castlevania) tends to be slow and the framerate drops significantly even if it's fixed at 30 fps.
so no one seems to be interested in overclocking the xplay?
i guess when its been out longer ill wont an overclock but i haven't had any slow down as yet well after getting rid of the rubbish that was on there "bloat"
i would rather a recovery menu first ha ha if were wishing here..
but we need a custom kernel first i believe before an overclock
You'll need someone to cook up a custom kernel to OC the play or someone to make a script that runs it without a custom kernel. Had this on my HTC desire hd before I rooted/unlocked the bootloader and flashed a custom kernel that could OC.
The first option will need a unlocked bootloader and the latter will just need root (if possible with the play).
Setcpu should be able to underclock as it is now, but that wont help with your gaming issues.
Regards Dousan...
No need for unlcoked bootloader just need root and someone to cook up a kernel module to work with set CPU. It's a standard qualcom 8250 shouldn't be to hard. Contact the developer of setcpu on twitter or by email
Sent from my SGH-I897 using XDA Premium App
brendanmurphy said:
No need for unlcoked bootloader just need root and someone to cook up a kernel module to work with set CPU. It's a standard qualcom 8250 shouldn't be to hard. Contact the developer of setcpu on twitter or by email
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Sweet! I don't mind the skinned version that SE provided. I just wanna overclock it for my Zelda game on N64oid
will wait for any updates on this. Havent rooted my phone yet cause im after overclocking it for now.
tux880 said:
i guess when its been out longer ill wont an overclock but i haven't had any slow down as yet well after getting rid of the rubbish that was on there "bloat"
i would rather a recovery menu first ha ha if were wishing here..
but we need a custom kernel first i believe before an overclock
Click to expand...
Click to collapse
What were the apps that you removed? I might just do this while waiting for an oc. And were there any signifcant changes in terms of the unit's speed.
hey owain
you already have xperia play !! you can do it
where are you man ?
did you forget xda site ?
why ?
We need the sources of the xplay to create own kernels - at least to create one without minor bugs
Ireas said:
We need the sources of the xplay to create own kernels - at least to create one without minor bugs
Click to expand...
Click to collapse
The source is out for the play, forget where now but the link is on this forum, i think its the thread about starting to root it.
waz000000 said:
The source is out for the play, forget where now but the link is on this forum, i think its the thread about starting to root it.
Click to expand...
Click to collapse
Really? Excellent will take a look at that
Sent from my HTC Desire using XDA App
Hey guys, i'm new to the play forum although ive been around for a while lol anyway just to clarify some points.
yes with the sony kernel source code we can make custom kernels, but without an unlocked bootloader we cannot flash unsigned images.. i only got my play 2day so i am unsure of what can or cannot be done, does the play have nand protection? if not and we can create and flash a custom recovery image, then an unlocked bootloader should not be nessesary. android has full R/W access by default to all the partitions while in recovery mode, so we should be able to flash things roms/kernels/ect. maybe someone should email clockworkmod and ask if they are or intend to work on a custom recovery
waz000000 said:
The source is out for the play, forget where now but the link is on this forum, i think its the thread about starting to root it.
Click to expand...
Click to collapse
I can't find it, anyone know if the source is available?
coutts99 said:
I can't find it, anyone know if the source is available?
Click to expand...
Click to collapse
ive googled it and can find nothing on sony releasing kernel source for the play
Only in the arc source seems released: http://developer.sonyericsson.com/wportal/devworld/search-downloads/android?cc=gb&lc=en
svenk919 said:
Only in the arc source seems released: http://developer.sonyericsson.com/wportal/devworld/search-downloads/android?cc=gb&lc=en
Click to expand...
Click to collapse
I'll have a poke about in that for now, will be similar-ish
could it be that the kernel is the same as the one for the play?
svenk919 said:
could it be that the kernel is the same as the one for the play?
Click to expand...
Click to collapse
pretty sure of that. They mention it's for their 2011 xperia gingerbread phones.
http://developer.sonyericsson.com/wportal/devworld/downloads/download/30a2181182tarbz2?cc=gb&lc=en
Sent from my Nexus S using XDA Premium App
it's the same firmware package for neo/arc/play
check arm/arch/config
semc_zeus_defconfig is the play one.
So there you have it the source code.
booting into linux now ill have a look and try to compile it
Hi all,
say that I'd like to try a CM7 custom compilation (e.g., removes half of packages, ...) for the sake of learning, what steps do you suggest to get into?
Compiling a full debuggable ROM and test it in the Android emulator?
Could I test It along with SE kernel (e.g., with the latest)?
In the emulator should i to install the SE related packages in order to set up the Xperia HW emulation?
Cheers!
There's a package of scripts named kitchen, made of a member here that let you customize a rom. There is even a root method that we were talking about the other day.
https://github.com/dsixda/Android-Kitchen
Hi kissmyarch,
i meant bulid It from the sources, not through the kitchen way ;-)
Oook sorry then.
LoL take a rom add ur theme, choose ur fav apps! Choose ur modules! And ur done! Custom rom is ready!
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
LoL nevermind then! This is what happening lately on mini pro forums, I just revealed how its being done!
Ravencz said:
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
Click to expand...
Click to collapse
I agree with Ravencz, building from sources is more funny than cooking... the fact is that you find a tutorial on cooking in the forum (and it's simplistic as hell) and no an hint on how to port your own CyanogenMod on your mini pro... what a pity...
Hoping someone on the devs' side will read this post ;-D... Cheers!
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
galvic said:
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
Click to expand...
Click to collapse
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
@galvic: CM doesn't seem a cooked ROM to me, since they provide the repository from which you could clone the sources. CM seems more a fork (with enrichments/improvements) of AOSP and cooking a CM isn't the same of building its source.
So the thread is correct, because if i fetch and edit the Gingerbread branch of CM source, actually i've built a custom CM7.
Instead of linking those megabytes of ROMs, shouldn't be better working on CM's branch and attach the related patches that brought to a custom CM ROMs, as patches for kernel modules and so on? Benefits of patches are small downloads size, learning what people do in making your beloved ROM, ... On the other side you've to set up a developer's environment, that is a bit expensive (Gingerbread sources are around 7 Gigabytes, if i'm not wrong).
I don't know if Gingerbread is the best choice with the unchangeable kernel that SE stuck on our smartphone, but say Gingerbread or Froyo or whatever the fix you've to make on a CM are (logically) the same until someone will make an hackish strike and take down that damned bootloader.
See you!
Ravencz said:
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
Click to expand...
Click to collapse
Sorry but CM is also bult on sources of AOSP
galvic said:
Sorry but CM is also bult on sources of AOSP
Click to expand...
Click to collapse
Of course it is, but it's modified
Ravencz said:
Of course it is, but it's modified
Click to expand...
Click to collapse
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
thats what free-xperia project did, use miniCM resources!
galvic said:
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
Click to expand...
Click to collapse
Nope, compiling gives you control over things such as source code, compiling options/flags for optimization (say that our mini pros have ARMv6 processor, why having a ROM built for generic ARM architecture? It doesn't make any sense... that's the source-oriented GNU/Linux distro way as Gentoo: compiling kernel and all application for your machine in order to have best performances and responses), possibility of adding removing code (e.g. libraries, system applications) and so on.
Cooking let's you modify something pre-made and doesn't give you *full* control on it ;-)
If we've to take over the world, we've to do it in the proper way! :-D
Cheers
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Added splboot.ko compiled with X10 mini pro kernel sources (same config as zImage) , address 0x00200000
Also included a nice sh for insmodding, and dmesg modules.
SPLBOOT MODDED SOURCES ON MY APPORTS INDEX!
Original sources can be found on FreeXperia git, and ARMv6 by nAa at X8 bootloader bypass thread
Thanks to nobodyAtall for porting splboot to ARMv6. Thanks to aZuZu and doixanh for helping and side tips.
D4rKn3sSyS said:
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.g z sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Thanks to aZuZu and doixanh for helping me compiling.
Click to expand...
Click to collapse
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
Just read the wikipedia article on zImage. Here.
wikipedia said:
The filename of the bootable image is not important, but by convention it is called vmlinuz or zImage.
Click to expand...
Click to collapse
can you make bzImage? 2.3 Mb is to big for download... Thanks! Nice work!
Any progress on bootloader bypass?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
This is a dev thread, why it's supposed that this is related with custom roms?. zImage it's kernel executable (compressed btw).
Uploaded splboot.ko module, seems working well, if you are gonna try, be sure that you chmod to 777.
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Snoopo said:
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Click to expand...
Click to collapse
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
D4rKn3sSyS said:
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
Click to expand...
Click to collapse
i think he mean you can use chmod 777 while For development & testing
but set correct permissions before releasing
mean dont keep 777 but correct it if 777 not needed
(+x or what ever i dont know more permissions type lol )
heh yeah... Maybe it's my linux administration thinking:
Permission 777 is bad ^^
You should better find out which user or group shall have execute ,rewad or write-rights and then set the correct permission...
for example:
chown 0:2000 /foo
chmod 750 /foo
you see? Okay on a mobile it's really not that important but think of that there is someone who writes a bad app that exploits just a permission of CM7 or CM6 that is used in every phone... and woops ^^ or whatever ^^
D4rKn3sSyS said:
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig.
Click to expand...
Click to collapse
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
What's splboot module for? Does anybody try to kexec-tool way?
Cheers,
ff0000.it
... I almost forget: this is the best thread on the forum, thanks D4! ;-D
ff0000.it said:
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
Click to expand...
Click to collapse
Yes... i think.
ff0000.it said:
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
Click to expand...
Click to collapse
no... more source required.
ff0000.it said:
What's splboot module for? Does anybody try to kexec-tool way?
Click to expand...
Click to collapse
bootloader bypass.
Or at least, i think i'm right.
OmegaRED^ said:
Yes... i think.
no... more source required.
bootloader bypass.
Or at least, i think i'm right.
Click to expand...
Click to collapse
Right, s.e site, right, and right
OmegaRED^ said:
no... more source required.
Click to expand...
Click to collapse
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
OmegaRED^ said:
bootloader bypass.
Click to expand...
Click to collapse
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
ff0000.it said:
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flash-able via Xrecovery
It's hard to isolate what to patch... consider that the big x10 threads have been messing with modified kernels for quite some time now..
Ip-tables, (CPU undervolt, overvolt and overclock) and many other mods directly implemented into the kernels.
And even so they are still stuck on the same kernel version.
SE has not even upgraded the kernel version with the 2.3.3 update.
So it may be possible but it makes alot of work for new drivers...ect..
It's best to try and optimize the current version and already working source instead of creating a whole new ball game.
OmegaRED^ said:
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flashable via Xrecovery
Click to expand...
Click to collapse
I think you don't get my point... i was saying (from my point of view) that a kernel upgrading is mandatory (or it should be)...
It's the same if i have a Linux 2.4.x kernel with a GNU distribution that relies on mechanism such as sysfs that isn't supported in 2.4.x kernels (>= 2.6.x); so to build a custom Gingerbread ROM it's a good choice having a related kernel (from wikipedia it's 2.6.35).
And what's within Xrecovery and CWM? Flashing differs from building...
Saying that i don't want bluetooth or GPS or wifi support in my ROM, disable it from kernel and ROM building... that's the benefit of having custom kernels and ROMS.
Still i don't understand why you answer me with Xrecovery and CWM
Please don't miss under stand.
All i am saying is that without source it becomes hard.
SE did not upgrade the kernel to 35 for the big x10 or the x8 so there is very little to work with.
It would be awesome to get the kernel to that level.
But it's easier to rather tweak the kernel we currently have.
ff0000.it said:
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
^^^
This is why i commented on CWM and Xrecovery.
Afair there are even custom kernels but they are not really stable and discontinued.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
What are you talking about?, we haven't already bypassed bootloader.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
The point is not the stability or the instability of a custom kernel, it's to have the chance of building a custom one...
It's my right to have a unstable custom kernel builded by me installed on my phone, isn't it? :-D
@D4: i'm going to learn more about "git" and then i'll try (in the spare time) to patch SE kernel up to 2.6.35 (with all git tags/branches) and the i'll upload it to github... no promise at all, by i'll try ;-D
D4rKn3sSyS said:
What are you talking about?, we haven't already bypassed bootloader.
Click to expand...
Click to collapse
Yeah my bad. Have read the custom kernel stuff while i was completely new to smartphones. The X10 has custom kernels, but theire development is afair discontinued.
Sorry for the irritation.
Hello people
I flashed the new rom Feralab v18 and DoomKernel v.06 on my phone x10i but I have seen that sometimes it block or it goes in spurts.....I don't sure that it's the kernel, but because I wanted to prove even more, I'm here to ask you :
What are the new and best kernel after DoomKernel with over / underclocked or not?? thx
no answer?
I found this link:
http://forum.xda-developers.com/showthread.php?t=1345913
some of you have already tried these kernel?
for example:
2. Free Kernel 4.05.4 SE233
- Direct port of Free Kernel 4.05.4
- Include dual recoveries
ftf File: http://www.mediafire.com/?3tolzmam2tid2qu
Wifi Module: http://www.mediafire.com/?6f8zwogejf3i4gg
has anyone ever tried this kernel?
Almost all of kernel for X10i are very similar, because are based on stock SE sources. I am using Doomlord kernels, because they are stable and have good scailng and undervolting capability.
It also depends if u want locked or unlocked bootloader version
HeliumX10 said:
Almost all of kernel for X10i are very similar, because are based on stock SE sources. I am using Doomlord kernels, because they are stable and have good scailng and undervolting capability.
It also depends if u want locked or unlocked bootloader version
Click to expand...
Click to collapse
i have unlocked bootloader now i search the best kernel for flowing, performance and without big bug
Raschild6 said:
i have unlocked bootloader now i search the best kernel for flowing, performance and without big bug
Click to expand...
Click to collapse
As I told - I recommend Doomlord kernels. There are not any kernel with "big" bugs (i know only about Usb host bugs). Look into section "Android Development" and choose the right one you thing is for you
HeliumX10 said:
As I told - I recommend Doomlord kernels. There are not any kernel with "big" bugs (i know only about Usb host bugs). Look into section "Android Development" and choose the right one you thing is for you
Click to expand...
Click to collapse
i had found this post :
http://forum.xda-developers.com/showthread.php?t=1345913
but in this days i don't have time to try all kernel.
you know something about (2.3.7 Roms) :
2. Th Kernel Rev08-5 Cob06c
- Based on Th Kernel Rev08-5
- Include dual recoveries (xRec and doomlord modified CWM5)
- change in ramdisk to support fxp netd
ftf File: http://www.mediafire.com/?1981mxs5ifvx82s
Wifi Module: http://www.multiupload.com/0RODM897XW
or :
5. Free Kernel 4.05.4 Cob06d
- Based on Free Kernel 4.05.4
- Include dual recoveries (xRec and doomlord modified CWM5 with Touch Screen)
- change in ramdisk to support fxp netd
ftf File: http://www.mediafire.com/?zvv311m1oo4ay78
Wifi Module: http://www.mediafire.com/?6f8zwogejf3i4gg
Try a FreeKernel version, they are under freexperia team and their development were one of the bestest
HeliumX10 said:
Try a FreeKernel version, they are under freexperia team and their development were one of the bestest
Click to expand...
Click to collapse
ok i try in this days and then I'll tell you how it went
if you have other news write here
but.....i have 2.3.3 version stock but with Feralab Rom v18 i passed 2.3.9.
the Free Kernel 4.05.4 Cob06d is compatible with the Rom?
Raschild6 said:
ok i try in this days and then I'll tell you how it went
if you have other news write here
Click to expand...
Click to collapse
Goodluck!
Personally its just a guess for you - I am still on locked bootloader and tested all of locked kernels and free kernels were the best all the time.
HeliumX10 said:
Goodluck!
Personally its just a guess for you - I am still on locked bootloader and tested all of locked kernels and free kernels were the best all the time.
Click to expand...
Click to collapse
thx so.....why you still on locked bootloader?
Raschild6 said:
thx so.....why you still on locked bootloader?
Click to expand...
Click to collapse
Anytime bro
I am on locked bootloader still because I dont have any reasons to unlock it and because:
- there is no rom/kernel which requires unlcked bl which has something really necessary for me (eg. new major version of OS or some extra functionalities)
- once bootloader is unlocked you can brick your phone totally (and I dont have JIG and UART adapter for X10i).
- i have completely modded WB rom by myself - extremely clean with huge of free RAM and great CPU performance. Didnt found something like mine yet
Only one reason why I will (in future) unlock my bootloader is CyanogenMod 9 which is in development but currently it hasnt deep sleep and camera working. Only one reason is Android 4.0 no else
HeliumX10 said:
Anytime bro
I am on locked bootloader still because I dont have any reasons to unlock it and because:
- there is no rom/kernel which requires unlcked bl which has something really necessary for me (eg. new major version of OS or some extra functionalities)
- once bootloader is unlocked you can brick your phone totally (and I dont have JIG and UART adapter for X10i).
- i have completely modded WB rom by myself - extremely clean with huge of free RAM and great CPU performance. Didnt found something like mine yet
Only one reason why I will (in future) unlock my bootloader is CyanogenMod 9 which is in development but currently it hasnt deep sleep and camera working. Only one reason is Android 4.0 no else
Click to expand...
Click to collapse
yes!!! it's true!!....but i have unlocked bootloader even when I was a noob xD
last question : you have learned himself to build and program kernel-rom?
I'd like to start doing something, in java for example
Raschild6 said:
yes!!! it's true!!....but i have unlocked bootloader even when I was a noob xD
last question : you have learned himself to build and program kernel-rom?
I'd like to start doing something, in java for example
Click to expand...
Click to collapse
Haha I am really NOT a noob, but still dont have it
No no its too difficult - yes I am able to build a android kernel from sources a make a really few mods in it, but I cant say, that I am a developer... Even I am programmer in desktop C++ and desktop Java, I cant write any app for android, its much more difficult than a programm app for PC in C++ and desktop Java is completely different from Android Java for a pity I have tried some tutorial for veleoping on android and I was disgusted how it works badly...
I recommend you to start programming in C++ or Java in desktop environment first and later move on Android Java
And ROMs no, still modding released ones and for personal usage at a time. I wasnt ever thought about to release my mods here on XDA yet
HeliumX10 said:
Haha I am really NOT a noob, but still dont have it
No no its too difficult - yes I am able to build a android kernel from sources a make a really few mods in it, but I cant say, that I am a developer... Even I am programmer in desktop C++ and desktop Java, I cant write any app for android, its much more difficult than a programm app for PC in C++ and desktop Java is completely different from Android Java for a pity I have tried some tutorial for veleoping on android and I was disgusted how it works badly...
I recommend you to start programming in C++ or Java in desktop environment first and later move on Android Java
And ROMs no, still modding released ones and for personal usage at a time. I wasnt ever thought about to release my mods here on XDA yet
Click to expand...
Click to collapse
i just study 2 year of C# (class,OOP,windows form) and 1 year of C++ and java at school but i'm still far from create app
have you got some guide of programming in C++ or Java for create app or complete guide of developing on android ??? i can try with eclipse and some guide but there are only court and incomplete
Raschild6 said:
i just study 2 year of C# (class,OOP,windows form) and 1 year of C++ and java at school but i'm still far from create app
have you got some guide of programming in C++ or Java for create app or complete guide of developing on android ??? i can try with eclipse and some guide but there are only court and incomplete
Click to expand...
Click to collapse
Bad school then I have studied half a year of C++ and year of Java and it tought me to build some apps myself now. Must note that all with no UI, just command line but its more usable and resources free.
No sorry mate, I bought two thin books for C++ and Java, but sold them back very early. I prefer myself playing with code
As I told, not evan for android app - few months ago I searched how-to make a Hello World! for android. It was for Eclipse as I remember... And was disgusted how long was the whole code for it - about 40 lines of something between XML and Java.
So I dont have any...
I'm aware that there are custom kernels for 5.0 by rumirand and entropy,
but rumirand's kernel is not really 100% compatible with YP-GB70 (KOR) and this is the device that i currently have.
Unfortunately, even in Korea GP forum, there is absolutely no custom kernel for 5.0 (Tegrak Kernel exists for 4.0)
So i wanted to develop it on my own so i've been searching for instructions.
I've instaled ubuntu, installed bunch of stuffs.
but i have no idea how to start. all those guides were incoherent.
can somebody tell me some basic infos and things that i should know for developing YP-GB70 kernel?
I would advice starting with reading about linux kernel structure, how it works etc.
I would like to develop new kernel for 5.0 too
Send from samsung galaxy s wifi 5.0 running paranoidandroid.
search, search, search!
That's what I had to do. I now have a modified, compiled and running kernel with no prior experience. Follow that guide, look at the android site for setting up an environment, etc.
Then you need your source files + initramfs. I don't think samsung has released their initramfs source so you're going to need to find it elsewhere. Samsung stuff is also different than the nexus things that the android site refers to so you need to take bits and pieces of information from places and piece it together yourself. I recommend looking at other kernel builder's githubs too, I've modified others sources and have wound up with good results.
exodus454 said:
search, search, search!
That's what I had to do. I now have a modified, compiled and running kernel with no prior experience. Follow that guide, look at the android site for setting up an environment, etc.
Then you need your source files + initramfs. I don't think samsung has released their initramfs source so you're going to need to find it elsewhere. Samsung stuff is also different than the nexus things that the android site refers to so you need to take bits and pieces of information from places and piece it together yourself. I recommend looking at other kernel builder's githubs too, I've modified others sources and have wound up with good results.
Click to expand...
Click to collapse
yeah that's what i was doing. i managed to extract initramfs from the zimage but dont know what to do anymore :silly:
Do you have any idea if the initramfs is the same between your version and the rest of the world? You might be able to use an already extracted version.
Sent from my YP-G70 using xda premium
exodus454 said:
Do you have any idea if the initramfs is the same between your version and the rest of the world? You might be able to use an already extracted version.
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
yes? i searched github but there weren't any for GB70 (there was g70)
So i just did it by myself, which took me around an hour. Everything was new to me so uploading GB70 initramfs to github took me like 30 mins.:silly:
my next step is to add cwm recovery to the kernel and it;s quite hard. most of the guides written in this forum are usually written for specific devices.
Before you start modifying the kernel, and i suggest you try compiling it to make sure your sources are good.
Sent from my SGP5 with XDA Premium
exodus454 said:
Before you start modifying the kernel, and i suggest you try compiling it to make sure your sources are good.
Sent from my SGP5 with XDA Premium
Click to expand...
Click to collapse
It can't be wrong. I got the zImage from Korean stock rom tar. But you are right. I gotta try decompiling and compiling to make sure
stylemate said:
It can't be wrong. I got the zImage from Korean stock rom tar. But you are right. I gotta try decompiling and compiling to make sure
Click to expand...
Click to collapse
Just a note..you can't decompile a kernel binary. The farthest you can go is extracting the initramfs from it. To get a kernel you would have to build it from source.
Sent from my HTC One S using Tapatalk 2
klin1344 said:
Just a note..you can't decompile a kernel binary. The farthest you can go is extracting the initramfs from it. To get a kernel you would have to build it from source.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
oops seems like i made a noobish term mistake there
i wanted to write unpack but thought that decompile can be used also. Thanks!