Database Develop

calling all devs, i need your help!

as most of you know im going to be building a new 1.5 rom based off of gumbo 1.5c. i want to give the phone as much of an aosp/nexus style as possible. the bad news is there is no white stock taskbar themes out there for 1.5.
SO... im asking one of our talented devs to create one or port one to work on a 1.5 based rom. i will of course give you full credits. PM me if you interested!

I know what you're going for, but the reason we haven't done it is when you try to change the clock text in the taskbar it will bootloop. And if there is a way to do it, it would be a pain and there really aren't that many people here that are still on 1.5... I hope someone helps you out though. I would try but I(along with a lot of other people) hate working on things that I personally will not use.

Leukay said:
I know what you're going for, but the reason we haven't done it is when you try to change the clock text in the taskbar it will bootloop. And if there is a way to do it, it would be a pain and there really aren't that many people here that are still on 1.5... I hope someone helps you out though. I would try but I(along with a lot of other people) hate working on things that I personally will not use.
Click to expand...
Click to collapse
im back & forth between 1.5 & 2.1 but i have several members interested in running a new 1.5c rom. damn i was hoping i could get that white taskbar too.
just something to play with until 2.1 officially drops ya know! actually according to the 1.5 & 2.1 customization page that godzon made there is a white theme that works on 1.5 but it's only for damage based roms. i just need this ported to work on a gumbo based rom.

http://forum.xda-developers.com/showpost.php?p=5023390&postcount=8

fixxxer2008 said:
http://forum.xda-developers.com/showpost.php?p=5023390&postcount=8
Click to expand...
Click to collapse
Woah holy crap, is that really for 1.5?

Leukay said:
Woah holy crap, is that really for 1.5?
Click to expand...
Click to collapse
that's what it says but i think it was for a damage based 1.5 rom. i tired to flash it and it caused a boot loop. i think it needs to just be ported to work on a gumbo based 1.5c/ pancake rom.

fixxxer2008 said:
that's what it says but i think it was for a damage based 1.5 rom. i tired to flash it and it caused a boot loop. i think it needs to just be ported to work on a gumbo based 1.5c/ pancake rom.
Click to expand...
Click to collapse
Unfortunately, that's incorrectly positioned / labeled in the thread.

JsChiSurf said:
Unfortunately, that's incorrectly positioned / labeled in the thread.
Click to expand...
Click to collapse
well you should let godzson know about that then. so theres no chance of this being ported then?
well ****.... maybe ill take pancake 2.1 or gumbo 2.1 and work with that then, i like the aosp feel.

fixxxer2008 said:
well you should let godzson know about that then. so theres no chance of this being ported then?
well ****.... maybe ill take pancake 2.1 or gumbo 2.1 and work with that then, i like the aosp feel.
Click to expand...
Click to collapse
Didn't know it was labeled as such until you pointed it out...
If the framework on your version of 1.5 is odexed (has .odex files in the /system/framwork), it is no small task to pull off, as the whole entire framework would first need to be deoxeded, so that you could then edit the services.jar file.
It's feasible, but not realistic, if this is the case, given that it's 1.5.

Froyo legend build

The source code for Froyo was released today
I am building a Vanilla Froyo rom for Legend, and should have the beta ready for download soon!

Great news
Just a stupid question: Froyo is available on AOSP. That means the sources of the OS are available. With this as a starting point, what is required to port it to a specific device (ie the legend)? Do you need the sources of the kernel (that HTC published), specific drivers (which ones?), something else?
Thanks!

MichaelAlexanderBull wel all love you!!!

gooooooood jub

Yeahhh!!!! Can´t wait.
Thanks!!!!

If you are succesfull, you will be our hero. Ohw and please put htc sens on it

This is really good news! I'm currently running the rom from Ali Ba, and I already prefer stock Android over Sense. Keep up the good work!

Great news!!!!
please let me enjoy legend without looking at my brother's nexus one with froyo

good news. cannot wait for the new ROM

qzem said:
If you are succesfull, you will be our hero. Ohw and please put htc sens on it
Click to expand...
Click to collapse
sorry i won't be able to put sense on it

MichaelAlexanderBull said:
sorry i won't be able to put sense on it
Click to expand...
Click to collapse
I think most of us would prefer it without sense ..

Y is sense so bad? I don't mind having sense maybe not the news and footprint but a lot of the sense I think its great
Sent from my HTC Legend using XDA App

I guess it will be very hard to port Froyo to the Legend because HTC devices often depend on com.htc.framework which will most likely not work with Froyo.
I'm going to try to port Froyo too once I get Vanilla Bean 0.3 ready, but this is hard work.
Sorry, not that I think MichaelAlexanderBull is doing bad work, but he simply doesn't have the source code for a few of the libraries needed to run HTC devices (especially some libraries that implement proprietary hardware calls). So don't expect a fully functional release.
I'm sure will see Froyo on the Legend though, just be patient.

ali ba said:
I guess it will be very hard to port Froyo to the Legend because HTC devices often depend on com.htc.framework which will most likely not work with Froyo.
I'm going to try to port Froyo too once I get Vanilla Bean 0.3 ready, but this is hard work.
Sorry, not that I think MichaelAlexanderBull is doing bad work, but he simply doesn't have the source code for a few of the libraries needed to run HTC devices (especially some libraries that implement proprietary hardware calls). So don't expect a fully functional release.
I'm sure will see Froyo on the Legend though, just be patient.
Click to expand...
Click to collapse
You know more than me, But im still going to try
EDIT:
I have managed to get the G1 port to boot and run on my legend in the past, it could recieve calls etc, but the touchscreen problem was there.
So i'm feeling confident that we will get a good stable release working with the ASOP release! Will probably take a bit of time, but it is going to happen

W00T!?
MichaelAlexanderBull said:
sorry i won't be able to put sense on it
Click to expand...
Click to collapse
NOT ?! You are fired!
Vanilla will be nice anyway
This is a good reason for me to root my Legend.

MichaelAlexanderBull said:
You know more than me, But im still going to try
EDIT:
I have managed to get the G1 port to boot and run on my legend in the past, it could recieve calls etc, but the touchscreen problem was there.
So i'm feeling confident that we will get a good stable release working with the ASOP release! Will probably take a bit of time, but it is going to happen
Click to expand...
Click to collapse
i'm sure you'll do just fine

MichaelAlexanderBull said:
You know more than me, But im still going to try
Click to expand...
Click to collapse
If my comment had made you run away and stop development I'd be very disappointed!
No, really, I'm confident you'll learn how to compile and port Froyo in no time. It's hard at the beginning, but once you get into it, it can be lots of fun too.
I wish you great success.

I would like to know if Flash would work in the browser.
That would be AWESOME

Froyo FTW
Cant wait for this ROM. It will be awesome
Will

you guys (michael and ali ba) should work together. this will make porting froyo to legend faster. =)

Fragamentation

I think HTC Tattoo, are to fragamented.
There should be only one rom, with all the developers, and them diferent packs with diferente window manager, apps etc..
Its a pitty that there is Roms based in CM6 but in CM6 website there is no maintainers for Tattoo..
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
Work togelher and we can go a long way...
P.S: Sorry for me English..

Start porting and developing MIUI than CM6....

inluxc said:
I think HTC Tattoo, are to fragamented.
There should be only one rom, with all the developers, and them diferent packs with diferente window manager, apps etc..
Its a pitty that there is Roms based in CM6 but in CM6 website there is no maintainers for Tattoo..
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn
Work togelher and we can go a long way...
P.S: Sorry for me English..
Click to expand...
Click to collapse
I agree with you but I think that developers like approaching a rom in their own way

It's like with Linux. There's different distributions of it. Some prefer this, and some prefer that, like some wants to have Sense and some don't.
Regarding official CM for the Tattoo, I don't think they will do that unless at least the camera works. I would have loved it if some of their clever developers could have helped getting it to work, as that's about the only thing missing to make Froyo perfect for the Tattoo.

yes camera is the only thing missing to make froyo perfect but without help from htc i don't think anyone will make it work on froyo

Camera not working HTC One

i recently flashed Faux123's M7 (UV/Intelliplug/dfsync/FauxSound/s2w/Hybrid Linux 3.4+) [May-25] Kernel using TWRP. Now after checking everything else out, everything is in full working order except the Camera's. This is extremely upsetting because although I've been in the android modding scene for nearly a year now, ive never encountered this problem, nor do i know what to do. If anyone can offer help or links to help, I'd appreciate it very much. Thank You in advance.

There's a camera fix that's needed for roms running the 1.29 and higher firmware. It should be in the aroma installer if not, then somewhere in the thread
Sent from my Tricked out HTC One

Squirrel1620 said:
There's a camera fix that's needed for roms running the 1.29 and higher firmware. It should be in the aroma installer if not, then somewhere in the thread
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
My software # is 1.26.502.12 will it work for that? And where can i find the installer?

Oh yes
i should also mention im running stock Sense 5 w/ 4.1.2 and tried flashing both listed camera fixes in the Fauxkernel thread to no avail. This is the biggest pain ever, and i am finding many other people are having this problem too.

Toxicoblivion said:
My software # is 1.26.502.12 will it work for that? And where can i find the installer?
Click to expand...
Click to collapse
Are you trying to run a custom kernel on a stock ROM? If so, there's might be your problem. Further, stop doing that--it's a very bad idea.

unremarked said:
Are you trying to run a custom kernel on a stock ROM? If so, there's might be your problem. Further, stop doing that--it's a very bad idea.
Click to expand...
Click to collapse
Yeah I am. Any stable custom ROMs you suggest for me to try? And supposedly it was only changing the Liboemcamera.so file or something like that. It doesn't matter though. I figured out that restoring it to a backup I made before I flashed the kernel fixed it. But now I have the problem I did before, with not being able to OC or especially UV and Fast Charge. As you know, this phones battery dies fast, and in the short time I was using Faux's kernel with UV/FC its battery life already had drastic improvements. So, can you help me get something stable like that?
Sent from my HTC One

Toxicoblivion said:
Yeah I am. Any stable custom ROMs you suggest for me to try? And supposedly it was only changing the Liboemcamera.so file or something like that. It doesn't matter though. I figured out that restoring it to a backup I made before I flashed the kernel fixed it. But now I have the problem I did before, with not being able to OC or especially UV and Fast Charge. As you know, this phones battery dies fast, and in the short time I was using Faux's kernel with UV/FC its battery life already had drastic improvements. So, can you help me get something stable like that?
Sent from my HTC One
Click to expand...
Click to collapse
Honestly, I'm surprised your phone booted without an issue. I've seen other folks who've flashed custom kernels on stock ROMs and be stuck in bootloops from hell.
TrickDroid and ARHD are both fantastic and I've frequently used both. They're also both running on Android 4.2.2, so they're the absolute latest you can get. ARHD focuses on refining and bettering the stock experience as much as possible without much changes. TrickDroid also has a stock look, but it lets you customize things a little more like the battery icon, clock location, etc. It's more your typical custom ROM, but it's not typical in it's awesomeness.

Thank god I'm so lucky. I never saw these problems in the forums for the kernels... No warnings, no instructions. I just followed the ones I remembered from my flashing days with the GS3.
I can find both of those on the forums, correct? And which do you prefer as a daily driver? Which one can I keep until stable CM10.1 comes out? Or maybe might want to keep even past that?
Sent from my HTC One

Toxicoblivion said:
Thank god I'm so lucky. I never saw these problems in the forums for the kernels... No warnings, no instructions. I just followed the ones I remembered from my flashing days with the GS3.
I can find both of those on the forums, correct? And which do you prefer as a daily driver? Which one can I keep until stable CM10.1 comes out? Or maybe might want to keep even past that?
Sent from my HTC One
Click to expand...
Click to collapse
I bounce between these forums and the AT&T One forums trying to help folks out so I'm not sure where I first started seeing the stock ROM/custom kernel issues. Also I may spend too much time on these forums... >_>
Regardless, I'm a flashaholic. I swapped between ARHD and TrickDroid quite regularly. ARHD seems to be updated a lot quicker, probably due to the fact that it's tweaked less than TrickDroid. The fact that Mike has been around forever too probably helps. I don't know Torxx's work quite as well. That being said, I prefer TrickDroid over ARHD because of a couple tweaks that I like such as SMS screen on, center clock, and replacing the battery icon with a numbered percentage. Not sure if those tweaks are in yet, though, since the change to 4.2.2
Just a head's up on the AOSP front, there's been alot of reports that AOSP-based ROMs are having issues with the camera. Not that it isn't working mind you but that it's taking absolutely absymal shots. This is likely because HTC baked in some software magic to improve the the image quality and those features are missing from AOSP. I wouldn't use an AOSP ROM as my daily driver until the HTC One Google Edition has been released and hopefully it will have that software magic. Figured you'd like to know since the title of this thread is regarding the camera. :

Alrite well, cool. I think I'll check out ARHD tomorrow when I get home from finals. And thanks for the foresight on the AOSP, I doubt that I would've thought of that before hand. Don't wanna lose this camera, its beautiful. xD Anyways, I'll PM you tomorrow with an update on how that ROM works out or if I have questions before hand. For now, goodnight, and thanks for all your help!!!!
Sent from my HTC One

she rdRegina
Toxicoblivion said:
Alrite well, cool. I think I'll check out ARHD tomorrow when I get home from finals. And thanks for the foresight on the AOSP, I doubt that I would've thought of that before hand. Don't wanna lose this camera, its beautiful. xD Anyways, I'll PM you tomorrow with an update on how that ROM works out or if I have questions before hand. For now, goodnight, and thanks for all your help!!!!
Sent from my HTC One
Click to expand...
Click to collapse
I need a cam fix for this rom:
http://forum.xda-developers.com/showpost.php?p=40819216&postcount=2
My details:
Android-Version: 4.1.2
HTC Sense: 5.0
Software: 1.29.401.16
Kernel: 3.4.10

Camera not working
Same here, bit new to this whole ROM thing, but basically I need full OTG support on my HTC One - So I can use DroidPlanner and my USB stick that talks to my Quadcopter - if I plug it in with the stock HTC, it pops up with "unsupported device. Now using the 4.0 rom you linked too and the OTG works fine, but now the camera just shows as a black screen... My HTC One (International) has software version 1.29.980.17 . not sure if that's the problem?
any help appreciated
syntax412 said:
I need a cam fix for this rom:
http://forum.xda-developers.com/showpost.php?p=40819216&postcount=2
My details:
Android-Version: 4.1.2
HTC Sense: 5.0
Software: 1.29.401.16
Kernel: 3.4.10
Click to expand...
Click to collapse

boardnz said:
Same here, bit new to this whole ROM thing, but basically I need full OTG support on my HTC One - So I can use DroidPlanner and my USB stick that talks to my Quadcopter - if I plug it in with the stock HTC, it pops up with "unsupported device. Now using the 4.0 rom you linked too and the OTG works fine, but now the camera just shows as a black screen... My HTC One (International) has software version 1.29.980.17 . not sure if that's the problem?
any help appreciated
Click to expand...
Click to collapse
From what i understand, OTG is based on kernel, not ROM. And this is definitely not the thread to post this on. Use Tbaldens kernel for sense or GE, and thatll be your best bet.
AT&T HTC One
ARHD 11.5
Tbalden Perf Kernel 2.1.3 UV/OC/UC

Camera not working
Thanks Toxicoblivion
Yes I'm running - teaMseven_kernel_SENSE 4.0 . The OTG is working fine with this kernel (sorry got ROM and kernel mixed up).
I tried to post a reply to that thread http://forum.xda-developers.com/showthread.php?t=2255160 , but get this stupid message below and as you will see it clearly tells me to ask about this in the General Q&A, so i'm pretty sure I'm in the right place to ask about "HTC One camera not working"?
"boardnz, you do not have permission to access this page. This could be due to one of several reasons:
Please Read: New members (those with fewer than 10 posts) are not permitted to post to development-related forums. The developer forums are intended for experienced users and developers to discuss ways to improve technical aspects related to ROMs and Software. While you may be an expert, we ask ALL users to avoid posting questions about using or installing ROMs and software in the Development Forums. To encourage this new Users can read but not post in these forums.
To ask Questions about developing your device, installing ROMs, software and themes you must go to the Q&A or General Forum.
Remember, your question has very likely been asked already, so please search before posting.
Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
"

Yes, youre in the right section, but your question has nothing to do with a camera problem. You should make your own thread (you are allowed in General & Q+A with the <10 post restriction) and title it correctly, as it will give you publicity to the people who roam those forums trying to help people in need. Im not saying i wont help (obviously i will) just, for the future. I might not be able to help with everything. Dont post on a random thread. Create your own! and if your kernel works fine, then enjoy your phone!
AT&T HTC One
ARHD 11.5
Tbalden Perf Kernel 2.1.3 UV/OC/UC

@boardnz
AT&T HTC One
ARHD 11.5
Tbalden Perf Kernel 2.1.3 UV/OC/UC

[Proposal] Fix Call Volume Proposal?

Hi everyone, this is my proposal for a call volume fix.
I'm not too experienced in developing, but I'm just trying to help.
I believe that the phone's noise cancelling application is not working well with the AOSP drivers, so I believe that using the stock phone application AND DRIVERS would fix it. Would it be possible to simply copy the stock phone.apk from the stock rom into those roms that don't work? True, you would have to go back to the old version of sense for at least the phone app, but would that fix the call volume problem?
However, I understand that perhaps the application may not be compatible with the AOSP rom and would likely require lots of work to make it compatible, but importing the proper drivers could likely be the solution to this age old problem.

123650o said:
Hi everyone, this is my proposal for a call volume fix.
I'm not too experienced in developing, but I'm just trying to help.
I believe that the phone's noise cancelling application is not working well with the AOSP drivers, so I believe that using the stock phone application AND DRIVERS would fix it. Would it be possible to simply copy the stock phone.apk from the stock rom into those roms that don't work? True, you would have to go back to the old version of sense for at least the phone app, but would that fix the call volume problem?
However, I understand that perhaps the application may not be compatible with the AOSP rom and would likely require lots of work to make it compatible, but importing the proper drivers could likely be the solution to this age old problem.
Click to expand...
Click to collapse
According h8rift and homeslice... Its the a1026 audience chip that has caused the problems... And... Unless albinoman... Now that he has the device... Can figure it out... It will be that way forever...
The fix...
Use the stock ROM...
Sorry
Sent from my Vivid 4G using Tapatalk

123650o said:
Hi everyone, this is my proposal for a call volume fix.
I'm not too experienced in developing, but I'm just trying to help.
I believe that the phone's noise cancelling application is not working well with the AOSP drivers, so I believe that using the stock phone application AND DRIVERS would fix it. Would it be possible to simply copy the stock phone.apk from the stock rom into those roms that don't work? True, you would have to go back to the old version of sense for at least the phone app, but would that fix the call volume problem?
However, I understand that perhaps the application may not be compatible with the AOSP rom and would likely require lots of work to make it compatible, but importing the proper drivers could likely be the solution to this age old problem.
Click to expand...
Click to collapse
No. you would have to add the htc framework making is senseless rom not AOSP .
It has nothing to do with the phone apk. Drivers are in the kernel.

bilibox said:
No. you would have to add the htc framework making is senseless rom not AOSP .
It has nothing to do with the phone apk. Drivers are in the kernel.
Click to expand...
Click to collapse
Could you replace the messed up drivers then?

123650o said:
Could you replace the messed up drivers then?
Click to expand...
Click to collapse
You're welcome to try. A bunch of us have beat our heads over it pretty well already though. sun_dream says he has a fix fof sense ROMs - the attachment in this (http://forum.xda-developers.com/showthread.php?t=2285611) thread. tbh I haven't looked at it and he made it pretty clear (as he always does), that he wouldn't share the solution.

homeslice976 said:
You're welcome to try. A bunch of us have beat our heads over it pretty well already though. sun_dream says he has a fix fof sense ROMs - the attachment in this (http://forum.xda-developers.com/showthread.php?t=2285611) thread. tbh I haven't looked at it and he made it pretty clear (as he always does), that he wouldn't share the solution.
Click to expand...
Click to collapse
Hi Homeslice, I love all your work on the Vivid.
I meant to suggest that this could be a possible fix for non-sense roms. I think that the Sense roms mostly have it together up until Jelly Bean.
I probably won't be able to try it until next month. I'm applying to college soon and need to finish my MIT application before November 1st.