[REQUEST] Cross-compatibility of badaDROID (volk204) & ZenDroKat (Tigrouzen) - Android Development on Bada

I think, badaDROID is on a state, where it is nearly ready for daily usage...
I know, there are users that prefer volk's ROM but they want to use it as NAND version.
I know, that Tigrouzen's ROM is not compilant with GPL...
For this, he uses his own page for development.
Why NAND of volk's ROM?
The ROM of volk204 is well developed! :good:
But the fact, that bada is still on device, this leads to performance issues.
These issues might be fixed with a NAND-version. Also all memory of device can be used...
So, this would bring lots of advantages.
But for users the problem is compiling your ROM as NAND version...
So maybe both developers can put their knowledge togethe to bring project forward...

In my opinion, NAND version has more downsides than benefits for now: battery charging is not controlled properly when the OS is shutdown. Moreover as said long time ago by Rebellos and Volk when it reach 100% with android it continues the charging process by progressively damaging itself.
(however they made an impressive work!)

Well...
There are still some points to be focused on...
But i think, batery issue seems to be fixed in nearer future... Progress is good...

Bada must be kept as long as there is no poweroff under android. Else, the phone will under low battery go in bootloop because it can't shutdown.
Nand is indeed faster than virtual partition, but not as much as people would think.
Maybe SD Rom could be a great, but it need a good sd to be faster than Nand (and virtual partition), and some work.

BenzoX said:
Bada must be kept as long as there is no poweroff under android. Else, the phone will under low battery go in bootloop because it can't shutdown.
Nand is indeed faster than virtual partition, but not as much as people would think.
Maybe SD Rom could be a great, but it need a good sd to be faster than Nand (and virtual partition), and some work.
Click to expand...
Click to collapse
You can find a lot of sd cards these days faster than the 4 year old nand of wave. I don't see why people want a nand Rom, it has low capacity it is often slower, in contrast sd cards are dirt cheap these days and they exist in an array of sizes and speeds to use for your best interest. Also "you" get to keep Bada as a backup os in case something awful happens to your android setup... Lastly it allows to have many separate roms, simply swap your sd and voila you've rebooted into a new Rom, other people would kill for this flexibility in their phones, we're blessed to have it, why spoil it?
Also -yes- a nand Rom would not be a bad idea but only for those who would not like to buy/use an sd card to their phones... But the main development better remain to sd...

Taxidriver05 said:
...So maybe both developers can put their knowledge togethe to bring project forward...
Click to expand...
Click to collapse
I reply here to avoid going off-topic in development thread, and because this thread topic, and the line quoted, applies to what I want to say
I think that last's Tigrouzen posts show that working together in badadroid is imposible, and that some Tigrozen's sentences deserve some comment
Tigrouzen said:
On last year we are 3 personne make badadroid advanced Rebellos, Volk204 and me (some on kernel)
Click to expand...
Click to collapse
Reading badadroid history, in the last three years there have been more developpers, including Mikegapinski who made the first really working ROM, and Oleg who made S8530 LCD driver
Mikegapinski intially didn't share sources and properly recognize other developers, i think it is interesting to read this Rebellos post about that situation, how he was asked to do it, and how he finally did it.
In my opinion the creation of new code (like RIL/modem/GPS) hacking undocumented phone internals done by Rebellos and Volk in these last two years is something few people, developers/programmers like them can do, and the modification of code/scripts/optimization is something more people can do, knowing that both kind of task are time demanding, and that I can't do none of them (I am not a developer, despite I appear in some credits)
Tigrouzen said:
GPL it is scam im not working for free.
Click to expand...
Click to collapse
Incredible to hear that from someone who is modifing GPL sources; not only XDA rules, but linux kernel inside android also is GPL
I think several sentences are enough:
This one from Rebellos about badadroid "...3% is mine, 95% is Samsung/Google and thousands people who did linux."
This one from me: "3 personne make badadroid advanced Rebellos, Volk204 and me? Rebellos and Volk are making badadroid, which has GPL sources, advance, but Tigrouzen is not making badadroid but just zendrokat, which has closed source based on GPL sources, advance". For example Tigrouzen is announcing today a new version with "Gps from Volk & Rebellos"; (indeed, the subject of this thread shows how badadroid and zendrokat are seen as different projects ...)
Yes, Rebellos and Volk are working and sharing sources for free, because they are just expecting the GPL licence of their code is respected.

hunktb
i'm join forum xda from 2012 ,I know what happens between Volk and Tigrouzen , we should respect them rather than divisive

Well...
Why I opened this thread?
I see the situation as a developer AND as a user...
As a developer I would say: Yes! We have to respect other peoples work... No question...
As a user I would ask myself: Are there any improvements indevelopment?
For me it is not relevant, who brings the improvements...
Wave devices are beyond their normal life cycle...
BadaDROID development only keeps them alive...
But THIS only can work, when the devs we have work together...
If I would have the technical abilities, I'd compile a ROM by myself... But I am NOT...
So I rely on devs like volk204, Rebellos or Tigrouzen...
I do not want to say, Tigrouzen's ROM is better or volk's ROM is better...
Of course I work together with Tigrouzen...
But I do this, because his ROM is closest to daily usability...
It's a fact that the dual boot of volk's ROM eats performance...
It's not due to his work. it's due to bada...
I know, battery isue is important and NOT fixed...
But i think, both together they can fix it.
Just think about...

All should unite to develop better
Specially These two Person >>Tigrouzen & Volk204
Hope
To respect all users
Turbidity put aside

@Taxidriver ,
i don't think so.
I have used all 3versions .
nand/sd/virtual partition.
what i want to say is SD versions are best .
i use sandisk class10 16gb ,
and performance is really better than nand.
rom is so good, nd performance is even better than current all higher mid range phones for sure.
not even a single lag nd crazy multitasking , ahh.
yesterday , i was comparing my wave2 with friend's S3 .
and multitasking comes better on wave2 haha.
i can minimize some games like gangstar vegas,asphalt8 etc .
but on S3 games was crashing at minimize manytimes.
:XD .
(and yes, i have disabled gapps, to boost up performance)

Senior wave user
- As a user I honestly use Tigrouzen ROM...
- For Developer I'll choose Rebellos, Volk204 for following all the GPL rules
- As a friend I like Tigrouzen even thou he sell his ROM but honestly he also share his work for free for all & easy to talk with..
Tigrouzen ROM is very optimized this is the features can't match the other roms..
But still I love all badadroid developers :good:

While installing tigrouzen nand rom i got error while restoring system in s8530

karan1719 said:
While installing tigrouzen nand rom i got error while restoring system in s8530
Click to expand...
Click to collapse
which error?
if you got md5 mismach error then go to last option in cwm recovery and uncheck md5 checksum and restore again

black0000 said:
which error?
if you got md5 mismach error then go to last option in cwm recovery and uncheck md5 checksum and restore again
Click to expand...
Click to collapse
I have bypass md5 chexking it shows error that "error in restoring system"

karan1719 said:
I have bypass md5 chexking it shows error that "error in restoring system"
Click to expand...
Click to collapse
have you extraxted and copied clockworkmod folder in correct position i.e. memory card and it does not contain any other folder named clockworkmod inside it.

karan1719 said:
I have bypass md5 chexking it shows error that "error in restoring system"
Click to expand...
Click to collapse
On recovery, select clean to install new rom, than reboot recovery , than try,
if still not , if nand , do format bada partition , if sd , repartion sd.
if still not. than re-dload rom, it may be currupted zip.
this should help

after flashing tigrouzen nand fota and bootloader phone doesnt boot it shows file not found

karan1719 said:
after flashing tigrouzen nand fota and bootloader phone doesnt boot it shows file not found
Click to expand...
Click to collapse
You have to put the zImage file on your SDcard

Please stay on topic!

As you all (should) know, Tigrouzen's ZenDroKat isn't GPL compliant. The GPLv2 requires you to share the source code if you've modified anything in the kernel, but Tigrouzen chooses not to comply with it. As such, ZenDroKat is considered as warez as far as XDA is concerned, and discussion of it is not allowed.
You can review the forum rules here and read more about the GPL here and here. Thread closed.

Related

MODEM rumours, progress... few details for noobs like me

Hmmm...
Yes I know, again stupid Question.
Why we can not use SHW-M130K "Modem" or part from it?
S8500 not start ?
S8500 explode ?
Any Logfiles exists?
Later I will write more... need to check again SHW-M130K files and JTAG Dump...
Its long long time ago...
Best Regards
It's so old... I have forgotten where my files stored.
http://forum.xda-developers.com/showthread.php?t=1133736
Here seems Firmware still active for SHW-M130K...
http://pspmaster.tistory.com/48
I have forgotten which files inside...
In bada Firmware amss.bin is mandatory file for Call.
This files is huge, more then 12 MB...
If you write own Code, then you know why I wrote huge... for 12 MB...
Samsung Android handset need file modem.bin...
Don't punish me, if wrong name...
In actual bada Android Port... modem.bin is complete DISABLED/or ignored by zImage ...
SHW_M130K_0x00000000_OK.rar this is JTAG dump I have for study...
No idea, if I remember correct, modem.bin from SHW-M130K is near 7 or 10 MB...
Damn, if I find my files I know it correct...
Best Regards
Short checked I9000 Firmware...
But here is baseband from Infineon... instead Qualcomm...
modem.bin is bigger then 12 MB...
I have taken this one for "research"...
GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip
Now I will download SHW-M130K WC21 from here:
http://pspmaster.tistory.com/48
Soon more ...
Best Regards
adfree said:
Short checked I9000 Firmware...
But here is baseband from Infineon... instead Qualcomm...
modem.bin is bigger then 12 MB...
I have taken this one for "research"...
GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip
Now I will download SHW-M130K WC21 from here:
http://pspmaster.tistory.com/48
Soon more ...
Best Regards
Click to expand...
Click to collapse
I really wish i learn to develop softwares nt unfortunately nt nw... So jst tell me in plain words gud news r bad news...i think u shud check for oldr samsung android phones....
M130K-HOME-GB-REV04-WC21
Short checked...
modem.bin bigger then 15 MB...
This time it is Qualcomm related... and also QSC6270...
Next...
For AMSS, this is your Modem... you need NVM knowledge...
NV items is also NO Kindergarten...
Minimum knowledge is Qualcomm related Tools like QPST and if more advanced. Then QXDM...
http://forum.xda-developers.com/showthread.php?t=899023
So you need advanced users with deep Qualcomm knowledge about AMSS, NVM... for instance like our pro Unlockers... GSM...
No Link to forum...
But this Forum is nice... Maybe you find here ""enough"" stuff for study.
http://www.finetopix.com/
Here are smart users with deeper knowledge...
Best Regards
Summary...
For successfully Modem integration you need expertS with:
- deep Qualcomm knowledge about AMSS, RF, NV...
this include working with Tools like QXDM...
- coding skills alone are nice... but not enough to manage all problems...
As modem.bin is 10 MB of perfect matching data... this is like rocket science.
This means many years of experiences in this GSM/CDMA business...
So in my opinion we have at the moment nobody... who can finish this in 2012...
1 man can't finish this...
Best Regards
QXDM overview from Qualcomm
Feel free to clicking around.
https://support.cdmatech.com/qxdm/1_START_HERE.htm
Here Call related...
https://support.cdmatech.com/qxdm/CallManager/CallManagerindex.htm
Here some NV...
https://support.cdmatech.com/qxdm/NVbrowser/NVindex.htm
Now maybe you can understand, how complex AMSS/Modem is...
Best Regards
https://jobs.qualcomm.com/public/jobDetails.xhtml?requisitionId=1888000&page=jobSearch
Such users we need also.
Embedded Software Engineer - GSM/EDGE Modem Physical Layer
Click to expand...
Click to collapse
http://www.qualcomm.com/careers
Clicking around and you will see. How long some jobs require...
3 years of experience...
Maybe after 3 years we will have someone, who is able to finish succesfull Modem functionality...
Maybe someone is able to make visible progress in 2013.
After hard, hard, hard learning process...
Best Regards
after seeing all this i have lost hopes for modem. drivers to be written from scratch.
only hope is that some modification of other android modem.bin gets fit to our modem.
or else we can hope for an optimised 3.3 inch android tab.
god bless wave.
Yes,its seems that modem writing is not an easy job...
especially for 1 person...
anyways,Adfree...u did a fantastic job by finding all this stuff...
only hope is with some trick or shortcut by which we can modify some other android modem...(my weird thought)
but for now,well done
Regards,
WaveGuru
http://www.youtube.com/watch?v=IWSCdpAeONA
Found this here:
http://code.google.com/p/docl4amss/wiki/ReferencePage
Btw...
Someone has this Doc found ?
80-VE263-25-MSM7200A-BasebandTopics.pdf
And normally for each Qualcomm Chip...
Full AMSS Source Code exists...
Several hundret MB...
Maybe someone has found something... MSM6xxx or older ?
Pudn is very good site to find interessting stuff...
Best Regards
http://bb.osmocom.org/trac/
OsmocomBB is an Free Software / Open Source GSM Baseband software implementation.
It intends to completely replace the need for a proprietary GSM baseband software, such as
drivers for the GSM analog and digital baseband (integrated and external) peripherals
the GSM phone-side protocol stack, from layer 1 up to layer 3
In short: By using OsmocomBB on a compatible phone, you are able to make and receive phone calls, send and receive SMS, etc. based on Free Software only.
Over the past 12 months, we've been making very good progress. Most of the hardware drivers have been written, and a relatively complete layer1, layer2 and layer3 exist.
No work has yet been done on any sort of UI on the phone. The only user interface is a telnet-based command line.
Click to expand...
Click to collapse
Our chipset is not listet... but maybe interesting for research...
Best Regards
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
Actually Oleg used some modem.bin and it seems like it worked but
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something. My battery seems to be pretty well "worn out" and my fuel gauge totally decalibrated, it keeps showing fake values all the time and at all my battery keeps power for ~20hours, I will put a warning in kernel thread.
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
Click to expand...
Click to collapse
There are few Fake IMEI... kind of "Emergency IMEI" somewhere in AMSS...
In theory we can have all the same IMEI for Calling...
I remember from my AMSS journey from 2006... QC Standard IMEI bla...bla
Will look into my old stuff...
Also I think we have enough space... to create more NV items...
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
I know few sources... but never seen complete AMSS package...
Also my brain is tooooo small to use these sources for something usefull.
I need this only for my QC collection. :angel:
Best Regards
http://blog.csdn.net/yili_xie/article/details/5656608#comments
Here seems few QC related infos... maybe more...
Request to other users.
Please.
1.
I need AMSS source for Download.
No idea, 300 or 400 MB ZIP or more...
Maybe this is something in this kind... Google Power. :angel:
https://www.codeaurora.org/git/proj...ions/db2575e163152f681668800744c99f287f77a8ef
Best Regards
How about Samsung Galaxy 3 I5800 ?
004400152020000
This is IMEI from SXG75, EF81, SL91 ... handset from 2006 with MSM6250...
If NV item 550 was lost/empty/blocked...
There are hundrets of such devices...
Also this IMEI can be found on other manufacturer, if QC AMSS...
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
Click to expand...
Click to collapse
For Android you could define new NV ID for IMEI... instead NV 550...
Best Regards
Rebellos said:
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
Actually Oleg used some modem.bin and it seems like it worked but
a) It would require rebuilding EFS aswell (like cloning it from QSC6270 phone and replacing IMEI?)
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something. My battery seems to be pretty well "worn out" and my fuel gauge totally decalibrated, it keeps showing fake values all the time and at all my battery keeps power for ~20hours, I will put a warning in kernel thread.
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
and what about tablet like this
http://www.androidtoitaly.com/goods.php?id=368
or this
http://it.aliexpress.com/product-fm/591540997-2012-new-android-tablet-sim-card-slot-wholesalers.html
they also have QSC6270...
also many renesas tablet have QSC6270, here some firmware/skd
http://www.chinadigitalcomm.com/opa...enesas-android-tablet-pc-firmware-t10398.html
Rebellos said:
Using modem from any other QSC6270 based phone is some kind of solution. modem.bin does in fact contain AMSS, stored in same or almost same format.
...
b) If there's no Android phone based on QSC6270 with battery fuel gauge controlled by modem - we won't have battery control, and this seems to damage something.
...
Comparing to implementation of new RIL - it's rather easy way to get some more functionallity out of Badadroid.
I've got pretty complete sources for MSM7200 AMSS and believe me - it's not something you want to dig in. It's just HUGE.
Click to expand...
Click to collapse
Rebellos, the modem control the battery? or them is related someway? kinda creepy
How to edit AMSS.bin or Modem.bin??

Want to start with AOSP JB 4.2 - experienced developers are welcome :)

Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium

[CM10.2]Compiling and testing on i9505 (the good and the bad)

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

[UPDATED Nov. 22] Badadroid Guides, general info & FAQ

Up to date as of November 22, 2013.
Modified: Installation guide: V2.0, some other parts including general info, changelog etc.
Added: Swapping guide, quick V2.1 guide, quick updating guide
---------------------------------
Are you experienced with ULTRA B.U.X? Please help me write its own guide (PM me)
---------------------------------
I created a centralized document with information about everything regarding Badadroid. The same questions are often asked over and over again by newbies/noobs (call it however you want to). I decided to write a centralized document that will include general information, a more detailed installation guide for those who struggle or have issues and a FAQ for everything regarding Badadroid.
In order to allow users to add their own feedback and comments I created it in Google Docs - but if a moderator/developer/authorized user here wants me to put everything on this thread just say...
I really hope this will help everyone. More info in the doc itself.
See http://bit.ly/19jWmE1
-------------------------------------------
Did this guide help you? Please hit the "Thanks" button
________________________
Member of Bada Israel
Are you Israeli? Wait for the Hebrew translation
Thx for the work!
Btw, wave doesn't have 512mb ram, (384mb)
Retrete said:
Thx for the work!
Btw, wave doesn't have 512mb ram, (384mb)
Click to expand...
Click to collapse
That's right. I think I confused it with my GPU thanks for the heads up.
Can anyone type the code to activate Zram on NAND tigrouzen rom (V3)? Please
Kiboi said:
Can anyone type the code to activate Zram on NAND tigrouzen rom (V3)? Please
Click to expand...
Click to collapse
Its all ready activated
Nadavs10 said:
I created a centralized document with information about everything regarding Badadroid. The same questions are often asked over and over again by newbies/noobs (call it however you want to). I decided to write a centralized document that will include general information, a more detailed installation guide for those who struggle or have issues and a FAQ for everything regarding Badadroid.
In order to allow users to add their own feedback and comments I created it in Google Docs - but if a moderator/developer/authorized user here wants me to put everything on this thread just say...
I really hope this will help everyone. More info in the doc itself.
See http://bit.ly/19jWmE1
Click to expand...
Click to collapse
Thanks Nadavs10, I think a FAQ is a good idea ... the point is how to ensure every newbie reads it before posting ...
I think it would be nice to join or at least to link this with another FAQ it was started in badadroid project page http://code.google.com/p/badadroid/wiki/FrequentlyAskedQuestions
Some comments:
Does it work for Wave II? YES! Many people ask over and over again the same question. Voice calling works now for Wave II too. If there’s something that isn’t the same for both devices, I will write it.
Click to expand...
Click to collapse
Bluetooth works in S8500 but no in S8530 (see status and this post)
Is it legal? Everything is legal except gapps. Decide for yourself.
Click to expand...
Click to collapse
Both badadroid and gapps are "legal", the difference is licensing model, so developers share badadroid open source code and binaries based in other open source code (android, aries ....) but they do not share gapps as it is google propietary. It is not ilegal to install gapps, but it should be ilegal to include it in badadroid package without google permision, so you have to install it separately.
There are many ROMs like Nand/LS Smook/moviNand. What are these, and what’s the difference? I’ll tell you the truth, I don’t really understand it. If someone knows it would be great for some comment here."
Click to expand...
Click to collapse
I am not an expert, but I am trying to share as I understand:
There are different "custom rom android flavors" (Cyanogenmod, AOKP, MIUI,...) as some communities/developers make some modifications in android source code. Just one example googling http://www.phonearena.com/news/Meet-the-best-custom-ROMs-for-Android_id44353
There are different badadroid roms as some developers try to optimize some points:
--Volk204's CM10.1 rom (and previously Rebellos' CM10) uses the same fota for booting, and it uses "standard" internal storage in our waves, so the uninstallation procedure is simple (another zip through CWM).
--Tigrouzen FnF SD (sorry if the name or some detail is wrong) uses special fota for booting, and it uses Nand memory/external SD storage with SD card partioned. http://code.google.com/p/badadroid/wiki/HardwareDocumentation#Memory Nand is a special memory in our waves that has to be written in a special way, and it is faster, so the unistallation procedure is a full flash of bada firmware. Tigrouzen's rom is more performance oriented and better for game players as far as I know.
hunktb said:
I am not an expert, but I am trying to share as I understand:
There are different "custom rom android flavors" (Cyanogenmod, AOKP, MIUI,...) as some communities/developers make some modifications in android source code. Just one example googling http://www.phonearena.com/news/Meet-the-best-custom-ROMs-for-Android_id44353
There are different badadroid roms as some developers try to optimize some points:
--Volk204's CM10.1 rom (and previously Rebellos' CM10) uses the same fota for booting, and it uses "standard" internal storage in our waves, so the uninstallation procedure is simple (another zip through CWM).
--Tigrouzen FnF SD (sorry if the name or some detail is wrong) uses special fota for booting, and it uses Nand memory/external SD storage with SD card partioned. http://code.google.com/p/badadroid/wiki/HardwareDocumentation#Memory Nand is a special memory in our waves that has to be written in a special way, and it is faster, so the unistallation procedure is a full flash of bada firmware. Tigrouzen's rom is more performance oriented and better for game players as far as I know.
Click to expand...
Click to collapse
Tigrouzen's rom is based on AOSP (Android Open Source Project) wich is basically, a build of the vanilla android sources released by google and the others implicated in the Android primary developement. (even if, tigrouzen included in his rom some code from CM to allow a better customization of the ROM, and so, it's a little bit different from pure AOSP)
Cyanogenmod is a modified open source android rom... it have some major changes in the code itself (compared to AOSP), in the library it uses, etc... it allow a higher personalisation of the UI than the original AOSP rom. (see their official website to find more info about the cyanogenmod project...)
And I would finally said that yes, tigrouzen's rom is released with an high optimisation care (resulting in a really smooth rom) while volk's rom: works on both wave I and II, I would say that it is a little bit more stable (but that's mainly because it's less often udated, several tigrouzen's updates resulted in an broken functionality (see the bluetooth problems in the AOSP thread) wich he quickly fixed anyway.) and I would say (except for the last "mic in call" update) more "hardware development" oriented (that's just my feeling, but it seems to me that volk (and rebellos) are focusing on the perspective of bringing a fully working android sytem to the wave rather than on the optimization of their existing incomplete system. (and honnestly, it's not a bad thing, it keep general development ongoing)).
Weird
Tigrouzen said:
Its all ready activated
Click to expand...
Click to collapse
Hey Tigrouzen i am facing a problem while using yur AOSP 4.3 Rom... I am using the ROM 4.3 LS V2 Revision 3 with SmooK V3 SD Kernel downloaded from http://www.multiupload.nl/HQ3BM7DOTH. The issue is weird as on the first booting of andriod, the netwrok is detected after arnd 20-25 mins but the next tiem the phone is booted in android it never detects network? :/
Any help on this plz wud be rly appreciated... Thanks
ghanii said:
Hey Tigrouzen i am facing a problem while using yur AOSP 4.3 Rom... I am using the ROM 4.3 LS V2 Revision 3 with SmooK V3 SD Kernel downloaded from http://www.multiupload.nl/HQ3BM7DOTH. The issue is weird as on the first booting of andriod, the netwrok is detected after arnd 20-25 mins but the next tiem the phone is booted in android it never detects network? :/
Any help on this plz wud be rly appreciated... Thanks
Click to expand...
Click to collapse
I solved this problem by removing then reinstall the sim, try
Kiboi said:
I solved this problem by removing then reinstall the sim, try
Click to expand...
Click to collapse
Thanks i am trying it right now....the ROM and Kernel which I mentioned are the right versions?
Kiboi said:
I solved this problem by removing then reinstall the sim, try
Click to expand...
Click to collapse
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
ghanii said:
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
Click to expand...
Click to collapse
Try with another sim and tell me if it works
ghanii said:
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
Click to expand...
Click to collapse
move it to the top right corner. It sometimes helps.
Otherwise use an other sim card.
GreekBlood said:
move it to the top right corner. It sometimes helps.
Otherwise use an other sim card.
Click to expand...
Click to collapse
I should move the sim to the top right corner? :/
ghanii said:
I should move the sim to the top right corner? :/
Click to expand...
Click to collapse
Its possible if its old sim, then try get new revision of your sim.
ghanii said:
I should move the sim to the top right corner? :/
Click to expand...
Click to collapse
Go to setting and below bluetooth there is an option of more click on it and then tick use only 2g network
this may help
Maybe "we" collect different external Links in different languages...
Today I saw again German user asked...
Or maybe "we" could use 1 Guide and translate in different languages...
For instance:
English
German
Hindi----> user kktkaran has enough time and energy to do this, instead spxm
.
.
.
Btw.
For few things Screenshots or Video maybe helpfull.
And please, maybe here on XDA 1 copy for reading... So if external Link changed/removed/... it is possible to read here something in Thread.
Thanx in advance.
Best Regards
Tigrouzen said:
Its possible if its old sim, then try get new revision of your sim.
Click to expand...
Click to collapse
i tried a different kernel and it worked fine ver 3.0.85... voice is also clearer. thanks for your help
i am from those people who have problem in wave2 battery like
after restart battery drains to zero or similar level
random shut down problem
so
i have done an experiment which help me thats why i'm sharing it
first of all these problems are because of battery as i think so
1.first remove the battery
2.spin on flat surface if it spin then you can do nothing but replace your battery
3.if doesn't spin check its point of connection and remove any dust or rust
3.last but not least if any thing doesnt work
then
take a "soledring ion" and solder each connecting point of your battery seperately dont let them touch each other so that solder cover connecting points.
now put your battery in phone and test it work or not i.e. your problem solved or not
sorry for bad english
and do it on your own risk and carefully
Asop or badadroid
I'm currently using the ASOP NAND ROM created by Tiguorzen, however it has some call problems similar to old badroid ROM so I'm wondering whether I should shift to badroid project as it seems to get regular updates and ASOP ROM seems like abandoned by tigo(hope not) but ASOP is undobtly the fastes and most streamlined ROM not sure abouy the latest badadroid though.

[HELP NEEDED] [OPEN PROJECT] AndROMega project, environment builder for custom ROM em

INTRODUCTION
Have you ever dreamed to get not any device but YOURS on the wide screen of your computer? Create a custom ROM and emulate it, or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system has become also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks like we do now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environments. An eventual port for Mac OS isn't envisaged for now but still welcome if someone wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Reserved.
Atronid said:
INTRODUCTION
Have you ever dreamed to get not any device but YOUR on the wide screen of your computer? Create custom ROM and emulate it or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system became also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks as we do for now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environment. An eventual port for Mac OS isn't envisaged for now but still welcome if somebody wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Click to expand...
Click to collapse
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
NonStickAtom785 said:
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
Click to expand...
Click to collapse
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
I'm In!
Atronid said:
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
Click to expand...
Click to collapse
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
NonStickAtom785 said:
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
Click to expand...
Click to collapse
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Atronid said:
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Click to expand...
Click to collapse
Thanks:laugh:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
ender1324 said:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
Click to expand...
Click to collapse
That's very nice, thanks!
As mentionned earlier, the project won't start right now due to my work, but in theory I should be available and ready to start it in the next months! I'll DM you as soon as it gets its first kick !

Categories

Resources