Database Develop

Thread Closed Please Delete Mods....

Closed Thread Due To New Thread.... Please Delete Mods

Awesome!
Will try!

Downloading.
Thanks
Edit: oops

Btw, can we expect better battery than the other gb roms?

Tell Me What You Think? Hit The Thanks Button

does it got that rainbow bug???????

Some What You Just Have To Try, Your Experiance Will Be Diffrent Than Mine...
It Should Be Its The Newest Modem...

neobuddy89 said:
does it got that rainbow bug???????
Click to expand...
Click to collapse
Yeah 2 Sec...

hayn_pryde46 said:
Yeah 2 Sec...
Click to expand...
Click to collapse
I dont want to sound discouraging, but why does CM7 and MIUI Gingerbread ROM dont have any rainbow? cant we use CM7 Kernel(Kang's version)
coz Kernel is reason to rainbow I think.
Thank you VERY MUCH for your Efforts..
keep it up!!

neobuddy89 said:
I dont want to sound discouraging, but why does CM7 and MIUI Gingerbread ROM dont have any rainbow? cant we use CM7 Kernel(Kang's version)
coz Kernel is reason to rainbow I think.
Thank you VERY MUCH for your Efforts..
keep it up!!
Click to expand...
Click to collapse
Its Based On Edts Rainbow Roms, No Bootloader... Thats Why Its Not The Kernel

So what's the deal with this Toggle Headset thing?
neobuddy89 said:
I dont want to sound discouraging, but why does CM7 and MIUI Gingerbread ROM dont have any rainbow? cant we use CM7 Kernel(Kang's version)
coz Kernel is reason to rainbow I think.
Thank you VERY MUCH for your Efforts..
keep it up!!
Click to expand...
Click to collapse
1.It's because we don't have Gingerbread bootloaders.
2. CM7 kernels don't work

I'm confused why people are reposting the EDT ROM with basically nothing changed. Users can uninstall and install app themselves. Same goes for Kernels and Modems. None of the original bugs are solved really so I'm confused why this is the second such ROM out today.
I understand it's a great learning experience but from a user standpoint it does not contribute much. I would love when the dev uses the things he/she learned from this to make something.
PS: hayn_pryde46, this is not directed at you nor is this negative. I am very glad you decided to get into the dev game and hope you will become good at it. I'm just unsure your learning experience should be posted as a complete ROM.

why did you port this if it has like NO difference between mine? i mean seriously dude not cool.

Thank you for the previous two posts. I recently got a thread closed because I stated that the dev section is getting polluted with too many roms, which are all the same with minor changes. Im glad im not the only one
Sent from my SGH-T959 using XDA App

ALL he did was download my rom, and re-upload it with some more apps and a different modem/kernel. NOTHING MORE.

Yeah sorry most 98% files are new from xwjvb I just used the rom as base deleted all the files but their init.d tweaks added new build.prop and modem and kernel got mtp sync to work and maybe debugging and original music player remember reboot problems with whitehawks rom, in which he changed it to miui apk
Sent from my GT-I9000 using XDA App

Delete
Sent from my GT-I9000 using XDA App

}{Alienz}{ said:
I'm confused why people are reposting the EDT ROM with basically nothing changed. Users can uninstall and install app themselves. Same goes for Kernels and Modems. None of the original bugs are solved really so I'm confused why this is the second such ROM out today.
I understand it's a great learning experience but from a user standpoint it does not contribute much. I would love when the dev uses the things he/she learned from this to make something.
PS: hayn_pryde46, this is not directed at you nor is this negative. I am very glad you decided to get into the dev game and hope you will become good at it. I'm just unsure your learning experience should be posted as a complete ROM.
Click to expand...
Click to collapse
Literally just came to post the exact thing. It seems to be a trend lately, to the point that it's getting ridiculous. The bugs that exist are pretty big, so how about we either work on those, or sit back and wait for other, more advanced devs to fix them before we start "porting" and call it our work.
I assume you don't have the ability to fix the existing bugs, so that alone should stop you when you go to open a thread for a new ROM that you know you don't have the ability to improve yourself.
I mean, then what? Someone is going to work really hard and eventually fix something, you're going to copy/paste it and call it an update? Just relax on these "ports" for now, they're not needed at this stage of 2.3.3 for the Vibrant.

so you DIDN'T tweak it as it says in your post. You give me NO credit even though you downloaded my rom (which has at least some BIG differences to whitehawks) and just replaced the files that determine the build number added a different kernel/modem and pass it off as your COMPLETE own work. Mine at least fixes some bugs his old rom had (battery drainage, made 3D gaming less sucky). Like cmon dude.

Delete
Sent from my GT-I9000 using XDA App

which rom is better ?

which rom is better for the 9001 sgs+ in terms of the following parameters
1. stability
2. performance
3. battery life
4. functionallity
5. appearance
can someone (or more) provide some feedback on the above mattter as i am trying to flash a rom for my phone , and all i can see is different versions where all seem ok . but is there anyway tha we can have some feedback from actual users.
which one to flash and why ?
I apologize to any possible disregard to forum rules.

manollis said:
but is there anyway tha we can have some feedback from actual users.
Click to expand...
Click to collapse
Users comment about the roms in the according threads.
The only thing you can do is read-read-read
manollis said:
I apologize to any possible disregard to forum rules.
Click to expand...
Click to collapse
Indeed, this is a development subforum.

broodROM
Cranium
Cryberts ROM
ANDROIDS REVOLUTION
I9001XXKPG 2.3.5 Gingerbread Deodex by Astap for MultiDownloader
CyMod ROM
UCM GingerBread Rom
these are the roms available.
afaik you can configure each one of them with not much effort so that it has the functions of another of the roms by changing kernel or adding or deleting tweaks. if there was a rom which would be "better" there wouldn't be any other roms.
i think they're pretty much the same.

only to broodROM alone the total posts are 2338 so far
where to start and what to read ??
anyway thank you for your replies anyhow.

manollis said:
only to broodROM alone the total posts are 2338 so far
where to start and what to read ??
anyway thank you for your replies anyhow.
Click to expand...
Click to collapse
Start at the beginning and read all.

i dont want to sound rude or "cleverish"
but should this development reach somewhere or it should be develpment for the sake of developing ??? i am a bit confused ??
it shouldnt reach to a rom that it should be stable (or any other criteria that one looks for ??)
i am just wondering ?
have people in programming lost the connection to the real purpose of the items in question , which is to communicate. ?
i dont know guys i am just wondering ??

the big picture is:
everyone develops what he wants to but simultaneously everyone looks at what other developers do and adopt their features or mods for themselves to have a good rom in the end. thats why i think the roms are all kind of the same. you can use a cranium kernel for brood rom and (in some cases) use the broodrom configurator for cranium rom or use thunderbolt for any of our roms. i don't think this is bad.

dr.wtf said:
the big picture is:
everyone develops what he wants to but simultaneously everyone looks at what other developers do and adopt their features or mods for themselves to have a good rom in the end. thats why i think the roms are all kind of the same. you can use a cranium kernel for brood rom and (in some cases) use the broodrom configurator for cranium rom or use thunderbolt for any of our roms. i don't think this is bad.
Click to expand...
Click to collapse
Yeh that's true, since we only have Samsung ROMS as base ROMS we don't have much choice , also for the configurator, it was actually built for XXKPS but it seems KPG (not sure), KPS, KPU and QK1 use the "same" framework, ZSKP6/7 is other tho

I suggest you try broodROM RC 3 with FeaCore kernel and thunder bolt.It's smoother than CraniumROM (tried) and my battery goes up to two and a half days on broodROM.Haven't tried it on Cranium.Didn't like it from the beginning.

[Q&A] Q&A Thread for Evervolv Jellybean builds

To keep the development thread clean, this thread is meant to post any questions with regards to Evervolv's Jellybean builds for your Nexus One, such as "Has issue X been solved in build Y?", or "I have a problem X. Is anybody else experience the same?". The kind users on XDA will try to answer all your questions, or point you to the relevant location to solve/address your issue.
For general discussions about the Rom, please use this thread: http://forum.xda-developers.com/showthread.php?t=1795954
Please don't forget to include as much details as possible to any questions (build number + release date, steps to reproduce the issue etc.).
Before you post a question, you should
1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
if you can find an answer for your question.
Before you post any questions with regards to a problem you're facing, you should
1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
3.) Search the Evervolv Code review site: http://review.evervolv.com/#/q/branch:jellybean,n,z
to check if there's already a solution that is not mentioned in OP, or if the issue was filed and/or a fix is pipelined by the developers already.
Thanks for helping to keep everything clean!

I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...

mtmjr90 said:
I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...
Click to expand...
Click to collapse
First off, thanks for posting to the correct thread! Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents.
Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.

Bexton said:
First off, thanks for posting to the correct thread! Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents.
Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.
Click to expand...
Click to collapse
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.

mtmjr90 said:
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.
Click to expand...
Click to collapse
Probably the best answer to get, is by looking at the release history of the Evervolv TexasIce Cream Sandwich thread (post 2 & 3): http://forum.xda-developers.com/showthread.php?p=19785288#post19785288
But don't expect weekly updates. Updates come, as Texasice think that it's worth to bump to a new build.
I didn't followed any AOKP projects.. But I know that some devs publish new builds for "every" commit they push to their repos to keep users up to date with the latest stuff. However, Evervolv is a small team of 3 devs and Texasice, who works on N1 stuff, additionally works on other devices and other stuff as well. From what I can see, he's pushing new releases when "something big" was fixed, or was improved, but not for every tiny change.
However, they build nightlies, too. So if you want, you could update every morning. But a better idea would be to follow the progress via their code review site and if you see any commit which you think you would like to have that, go ahead and grab the next nightly.
All Jellybean commits: http://review.evervolv.com/#/q/branch:jellybean,n,z
Jellybean commits that have been merged: http://review.evervolv.com/#/q/status:merged+branch:jellybean,n,z
Finally, you can find the source at GitHub and build yourself as often as you want. https://github.com/Evervolv

Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).

mtmjr90 said:
Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).
Click to expand...
Click to collapse
There are no peculiarities to JB that I know of. All I had to do was enter a2sd install in Terminal (after getting SU there first). I assume you already had an sd-ext partition on your SD.

Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?
Thanks!

mothor said:
Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?
Thanks!
Click to expand...
Click to collapse
It is version 3.0.0
p stands for pre-alpha (see it as pre-release) and the build number The JB build is just beginning TexasIce will come up hopefully soon with an alpha build once all the merging is completed

I'm coming from ICS as my daily driver, but hesitant on JB just yet.
Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.
Thanks,
-sj

I'm having serious stability issues and I just want to confirm what causing them...namely is it the ROM or perhaps a hardware issue. I've had the ROM set up and running three times now and each time (once over night, twice just having it sit around for an hour or so) it just freezes up and when I battery pull to reboot, almost all of my apps and settings have been erased. I've used the built in a2sd to move apps and dalvik to sd-ext, dunno if that could be part of the problem... Anyone else have similar issues? I'm thinking if it's not the ROM, it could be corrupt storage or something.

Is butter working in these builds?

This is more in response to your rant on the development thread than in relation to the ROM directly, but I was thinking it would possibly reduce the amount of posts about stuff not appropriate for the development thread if you could put a warning to come up when someone is writing a post for the thread asking if what they're writing is going to contribute to the development of the ROM and with links to this and the discussion thread suggesting them as more appropriate places to post. Dunno if that's possible, or if someone like you with lots of posts could suggest it as a solution to this problem that plagues so many threads?
Sent from my Nexus One using xda app-developers app

Another question which is more directly related to the ROM.
Is it possible for an option to be added to remap the soft keys? Such as remapping the search key to be a multitasking key as is in actual ICS phones?
I know I personally hardly ever use the search key but often use the multitasking features which would make it awesome to have that functionality!
Just a thought, thanks if you implement it!
Sent from my Nexus One using xda app-developers app

Just wondering when TI will release next build. Am having trouble with notifications. I have pushed all the libs but still the video playing is broken. I really don't know what bexton has fixed but p1 with all fixes was just awesome. I know TI will incorporate all those stuffs so just waitimg eagerly for a p3.
Sent from my Nexus One using Tapatalk

I don't know if it's a bug or not... sometimes screen display doesn't turn off but phone is asleep (I think). See the lockscreen but doesnt respond to touchscreen. Works fine once I wake up phone with power button. On latest nightly(7/27).
Sent from my Nexus One

seinjunkie said:
I'm coming from ICS as my daily driver, but hesitant on JB just yet.
Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.
Thanks,
-sj
Click to expand...
Click to collapse
i am using the xdata flag everything seems to work in regards to that

With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?

ironjon said:
With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?
Click to expand...
Click to collapse
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One

vimitake said:
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One
Click to expand...
Click to collapse
I did it with setcpu
Enviado desde mi HTC Desire usando Tapatalk 2

[Q] How to port I9300 roms to I9305?

Hello , I'm very disappointed of the interest of the developpers for the LTE variant of the S3 so i wanted to port i9300 roms from myself , according to hardware , the only changes are the modem and the ram right ? So how could i port these roms ? From no specific knowings , i'd like to at least learn how to do it without big risks of brick so help please .
Thank you and sorry for english mistakes if i've done some.

aaz03 said:
Hello , I'm very disappointed of the interest of the developpers for the LTE variant of the S3 so i wanted to port i9300 roms from myself , according to hardware , the only changes are the modem and the ram right ? So how could i port these roms ? From no specific knowings , i'd like to at least learn how to do it without big risks of brick so help please .
Thank you and sorry for english mistakes if i've done some.
Click to expand...
Click to collapse
this is not a easy question for random guys like me with almost zero knowledge about developing, although on the other hand a developer could simply explain how its done by f.e. making a thread about porting roms specifically to our i9305 in noobs language (if possible) but i doubt that this will happen, as it is very much time consuming and a lot of thinking and typing work. personally i think a thread like this would bring some life into our i9305s threads, dont you think so..?
to get you already started with some learning and discovering for yourself, read further..
the best method for porting roms is IMO building from source, but this is not as easy as it sounds..
first you will need to set up a build environment. I assume youre using Windows OS, now if you got a 64 bit system this is exactly what you need.. fortunately for you and others there is a custom branch of the Ubuntu OS thanks to @sylentprofet to use with Oracles VB/VM (Virtual Box/Machine) already preconfigured for building or porting roms (both require building/developing experience though) all you need to do is download the source and commit, fork, cherry-pick etc. if you decide to step into the android development world, you will learn more step by step however having some basic knowledge like terminal commands and git commands would be useful.
Also you need to get familiar with github and how it is used, check out here
I recommend lots of research though before actually taking any actions!! all these things will make you feel :silly: at times, but do not give up! for there were is a will, theres a way
good luck :good:
Download builduntu v1.4 here
Download Oracles VB here
Guide-how to build rom from source (most recent one i guess)

MaHo_66 said:
this is not a easy question for random guys like me with almost zero knowledge about developing, although on the other hand a developer could simply explain how its done by f.e. making a thread about porting roms specifically to our i9305 in noobs language (if possible) but i doubt that this will happen, as it is very much time consuming and a lot of thinking and typing work. personally i think a thread like this would bring some life into our i9305s threads, dont you think so..?
to get you already started with some learning and discovering for yourself, read further..
the best method for porting roms is IMO building from source, but this is not as easy as it sounds..
first you will need to set up a build environment. I assume youre using Windows OS, now if you got a 64 bit system this is exactly what you need.. fortunately for you and others there is a custom branch of the Ubuntu OS thanks to @sylentprofet to use with Oracles VB/VM (Virtual Box/Machine) already preconfigured for building or porting roms (both require building/developing experience though) all you need to do is download the source and commit, fork, cherry-pick etc. if you decide to step into the android development world, you will learn more step by step however having some basic knowledge like terminal commands and git commands would be useful.
Also you need to get familiar with github and how it is used, check out here
I recommend lots of research though before actually taking any actions!! all these things will make you feel :silly: at times, but do not give up! for there were is a will, theres a way
good luck :good:
Download builduntu v1.4 here
Download Oracles VB here
Guide-how to build rom from source (most recent one i guess)
Click to expand...
Click to collapse
Thanks mate, i'm gonna try this and gîve you some news, other advices for maybe add some optimizations like linaro and kernel adding for example? I'd like to just port Roms but maybe it would be interesting to build my own rom later
Edit: sorry didn't read the guide, find my answers, thank you

aaz03 said:
Thanks mate, i'm gonna try this and gîve you some news, other advices for maybe add some optimizations like linaro and kernel adding for example? I'd like to just port Roms but maybe it would be interesting to build my own rom later
Click to expand...
Click to collapse
your welcome bro :good:
i really have no idea about how linaro is used in combination with kernel, you really have to google that one or get in contact with a dev. willing to help you out i think the kernel is automatically installed with your build when youre initializing/syncing repos and with commands in terminal its executed to build it. you can of course compile own kernel with modifications but as i said it needs lots of research, wish i could help you..
try for now some basics with the guide for gaining more experience and who knows what you will be capable of in next 2/3 months or less

aaz03 said:
Thanks mate, i'm gonna try this and gîve you some news, other advices for maybe add some optimizations like linaro and kernel adding for example? I'd like to just port Roms but maybe it would be interesting to build my own rom later
Edit: sorry didn't read the guide, find my answers, thank you
Click to expand...
Click to collapse
Here you got some useful video tutorial regarding kernel development with Linaro

MaHo_66 said:
Here you got some useful video tutorial regarding kernel development with Linaro
Click to expand...
Click to collapse
Ty , it 'd try , any other advice for kernel dev ?

aaz03 said:
Ty , it 'd try , any other advice for kernel dev ?
Click to expand...
Click to collapse
not that i know of, the tutorial should be explaining everything

[Q] Queries regarding custom kernels

Hello everyone
This is the first time Im creating a thread in all my years here on XDA. So please bear with me
Im very happy and excited to see the recent boom of custom roms for our device, its going really well and at a break neck speed.
Much rapid then I can download and flash it too
However, the only thing bugging me the lack of custom kernels.
I understand that the pINKman kernel by slukk and unnamed kernel by luca are both fantabulous kernels , and are mighty contenders for your time.
Dont get me wrong, I fully and whole-heartedly appreciate the kernel-devs and the awesome work made by them
The furnace kernel by savoca seemed to be a good one too, but I noticed that the thread has been closed and my recent pm to him about some possible update has not yielded any results.
I dont possibly know where im going with this conversation (lol), but if you catch my drift, we'd certainly want to see the boom of custom kernels just as we did with custom roms
Sorry for such a lengthy post .
*bows out*
:cyclops:
EDIT- lol, sorry for creating a thread in the general section, I botched it
Should have created in the QA section

metalrules321 said:
However, the only thing bugging me the lack of custom kernels.
Click to expand...
Click to collapse
Well, as long as Motorola doesn't release the kernel sources for lollipop, there isn't much that can be done. I found today some commits for lollipop but nothing official (look at Motorola's github kernel under issues). It took Motorola quite a while to release the sources for kitkat, so we have to keep patient.

need some OC and OV feature

@doppelhelix
Whelp
Thanks for clearing that up for me man.
Yeah it kinda sucks , I mean with the recent influx of so many roms and only 2 kernels was an eye-sore xD
Anys ways
*fingers crossed*

@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??

metalrules321 said:
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
Click to expand...
Click to collapse
based on kitkat. Thats why they don't work on stock lollipop, only cm