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??
Related
Hello,
I have an Ampe A10 Quad core tablet (Freescale I.mx6q chip) which has quite a small dev community so far so I am looking at building my own rom for the device.
i can get by in Linux and learn fast so feel I can do it. I have been reading constantly for the last week before even starting to get a grip of whats what. I am trying to make an ASOP version of 4.0.4 to replace the stock 4.0.4, rather poor rom.
My question is what do I do about vendor overlays as there is nothing out there for this device or anything similar. I have done a lot of searching on this and found the suggestion "You could just use an extract from a working Rom or phone" " You use the extracted proprietory files to complete the source" . I understand I need the proprietary binaries to make the build but i don't really understand what that the suggestion means.
Any help you could offer on obtaining the files I need from the stock ROM and how to setup the vendor overlay would be most appriciated.
Cheers,
I don't have your device man, but if there is another similar device out there with a similar board and chip configuration search github for a repo that contains an "extract-files.sh" file for that other device. Fork it, clone into your dev environment under your Device folder, connect your tablet via USB (make sure adb is running), and run that script. It should pull the proprietary files required straight from the device and you may be better off.
Hope this helps a little! Good luck with your project.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
djmatt604 said:
I don't have your device man, but if there is another similar device out there with a similar board and chip configuration search github for a repo that contains an "extract-files.sh" file for that other device. Fork it, clone into your dev environment under your Device folder, connect your tablet via USB (make sure adb is running), and run that script. It should pull the proprietary files required straight from the device and you may be better off.
Hope this helps a little! Good luck with your project.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the advice. I have spend some time searching but cannot find anything on github. There are only a couple of devices that are similar. The Ampe A10 Sanei N10 and Hiapad F10 are all the same thing just rebranded, the other is the Zenithink C94 but I cant find anything on any of them.
How can I create a new device tree for my device? (which from what I understand is what I want) It would be a good thing to achieve as it would help others in the future. I have been through the "Configuring a New Product" on the AOSP site so now understand a bit more what's going on.
Sp3ktral said:
Thanks for the advice. I have spend some time searching but cannot find anything on github. There are only a couple of devices that are similar. The Ampe A10 Sanei N10 and Hiapad F10 are all the same thing just rebranded, the other is the Zenithink C94 but I cant find anything on any of them.
How can I create a new device tree for my device? (which from what I understand is what I want) It would be a good thing to achieve as it would help others in the future. I have been through the "Configuring a New Product" on the AOSP site so now understand a bit more what's going on.
Click to expand...
Click to collapse
extract-files.sh is a cyanogenmod creation, so you'd be lucky to find anything....... Linaro offer support for the sabre lite development platform which is a i.MX 6q based board, maybe building Linaro's version of the AOSP would be a good start
Here's a couple of links to get you started
https://wiki.linaro.org/Boards/MX6QSabreLite - Overview of the Board, you can check how close it is to your device
https://wiki.linaro.org/Platform/Android/BuildSource
You are correct you need to create a device tree , a couple of good resources I've used in the past when creating device tree from scratch are
Embedded Android ( http://shop.oreilly.com/product/0636920021094.do ) this book is pretty close to the bible on the Android Build System and worth the Investment. Alternatively ( more importantly free! ) a slide deck by the same author ( http://events.linuxfoundation.org/slides/2011/abs/abs2011_yaghmour_porting.pdf )
Android Device Porting - http://www.youtube.com/watch?v=mvxYt3AkbrE
Could the extract script not be used to help pull the right files straight from the device for his vendor folder though? He would just need to edit the list of files to be pulled in the referenced list the script uses in the loop if he knows what configuration files are needed, no?
I'm by no means an expert but on first glance that's all the extract-files script does...or is there something I'm missing? I'm learning too so would be good to know either way lol
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
djmatt604 said:
Could the extract script not be used to help pull the right files straight from the device for his vendor folder though? He would just need to edit the list of files to be pulled in the referenced list the script uses in the loop if he knows what configuration files are needed, no?
I'm by no means an expert but on first glance that's all the extract-files script does...or is there something I'm missing? I'm learning too so would be good to know either way lol
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Apologieses if that came across as abrupt, Just sayin' you'd be lucky to find one that come close to his board etc, iMX Freescale chips are not that mainstream But yeah if you can find an extract script than have at it! Saying that why do you even need a script? just pull the files yourself through adb, pointless wasting time searching. The question then becomes, what files? And that is unique the each device and each version and how much of it is open source etc,etc.
I think the OP is probably a way off doing that, when I've played around starting a device tree from scratch, I've find it is easier to start off with the base requirements, i.e processor architecture, maybe start with building a mini package first or even BUILD_TINY_ANDROID on a generic arm board. The whole starting from scratch thing is not a small task, which I suppose was your point in the first place lol
For sure. It really does boil down to what files, whether a script is used to pull them or not lol.
Thanks for the links by the way, SUPER informative
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
thanks for all the great info Trevd. The Sabre lite board is very similar indeed! There seem to be only a few minor differences which are inconsequential anyway. For example the tablet have less USB and no Ethernet. I think it could be a good starting point.
I guessed when I started this project it wouldn't be a quick fix but that't not a problem, At the end of it I will have my own working ROM and that's the point.
I can see the Freescale chips being taken more in to the main stream in the future. The tablet is VERY fast and reliable it has just been let down by poor, half-arsed software. For example all the aspects of Android relating to telephony have still been left in.
Thanks again,
Sp3ktral said:
thanks for all the great info Trevd. The Sabre lite board is very similar indeed! There seem to be only a few minor differences which are inconsequential anyway. For example the tablet have less USB and no Ethernet. I think it could be a good starting point.
I guessed when I started this project it wouldn't be a quick fix but that't not a problem, At the end of it I will have my own working ROM and that's the point.
I can see the Freescale chips being taken more in to the main stream in the future. The tablet is VERY fast and reliable it has just been let down by poor, half-arsed software. For example all the aspects of Android relating to telephony have still been left in.
Thanks again,
Click to expand...
Click to collapse
Plz keep us in the loop on how the rom is comming along.
Not that many I.MX6Q roms out there yet, and im sure many peeps are waiting for it
Thx for giving it a shot
Ill be watching
Corw1n said:
Plz keep us in the loop on how the rom is comming along.
Not that many I.MX6Q roms out there yet, and im sure many peeps are waiting for it
Thx for giving it a shot
Ill be watching
Click to expand...
Click to collapse
I'm one if those hoping for a decent rom... Apparently freescale have released a beta for jelly bean on the imx6.
MrVanDango said:
I'm one if those hoping for a decent rom... Apparently freescale have released a beta for jelly bean on the imx6.
Click to expand...
Click to collapse
Oh? Where did u find that? Been googeling my ass off trying to find a freescale jb rom....
Hope it comes tho.....already ordered my ampe a10 quad.....
Corw1n said:
Oh? Where did u find that? Been googeling my ass off trying to find a freescale jb rom....
Hope it comes tho.....already ordered my ampe a10 quad.....
Click to expand...
Click to collapse
You can download it from github. I can't post links at the moment. If you can't find it PM me and i'll forward the link i have.
MrVanDango said:
You can download it from github. I can't post links at the moment. If you can't find it PM me and i'll forward the link i have.
Click to expand...
Click to collapse
any updates on this? i cant find it on github either.
goldenpipes said:
any updates on this? i cant find it on github either.
Click to expand...
Click to collapse
The Freescale Github account is here, and it doesn't look like they provide much more useful stuff than their meta-packages there: github.com/Freescale
What I know is that for every SoC they have a page (sorry, not allowed to link yet. just search "i.MX6" on the freescale website) where they offer demo images and at least a set of patches with some documentation on how to build that Android branch.
E.g. at "Operating System Software-Board Support Packages" you can find a demo image for Kitkat and a source package: "IMX6_KK442_100_ANDROID_SOURCE_BSP" (you have to register a free account with your mail to download this). Then usually it works like this:
Get the according AOSP branch from Google
Apply patches provided by Freescale
Clone their kernel repository
Clone their uboot repository
Build
Look for a document named "Sabrelite-Android_User's_Guide.pdf" for more detailed information. Sorry, I can't remember if it was included in the source package or in another download provided in their list.
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
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.
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.
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 !