[Q] Pertaining Adreno 2XX Binaries - HD2 Android Q&A, Help & Troubleshooting and Genera

Will this release really help our HD2's properly run HWA on ICS Roms? I'm asking because I'm not a developer and was hoping to get a more technical answer from someone who is more tech savy Plus I read on a post from texasice that they were not going to be of much help because they've been out for months :/
Source: http://forum.xda-developers.com/showpost.php?p=23702261&postcount=2871

I hope they do help cos I would really like ICS running properly on the HD2, but for me it isn't suitable for daily use. However if these haven't helped at all yet (assuming the leak was legit) then I don't see what they could do

firstly, libs has latest version (build at 09mar 2012 )
secondly, libs - not all that is need. sdk - that powerful tool! now there is libs+sdk in public - so you could integrate lib into rom and... yes, it will take a time for rework source code, but this libs is not useful - it just need to rewrite quite a lot of android source.

Related

compiling your own roms

so... here's what i'm thinking.
how about setting up a vmware machine with all the source code for android on it, so that when a new version comes out, you can compile your own rather than waiting and then flash it to your phone. you could add your own modifications and any others that are out there.
this is a win / win situation as you get your own compilation, your own custom build and can screw about with the code it as much as you want as it's on a virtual machine.
you could update the android source code by pulling it online. and because it's a virtual machine, you don't need to worry about compilation issues across different machines.
i'm thinking about doing it - who'd be interested?
That's what I'm doing. It's FUN but to be honest it's quite a pain in the a$$ when you sync the master branch, compile, flash, and found out that the resulted ROM does not working properly and can't find any information about how to fix it.
BTW, I can hardly find the info on modifications -- most topics here are ready-to-flash ROM releases but no info on development. I did found some useful information in Nexus One forums, though.
Any suggestions on where can we find the resources regarding compilation and modification of AOSP?
well, my instincts tell me the modifications are "closed-source", hidden away from you. who knows what sorts of nasties are in the actual rom that's sitting on your phone. logging your every move, grabbing every site you visit, logging everything you type etc.
so, what's needed for a more successful dev community as far as i'm concerned is to allow the users to pick and choose what mods they want. this is an adp after all, and is one of the easiest phones to compile for.
so, if there's an active community compiling their own roms, then mods will perhaps become more open source with diffs / additions to the android source, which in itself will be better for users, developers and heck, who knows who might actually add it to the android source?
as for info for building:
http://source.android.com/source/building.html

[Q] Creating a custom ROM

Hello. I am interested in building my own ROM. I have some computer knowledge, but I want to know, what tools and files do I need for creating one. So maybe someone can guide me or point me to a tutorials. I basically just want to try some things.
Is there a way to brick my phone by using a custom ROM?
Also, what is android 2.3.5? Google's latest is Android 2.3.3 .
Android Latest stable release
Tablets: 3.2 (Honeycomb)
Phones: 2.3.5 (Gingerbread) / 25 July 2011; 38 days ago
Latest Android release is 2.3.5 for phones
good new, should be more like you.
Latest android for smartphones is 2.3.5.
Regarding advices to build a new rom, nothing better than to speak to those that already did and have the knowledge (stcokwell, DZO, FFranco, Knzo, etc)
Search the posts of each rom and speak with respective developers.
Good luck and I waiting for your rom to test it
I'm interested too, but it requires more knowledge about linux. Kernels and so on.
So i'm thinkin is better to build kernels, there is sources, there is websites with how to and so o.. rom is more complex.
I'm bringing this thread up now.
I am currently downloading CyanogenMod's source, because of what I've read android.git.kernel.org is down. My first idea was to do a proper scene port of the latest Android. But well, this has better documentation anyway. So, I haven't got the source yet to browse, but is there a way to make a general build and if I understand correctly, it creates me a system.img? How to make it flashable by recovery? And if it fails to start, can I still get to the recovery? And about kernel, this has to be modified too, right?
And for last, if anyone has a good Android source code browsing/modifying e-book/video/whatever, can I have it?
-e-
I found that CyanogenMod can automatically make a signed .zip and on normal Android AOSP I can make it with "make otapackage". Is that right?
Any good read?
u8800,cm7,[email protected]
PlanDreaM said:
Any good read?
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Start from here
http://forum.xda-developers.com/forumdisplay.php?f=613
Good luck!

[samsung i857(doubletime)]ROM devlopers and users of this phone

HI all , i lunched this thread after weeks of googling and usless search for a new stock or custom rom to update my phone (samsung sgh-i857 doubletime) it's a dual screen phone with querty built-in keyboard it's from at&t and it is stuck on android 2.2.2, i'm very sad that they and after years from lunching it didn't back it up with a single soft update -_- ... and i know that there are users who bought this phone like me and seek help.. i know that it's not this easy but if you are a devloper help us by creating a custom rom for it ....if you are a user of this phone please support this thread by commenting so we can get an update for it :good: ps: i attached informations for it's cpu
Hello good sir, I like you am a noobish Doubletime user who is struggling to update it to Gingerbread. So far I have been somewhat able to use the Cyanogenmod source code and I have built a CWM Recovery for the device but that seems to have hard bricked it... I ordered a new one off ebay for $15 and I'm ready to start cooking. You have my support!
Just an update.
I have a plan I have on how to get this runnin.
1. Port CWM to the DoubleTime through Cyanogemod 6.
2. Get a working version of Cyanogenmod 6 working on the DoubleTime to hopefully free up some space.
3. Find if Gingerbread can run on Froyos kernel.
From there I'll either be building a GingerBread compatable kernel or Cyanogenmod 7 depending on compatability. Any advice or help would be very appreciated.
Being new to ROM building I'm a little lost and hesitant on flashing things but here's what I know so far.
The DoubleTime uses a Qualcomm MSM7230 same as the HTC Vision. I forked it's Github respiratory and I'll be using it as a base as recommended by the Cyanogenmod porting guide.
The partitions sizes (as a accurately as I can estimate them) are:
/cache=21.05MB
/data=176.65MB
/system=194.38MB
I may need to know the recovery partition size but I'm not sure how to find that out.
I have the recovery.img and the boot.img as well as the zImage. So as soon as the repo sync is done I'll be on my way.
I'm back again today with somewhat mixed news, I can find most of the partitions and their names (I've learned a lot today) but I can not seem to find the boot, recovery or ramdisk partitions. I'm already boggled by the what seems to be unconventional naming setup for partitions. Put all of my "notes" in a text docement in the attachments section. Any help with this is very appertiated. I can type and post anything into the ADB shell you need me too.
I'm beginning to feel like I'm talking to myself, I probably am...
Upon reading forum rules and such it has come to my attension that this is the wrong forum for this kind of thread, So I have made a new thread in the Miscellaneous Android Developement Forum that will hopefully be more useful at getting more proffesional and opinionated help.
http://forum.xda-developers.com/showthread.php?t=2651728

Developing Discussion | ROM & Kernel Dev./Port.

Hi Everybody
after some weeks Trying developing ROM's and Kernels i almost Give up... the kernel developing to MTK SoC is too much different compared to qualcomm SoC's (To me at least...) after compile more than 10 kernels to Run at my phone i only get Bluetooth and Radio FM not working with random reboots annoying frequently... but a real modifications to get this phone more smooth usage fail every time...(if you only compile the original source kernel it will run exactly like original kernel...)
I'm too n0#b alone to get everything running at developing process(kernel or ROM dev.).. at qualcomm phones(Xperia Acro S and Xperia L), i get more things running correctly with much more help from others Developers... but not released anything because it will be more from the same as others releases...
so if anyone here have more knowledge about that developing process things i have the Kernel Source and ROM platform to our phone...
---
i already try make CM12.1 run too.. but don't boot =#.. and if get work soon will be too much unstable to release, like my kernels =#
i will try port CM12.1 from @fire855 using that tutorial
the other possibility is try make compile the CM12.1 using our sources with modification from this ROM
but i will need help to make it compile right =#
so.. i will like have a discussion about that process with you guys... if anyone have some experience to help our phone have more custom's things to don't be locked with Original stuff/performance only.. if anyone have a useful guide, video or tutorial to compile anything to MTK SoC's it will be great too :highfive:
I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk
Ilxaot said:
I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk
Click to expand...
Click to collapse
already started try port CM12.1 ... but will not work too much things... almost every sensor will not work because that cross-firmwareOS port (CM Modules Drivers have a different compilation process =#) what i can do is try upgrade our source kernel using other MT6592 Sources to can compile the CM12 to our device... but again i will need find Module Updates drivers(blob) from other phones sources... =#
and my status with that right know is fixing a lot of errors while i compiling the kernel... i don't reach the inHouse ROM Compilation to than can get more Errors on logs to fix to release a simple Almost "stable" rom to how want test if it works properly to everyone... but don't push me to get that finished.. i work everyday and when i have time i try my best to develop that :highfive:
and release a unstable ROM/kernel is a wrong because maybe can brick someone phone because my errors (ramdisk modifications, and partition table map when installing the rom)... or we can wait BLU release the Lollipop with Hope because on twitter( @ UKkazam) tell me about no lollipop updates to this phone =#
i Tweeted to [@ KazamUK] asking they about lollipop updates and receive two replays... One say about newer updates to fix bugs on OS but not about lollipop and other saying "unfortunately, not upgrades to newer Android versions will be released"... otherwise [@ BLU_Products] Replay this "Please stay tuned on our social media for future updates, thanks!"... so... we have a faith about BLU brings Lollipop to our device? i don't have sure but with lucky it will happens :highfive:
...
and the porting CM12.1 ROM don't worked with me... bootloop =# and CatLog is extremely confuse =#
Kernel source link not working
I have an opportunity to make a PORT CM12 for BLU VIVO AIR in two days. A neighbor of mine bought a VIVO AIR and I will do whatever is necessary to get the ROM on the device.
I helped the BLU VIVO IV the users to have CM12. But as the device was not mine, so I could not fix some bugs. In the same epoch I talked to a BVA User and helped the kernel issue. He had given me feedback in relation to not have phone signal and not be able to replace the IMEI. But as I had no time, and the phone in my hands, the CM12 ROM stood with him.
Currently, it is quite possible that after CM12 MT6592 to be 95% stable in most of these devices Socs, the VIVO AIR may also have.
Once I have the device in hands, I'll let you guys know if CM12 can be available for all users VIVO AIR.
But if anyone know a actually already exist a ROM CM12 for VIVO AIR and clones.... Let me know...??
That would be awesome and I'm sure as me a lot of users are going to be happy about it
Sent from my REVIVED VIVO AIR using XDA mobile app

Need help wrapping my head around building AOSP for HTC One M9

Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!

Categories

Resources