Hi all, I'm starting to develop a new CM10.1 Rom. I'm going to get help by watching the code of the pyramid device because it have the same chipset and it have the 10.1 full working. Any help would be appreciated cause I'm a bit new to these things.
I know how to compile and such as others thing but I'm new so...
Inviato dal mio HTC EVO 3D X515m con Tapatalk 2
I appreciate the attempt at variety and your honesty at this being a learning experience. Don't take offense to this question but do we need another cm10.1 option? Dastin's is working very well. It might be beneficial to the community if you offered something different, maybe a different aosp rom instead?
Sent from my Evo 3D CDMA using xda app-developers app
Yes can be an alternative but the cyano isn't fully working and this make me disappointed.
I like aosp and aokp but because we already have both roms and cm too, i would like to do a cm rom (fully working if i can) cause is better than aokp and aosp.
Or you think that's better if i make aokp or aosp? Let me know, because i have not decided yet, i prefer cm also cause there is a lot of support for it and to make it.
I use Yoda ICS because Disarmed toaster (CM10) dont work 3D, videos falling and i want setting 3g only. Make with that and it will be perfect
I don't like Disarmer Toaster much, i don't know about java programming language so i can't make 3d working.
I think that i'm going to make an aokp rom, hoping fully working.
EDIT: I think that i'm not going to make any rom. Cause it's too hard and there isn't much documentation that explain device tree, kernel, android, and what do to.I don't have the skills yet to make it possible..
Mmmm, i can't give up! I must learn how to do it! Please any developer here that know how to do it, please give me informations and some explanation about device trees and kernel, and what is the binding between kernel and device trees. And if is possible what i should do to make it working, i don't mind full explanation of what to do but the necessary that i must know. Thanks!!
LoKKeR said:
Mmmm, i can't give up! I must learn how to do it! Please any developer here that know how to do it, please give me informations and some explanation about device trees and kernel, and what is the binding between kernel and device trees. And if is possible what i should do to make it working, i don't mind full explanation of what to do but the necessary that i must know. Thanks!!
Click to expand...
Click to collapse
I think you need to spend some good time searching and reading. There are many guides on how to create a ROM, how to compile from source, and other related topics of developing. That's just a few that came up in a quick search and on XDA only, there's even more when you use that thing called googl. It's all there, you just got to search. Good luck!
I'm seraching continuously on google but what i found it's hard to understand for me, or isn't explained right enough for me!
Look these device trees, they are good? What are threy used for?
Device trees: https://www.codeaurora.org/gitweb/quic/la/?p=platform/vendor/qcom/msm8660_surf.git;a=tree;h=refs/heads/jb_mr1_rb1.9;hb=refs/heads/jb_mr1_rb1.9
Some informations: https://www.codeaurora.org/gitweb/quic/la/?p=platform/vendor/qcom/msm8660_surf.git;a=summary
Maybe you should start small. Play with the stock sense Rom maybe and tweak little things there to help you learn the basics.
To be clear, I don't develop. Wouldn't know where to start. Just saying it might be good to start small.
Sent from my Evo 3D CDMA using xda app-developers app
Some time ago when i had the galaxy ace i was a developer but it was easy to make rom for it, not rom built from sources. But now it's different.
Let learn and mayby we will find your nick in our phone informations
R: New CM10.1 By Me
Hahaha I hope anyway I have found something that maybe can make cm10.1 fully working. I hope so.
Inviato dal mio HTC EVO 3D X515m con Tapatalk 2
I don't really think it is as easy as doing a search, dastin,Mazda, helicopter and agrabren would have already fixed all the issues if it is that simple, I would love for you to make me eat my words but I don't think so
Sent from my IdeaTabA2109A using Tapatalk HD
I know but i want to learn how to do it!
Start porting Roms, its easier but no guarantee it will boot, then you'll appreciate what it takes to build from scratch, I have tried to port cm 10 to my tablet and I tell you, its not as easy as it sounds, there's no shame in being a cake decorator either, take the stock ROM and customize to your liking or be like lens flare and kang a ROM and call it your own, just change the build prop, bam your a developer
Sent from my IdeaTabA2109A using Tapatalk HD
HAhahahhha that's funny xD
Anyway i'm ( doing a cool thing, i think) porting device trees from pyramid to shooteru, and i'm trying to build a cm10 with it.
Just a question, with the rom, i need to build a kernel too? And what kernel, the stock kernel on the htc-dev web site?
Start on github teamhydra or evervolv they have the android repo with manifest where u can see how its done by them what was changed in tree to compile shooteru . Its with working kernel and all.
BTW Google is ur friend .
Odesláno z mého Evo 3D GSM pomocí Tapatalk 2
I know i know, i only want to know this:
Just a question, with the rom, i need to build a kernel too? And what kernel, the stock kernel on the htc-dev web site?
Click to expand...
Click to collapse
LoKKeR said:
I know i know, i only want to know this:
Click to expand...
Click to collapse
U don't know I told u everything u can't even read.
Kernel included .
Odesláno z mého Evo 3D GSM pomocí Tapatalk
Related
Thought we'd have a thread here for mainly Dev's so we can communicate in one section with the already isolated sections.
Well, I'll start off first:
Does anyone have luck on the following?
- Creating AOSP kernel (GB base)
^ 2.6.35 source is out on htcdev, but kernels are not my expertise. I contacted cayniarb to see if he'd be willing to make one for us.
- Building any AOSP roms? GB/ICS hacks
^ Been trying CyanogenMod 7 unsuccessfully for a few days.
I don't think it's impossible, however given several tries at compiling. Resulting zips just don't boot, probably bootimage/kernel related... Think I have got all the proprietaries pulled and needed files set up by mostly mimicking other MSM8655 builds.
- Direct porting flyer roms to express
^ Something I may try soon if I can't get any progress done on my end. This is probably not very hard, but looking at the Flyer choices there doesn't seem to be a whole lot we are missing out completely on.
kaijura said:
- Direct porting flyer roms to express
^ Something I may try soon if I can't get any progress done on my end. This is probably not very hard, but looking at the Flyer choices there doesn't seem to be a whole lot we are missing out completely on.
Click to expand...
Click to collapse
I can vouch for this; using any Flyer ROM with the View kernel that matches the version of Android (i.e. GB or HC) WILL work on the View. Namely, LeeDroid's GB ROM with the OC View GB kernel. Although, using the Flyer kernel will cause a bootloop :\
The only thing we are missing out on is an optimized kernel. We wouldn't even need Flyer ports with a "proper" View kernel
I am more interested in getting ICS working right now. I'm working on the final build of CypherROM and from there working on themes and a kernel. My team has been trying to build a kernel based off of leedroid's work for some time, but haven't had any luck.
It looks like a dev just made an alpha AOSP kernel for the flyer, which we can't use of course (for the newbs reading):
http://forum.xda-developers.com/showpost.php?p=22955319&postcount=103
kaijura said:
It looks like a dev just made an alpha AOSP kernel for the flyer, which we can't use of course (for the newbs reading):
http://forum.xda-developers.com/showpost.php?p=22955319&postcount=103
Click to expand...
Click to collapse
The biggest problem is the WiMAX. Doing some research it looks as though we might be able to use HTC "speedy" aosp kernel source. Same processors and gpu. Just need to get a hold of kernel source and comparing def_configs. I have done nothing but kinda look into it. I have built the device folders too. But I knew the kernel was the issue so I wasn't going to compile. And once we get an aosp kernel we can also get a decently functional touch recovery.
Sent from my PG41200 using XDA Premium App
---------- Post added at 05:23 PM ---------- Previous post was at 05:12 PM ----------
Also, I noticed cyanogenmod kernel source for msm7x30 has the express in its defconfig. So Im looking into that right now
Hello everyone....I am a previous developer from the EVO 3D and would like to let some devs know that if they want working Beats then take a peak at the Sensation XL!
HTCFlyerX said:
Hello everyone....I am a previous developer from the EVO 3D and would like to let some devs know that if they want working Beats then take a peak at the Sensation XL!
Click to expand...
Click to collapse
Why don't you just port it for us?
If I only had more time I could actually get more done with my rom and try to build AOSP. Getting promoted has just taken away all my time.
spartan1987 said:
Why don't you just port it for us?
If I only had more time I could actually get more done with my rom and try to build AOSP. Getting promoted has just taken away all my time.
Click to expand...
Click to collapse
In my opinion beats makes music sound like crap when ported. And I have had it on multiple devices.
My aosp kernel testing is not going very well. I really need to read up on board files in the kernel to remove the sense stuff from them
Sent from my HTC_A510c using xda premium
jmztaylor said:
In my opinion beats makes music sound like crap when ported. And I have had it on multiple devices.
My aosp kernel testing is not going very well. I really need to read up on board files in the kernel to remove the sense stuff from them
Sent from my HTC_A510c using xda premium
Click to expand...
Click to collapse
I thought it sounded good on the E3D...(?)
@jmztaylor As for the kernel, would you be interested in working with my team to get the stock one working on cypherROM? Daniels7 (leedroid tweaks) gave me permission to port his tweaks over to my rom, but I need a kernel port of the leedroid kernel or something to that effect (I'd like to build our own). I don't know enough about kernels to do it myself and unixdood hasn't had any luck building one. Everytime I try to cook it in, or even make it flashable it causes bootloop. PM me if you do or if you'd like to work on anything else (including teaching me lol). Thanks!
Hmmm maybe I will just go ahead and do that but idk....getting kicked out and my ROMs shut down was not very nice....just maybe though!
maff1989 said:
I can vouch for this; using any Flyer ROM with the View kernel that matches the version of Android (i.e. GB or HC) WILL work on the View. Namely, LeeDroid's GB ROM with the OC View GB kernel. Although, using the Flyer kernel will cause a bootloop :\
The only thing we are missing out on is an optimized kernel. We wouldn't even need Flyer ports with a "proper" View kernel
Click to expand...
Click to collapse
So would LeeDroids HC Flyer Rom work on the the View?
Sent from my HTC EVO View using XDA on viperROM
wyldkard said:
So would LeeDroids HC Flyer Rom work on the the View?
Sent from my HTC EVO View using XDA on viperROM
Click to expand...
Click to collapse
No it won't. Kernel won't boot for one. I don't think I have tried putting EVO view kernel on it. But I still highly doubt it would boot.
Sent from my PG41200 using XDA Premium App
spartan1987 said:
I thought it sounded good on the E3D...(?)
@jmztaylor As for the kernel, would you be interested in working with my team to get the stock one working on cypherROM? Daniels7 (leedroid tweaks) gave me permission to port his tweaks over to my rom, but I need a kernel port of the leedroid kernel or something to that effect (I'd like to build our own). I don't know enough about kernels to do it myself and unixdood hasn't had any luck building one. Everytime I try to cook it in, or even make it flashable it causes bootloop. PM me if you do or if you'd like to work on anything else (including teaching me lol). Thanks!
Click to expand...
Click to collapse
I have tried taking flyer kernel and porting it to the view but I can't get it to finish compiling. Even after fixing the missing stuff I still was getting a lot of errors. So I put it on the back burner. I got too many projects going on. HTC policy officially is 90-120 days to release kernel source. So we are almost there. LOL
Sent from my PG41200 using XDA Premium App
@HTCflyerX What happened?
Sent from my PG41200 using XDA Premium HD app
Spartan.....hold your horses LOL....I've got to port the beats sound effect into our htcmusic app first....once that's finished ill be releasing the first Beats ROM for the View
HTCFlyerX said:
Spartan.....hold your horses LOL....I've got to port the beats sound effect into our htcmusic app first....once that's finished ill be releasing the first Beats ROM for the View
Click to expand...
Click to collapse
*tear* all that anticipation...gone...
jk
Got some good news from tiamat
Sent tiamat a message, got a reply back. There is hope for us, but we need people to jumpstart and kick development back into the Evo View. So, testers needed on irc...
Hey there, your kernels have been a hit with the vivo on the latest ICS rom we have, we built over the IceColdSandwich LorD ClockaN has been working on for the ace.
I was wondering, if you would ever take the time to look into making a few extra kernels for a few spots where development is really sore.
It's with the HTC Flyer / EVO View 4G tablets, as since we don't have any AOSP kernels, no unofficial CyanogenMod with us too.
The chipsets of those tablets uses the same one as other devices.. I don't think the Flyer has a popular chipset (MSM8255T) but the View uses the mecha's MSM8655 only to be clocked at 1.5Ghz instead of 1.0.
If it's not too much to ask, we could really use your help.
Click to expand...
Click to collapse
The only thing that has been holding me back from working on kernels for the Evo View 4G / Flyer is a lack of testers. the difference in the two processor numbers is not actually related to the processor. The 2 indicates GSM basebands whereas the 6 indicates CDMA bands. I imagine the WiFi-only Flyer is numbered 8055. In any case, to further confuse the numbering/naming scheme here, this chipset is usually referred to as the 7x30 platform. The Thunderbolt, Desire HD, Desire Z, Desire S, Incredible 2, Inredible S, Evo Shift, MyTouch 4G, View/Flyer, Bliss, Merge, Sensation XL, Rhyme, the upcoming One V, and some more I'm missing all use the same platform and should theoretically be easy to merge into my existing code. I only support the first 8, but if I had testers on any of the others, I'd be happy to add them in. The catch there is that I can't make the ROMs for it.
Send me an email or find me on IRC and we can talk more about it.
Click to expand...
Click to collapse
kaijura said:
Sent tiamat a message, got a reply back. There is hope for us, but we need people to jumpstart and kick development back into the Evo View. So, testers needed on irc...
Click to expand...
Click to collapse
Willing tester here! I'm off tomorrow and have no problem staying up late!
Sent from my PG41200 using xda premium
I'd be willing to test. Not tonight, as my View is out of juice right now, but in the future I'd be happy to try and test out stuff. Just tell me where to go.
tiamat is on IRC, find him on irc.freenode.net channel room #tiamat
His handle is cayniarb, but probably isn't hard to find and people in the room will help out.
Listen up, please don't post useless comments. And if people do, don't flame them for 5 pages because of it!
I am not an expert, but this is what I have pieced together. I know this is rather long but this will roughly explain Kernels, S-Off, and why Development is lacking.
Here is the way I see community android development. There are themers, Rom chefs, kernel builders, and coders. Themers make most of the visual changes. Rom chefs take a little of everyones efforts and actually puts the Roms together. Kernel builders make the custom kernels for sense, aosp, and miui. The coders are the ones who really understand the code and make the complicated things work (S-off/Root Access/Incomplete drivers/new bootloaders/things like that). Now really everyone works together and there is some crossover in people's abilities but a community really needs all of these in order to fully develop.
Kernels/Drivers:
Think of it this way, the hardware talks to the drivers/kernel and the drivers/kernel talks to the Os. The drivers/kernels are like the translator between two different languages. The problem is that our current kernel made by Htc only knows how to translate from our hardware to Sense. We have to make custom kernels that can translate from our hardware to Aosp Gb, Aosp Ics, or Miui.
The problem:
Faux is extremely talented but here is what he has stated as the problem in making these custom kernels:
Amaze WiFi driver is a modified TI WiFi driver. The major problem is we don't know what HTC did to the WiFi driver for the Amaze.
Click to expand...
Click to collapse
Now I have talked to Htc and they said that they won't be releasing the full source code that includes the wifi drivers because of proprietary issues. My guess is that TI is the company that owns the original drivers and they don't want them released. Faux:
TI drivers are designed to work with OMAP Chipsets not Qualcomm chipsets, so HTC had to do some major hacks to make it work with Qualcomm chipset. It is NOT IMPOSSIBLE to reverse engineer what HTC did, it's very time consuming and tedious.
Click to expand...
Click to collapse
The Solution
I don't have a solution but that is what this thread is for. We need to brainstorm ideas to make this happen.
Here is a link to Htc Dev if you would like to bug them about it (though I'm not sure this would help)
http://htcdev.com/contact
The other solution is to focus on Coders that can reverse engineer the Wifi drivers. We don't need S-OFF yet! S-Off simply allows users to flash things like a kernel and radio directly to the phone through recovery. THAT IS ALL! It will not help bring Aosp faster! Here is Faux's opinion:
IMHO, S-Off at this stage does very little if at all at this moment. Having a working WiFi source is far more important and will increase development for Amaze than S-Off... S-On is just a minor annoyance...
Click to expand...
Click to collapse
I hope that this helps to clear up why development is so slow. We don't have anyone that wants to jump in and build the Wifi drivers so that Faux and Xboarder can make the Kernels for the Aosp Roms to run upon. Xboarder is still at work hacking and slashing at the code to get it working but I think we need someone with years of experience and knowledge to join the efforts. Xboarder is extremely talented but he isn't a code guru yet. Go to the forums of previous phones you have had and look around for people who have re engineered Lib files and phone drivers. Talk to some of the other Kernel builders to see if they are interested in building the driver. This is where we need to focus effort and money in order to stimulate development.
Wifi Driver
From Squish099:
@htcdev Amaze 4G needs missing wifi driver from /platform//hardware/ti/wlan/wl1283 and /wl1283_softAP. Both are missing from Amaze source.
Found it in an old tweet faux sent to htc just after thanksgiving.
Click to expand...
Click to collapse
craigtut said:
Listen up, please don't post useless comments. And if people do, don't flame them for 5 pages because of it!
I am not an expert, but this is what I have pieced together. I know this is rather long but this will roughly explain Kernels, S-Off, and why Development is lacking.
Here is the way I see community android development. There are themers, Rom chefs, kernel builders, and coders. Themers make most of the visual changes. Rom chefs take a little of everyones efforts and actually puts the Roms together. Kernel builders make the custom kernels for sense, aosp, and miui. The coders are the ones who really understand the code and make the complicated things work (S-off/Root Access/Incomplete drivers/new bootloaders/things like that). Now really everyone works together and there is some crossover in people's abilities but a community really needs all of these in order to fully develop.
Kernels/Drivers:
Think of it this way, the hardware talks to the drivers/kernel and the drivers/kernel talks to the Os. The drivers/kernels are like the translator between two different languages. The problem is that our current kernel made by Htc only knows how to translate from our hardware to Sense. We have to make custom kernels that can translate from our hardware to Aosp Gb, Aosp Ics, or Miui.
The problem:
Faux is extremely talented but here is what he has stated as the problem in making these custom kernels:
Now I have talked to Htc and they said that they won't be releasing the full source code because of proprietary issues. My guess is that TI is the company that owns the original drivers and they don't want them released. Faux:
The Solution
I don't have a solution but that is what this thread is for. We need to brainstorm ideas to make this happen.
Here is a link to Htc Dev if you would like to bug them about it (though I'm not sure this would help)
http://htcdev.com/contact
The other solution is to focus on Coders that can reverse engineer the Wifi drivers. We don't need S-OFF yet! S-Off simply allows users to flash things like a kernel and radio directly to the phone through recovery. THAT IS ALL! It will not help bring Aosp faster! Here is Faux's opinion:
I hope that this helps to clear up why development is so slow. We don't have anyone that wants to jump in and build the Wifi drivers so that Faux and Xboarder can make the Kernels for the Aosp Roms to run upon. Xboarder is still at work hacking and slashing at the code to get it working but I think we need someone with years of experience and knowledge to join the efforts. Xboarder is extremely talented but he isn't a code guru yet. Go to the forums of previous phones you have had and look around for people who have re engineered Lib files and phone drivers. Talk to some of the other Kernel builders to see if they are interested in building the driver. This is where we need to focus effort and money in order to stimulate development.
Click to expand...
Click to collapse
Good post lots of info, s-off really isn't that much of a big deal. Interesting. The WiFi drivers really are important sucks how HTC handled the amaze, I'm really hoping they're more open with the HTC one thanks for the info.
Sent from my HTC_Amaze_4G using xda premium
I was able to flash kernel through recovery?
Sent from my HTC_Amaze_4G using XDA
knifeproz said:
I was able to flash kernel through recovery?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Uhh no...?
Sent from my NRGized Amaze...
via xda premium
HTC really messed up, and they call them self dev friendly,
same people that has got s-off on the sensation had tried to do for the amaze but they backed off,
but as you made a point s-off isnt really the problem here, the problem seems to be the drivers that htc wont realease
really the only person we have working hard on this device is Xboarder and binary100100 is doing what he can.
and he has done a really good job, and noobs had got on his nerves. We can not afford to lose him.
i really wish this phone have more developers working on getting things right, like that saying says two brains is better than one
i really love my phone but in the other hand i love roms. and as this phone its not a worldwide phone like the sensation i can understand the lack of developers
as you all know that the sensation have 40+ roms,themes,radios,kernerls,tweaks
sometimes i regret of getting rid of it, but specks says this is a better one,
had you guys ever though about asking for help on the android development forum? we might get lucky and find somebody that is willing to help.
but anyways thank you for saying it like it is and get us understand more of the situation, and me as i think all of you, would do anything to help..
I'm no dev, but i have done something
I HAVE PMED TWO KERNEL DEVELOPERS , TO LOOK INTO THIS THREAD TO GIVE A GLANCE , IF THEY CAN GIVE ANY INPUT ABOUT IT..
If there is any reply from them , i'll let the community know..
I think this is one of the important thread, we should probably have it in Development section and should be made sticky.
Mafioso said:
I think this is one of the important thread, we should probably have it in Development section and should be made sticky.
Click to expand...
Click to collapse
Lol good luck finding an active moderator to do anything in this Amaze forum besides handing out infractions. Binary bounced
Sent from my Energized HTC Ruby using XDA-Premium or Tapatalk
glacierguy said:
Lol good luck finding an active moderator to do anything in this Amaze forum besides handing out infractions. Binary bounced
Sent from my Energized HTC Ruby using XDA-Premium or Tapatalk
Click to expand...
Click to collapse
yeah, you will have more luck if you are looking for trolls flaming moderators indeed
Anyway,we cant stick everything in development, but i will see what i can do
Edit: oké, i will make a sticky collection thread.
So we will have less thread's sticked.
One or two sticked with all important info
This thread should be priority one in the Amaze forum.
Max Krivonos has Wifi working on his CM9 build for Amaze. Once he gets everything else working (which is limited to the rest of the radios, camera, and USB charge detection), I imagine the source will be released for use.
Accophox said:
Max Krivonos has Wifi working on his CM9 build for Amaze. Once he gets everything else working (which is limited to the rest of the radios, camera, and USB charge detection), I imagine the source will be released for use.
Click to expand...
Click to collapse
agreed. football usually drops a leak well ahead of the time ota goes live. either way, once we get the ics kernel, im rocking cm9 for good
mrmako777 said:
agreed. football usually drops a leak well ahead of the time ota goes live. either way, once we get the ics kernel, im rocking cm9 for good
Click to expand...
Click to collapse
Official ota will help but I don't think it will work for aosp. It will still only work with the sense until faux does some of his magic to it.
Sent from my HTC_Amaze_4G using XDA
Once cm9 comes out ill use it till aosp is out. I wasn't a huge fan of cm9 for hd2 but might change for this device!
Sent from my HTC_Amaze_4G using XDA
craigtut said:
Official ota will help but I don't think it will work for aosp. It will still only work with the sense until faux does some of his magic to it.
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
dont quote me, but i think max said once he got a hold of the ics leak, he could use the wifi drivers from there...or something to that effect
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
gypsy214 said:
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
Click to expand...
Click to collapse
If I was a Dev I would take any help I could get =\
Sent from my HTC Amaze 4G using XDA
Xxxpachaxxx is a kernel developer for dhd..he is looking into it but he wants to know what is the driver number for HTC amaze ...
Can some1 pleease tell me what it is ASAP!!
Is it bcm4329 ?? Fast please
Sent from my HTC_Amaze_4G using xda premium
dullhunk said:
Xxxpachaxxx is a kernel developer for dhd..he is looking into it but he wants to know what is the driver number for HTC amaze ...
Can some1 pleease tell me what it is ASAP!!
Is it bcm4329 ?? Fast please
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I don't know what it is but you could pm Faux123 for the info.
gypsy214 said:
he already have wifi working on cm9, but not calls, and he wont take any help. this once used to be a family in devs working together trying to get things right but now its just a race on who release it first, same thing happened on the sensation
Click to expand...
Click to collapse
He's working with a dozen other CM devs on MSM 8x60 devices. He just doesn't care for XDA. And with what this forum is turning into, I don't blame him.
Sent from my HTC Amaze 4G using xda premium
Greetings everyone,
Yesterday it itched me, there is no paranoid android for the hox+ as of yet! Thus it startled me to try to make my first rom port from the hox:silly:
Everything fine, I got all day, taking my time, comparing the roms etc etc.. You know how it goes haha!
So after some process and managing to get it booted and most things working, I can't get the Paranoid Preferences to work nor the System from the settings menu
I've uploaded the ROM, hopefully someone will be able to help me and otherwise I hope I got someone an awesome idea to do this properly and build it from source!:fingers-crossed:
I, unfortunately, do not have the resources nor the knowledge as of now to do this myself..
Rom download: removed
Any help or suggestions are welcome!
Kind regards,
aardappel12
P.S.: All credits go ofcourse to Lloir for the awesome CM10 base and to Floatshow for his PA2.53 ROM for the HOX!
I'm pretty sure half of your problems are, that your using lloirs CM framework, the prefs.apk will need the PA framework porting.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
I'm pretty sure half of your problems are, that your using lloirs CM framework, the prefs.apk will need the PA framework porting.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Yea, tried porting the framework from the PA rom but it wouldn't boot up.. Made a logcat but I'm still too noobish to make out of what the culprit was haha
I'm guessing building from source would take care of these framework problems etc?
Remove the link! No permissions asked
Sent from my HTC One X+ using XDA Premium HD app
Lloir said:
Remove the link! No permissions asked
Sent from my HTC One X+ using XDA Premium HD app
Click to expand...
Click to collapse
Apologies for that, was also merely trying to get this working for personal use. Seeing as it's an outdated version of Paranoid Android, I'm guessing the demand for this would be minimum.
But yea, once again, my apologies.
So it seems there is that Chinese Rom with Sense 4.1 and working 3D, this is amazing, however, it is the only one of it's type.
The fact that HTC did not release the Driver Sources made me somehow hate them and it was the reason why many bugy couldnt be fixed, many devs left.
So, this Chinese Rom is removed because it is not allowed according to the rules, but... why exactly?
Could someone please post information on this story, really, this is EXTREMELY important, it could change our 3volife
Is it because it's a Viper fix, why then don't they release the fix?
So, the simple question is:
What's the fuzz about the 3D-fix? Somehow no one knows whats going on!
I'm gonna make it as brief as possible.
We can't release it on XDA or link to it because it is considered kang. The ROM is based off of a Viper3D build and was used without permission. Now unless Team Venom gives us permission to release their ROM with working 3D here on XDA, we can't do it because then that's kanging someone else's work, and that's highly frowned upon here, and leads to heavy infractions
Sent from my Nexus S 4G using Tapatalk 2
I can not understand how is it possible that only one team is capable to make 3D work. Why can not someone else make it from the basis without their rom?
B3!CrAZy said:
I can not understand how is it possible that only one team is capable to make 3D work. Why can not someone else make it from the basis without their rom?
Click to expand...
Click to collapse
I am pretty sure coolexe or anryl or mwakious could do it if they have time
Somebody could definitely do it, but it would be a very hard thing to do since HTC doesn't hand out their 3D drivers. That team who got it working guaranteed was working for weeks and weeks on end getting it working, somebody here could do it for sure, but nobody has tried yet, and its probably something that's more trouble than its worth. Even if we looked at what that team did to get it working we can't use any of that, or even copy any of that because then it would still be kanging their work. Its something we either A) need to get permission for or B) take care of ourselves, but have that be 10000x harder. Its not impossible, but it is improbable
Sent from my Nexus S 4G using Tapatalk 2
This is ridiculous in my opinion.
I'll probably get flamed but the whole purpose of android being open source is so anyone and everyone can contribute and make it a better experience.
I understand the HTC drivers are proprietary, but in my eyes, if you've made something better why not share it with the world...are these 'team' members making money on these fixes, are they coming out with their own proprietary phones...that's the only reason I can see to necessitate keeping these fixes to yourself...yes I applaud any ROM dev for their work (I sure as hell couldn't do what they do) but what's the point in the end? Bragging rights? Come on!
Sent from my HTC Evo V 4G using xda app-developers app
hossman said:
This is ridiculous in my opinion.
I'll probably get flamed but the whole purpose of android being open source is so anyone and everyone can contribute and make it a better experience.
I understand the HTC drivers are proprietary, but in my eyes, if you've made something better why not share it with the world...are these 'team' members making money on these fixes, are they coming out with their own proprietary phones...that's the only reason I can see to necessitate keeping these fixes to yourself...yes I applaud any ROM dev for their work (I sure as hell couldn't do what they do) but what's the point in the end? Bragging rights? Come on!
Sent from my HTC Evo V 4G using xda app-developers app
Click to expand...
Click to collapse
Amen to that
Sent from my LG-MS770 using Tapatalk 2
kajoshin201095 said:
So it seems there is that Chinese Rom with Sense 4.1 and working 3D, this is amazing, however, it is the only one of it's type.
The fact that HTC did not release the Driver Sources made me somehow hate them and it was the reason why many bugy couldnt be fixed, many devs left.
So, this Chinese Rom is removed because it is not allowed according to the rules, but... why exactly?
Could someone please post information on this story, really, this is EXTREMELY important, it could change our 3volife
Is it because it's a Viper fix, why then don't they release the fix?
So, the simple question is:
What's the fuzz about the 3D-fix? Somehow no one knows whats going on!
Click to expand...
Click to collapse
Android is open source, you changed is the exclusive copyright? This is not unreasonable.
If anyone need help, you can email me
The rules centered around this are not android related. It has nothing to do with open source, they're xda's rules. It makes sense why they're there (that way we don't see the same exact ROM under a different name pop up every 20 minutes, etc.). I don't like the rule either but hey, its just something we gotta live with
Sent from my Nexus S 4G using Tapatalk 2
I think that we could do an exception for 3D in 4.1 sense...
http://www.android-hilfe.de/custom-...1-0-0-full-3d-beats-audio-high-quality-3.html
elitman said:
http://www.android-hilfe.de/custom-...1-0-0-full-3d-beats-audio-high-quality-3.html
Click to expand...
Click to collapse
CDMA????
SketchyStunts said:
CDMA????
Click to expand...
Click to collapse
it is a german forum. So it is probably GSM. I gonna try it now. (With my GSM-device)
Gonna be quite honest, hit up that link while you can because it ain't gonna be there for long
SketchyStunts said:
CDMA????
Click to expand...
Click to collapse
GSM - working like a charm. Using the 2.0 version. Aroma is in Germany but pretty understandable.
Sent from my shooteru using xda app-developers app
Sieht gut aus, heruntergeladen! I'll probably tear the rom apart and see about making it CDMA worthy, though I won't be able to share it once I'm done being it's Kang'ed...
elitman said:
GSM - working like a charm. Using the 2.0 version. Aroma is in Germany but pretty understandable.
Sent from my shooteru using xda app-developers app
Click to expand...
Click to collapse
Is Sense scroll lagging for you?
I'm asking this coz had no problems at all with the original chinese ROM, but after flashing this one got lags during Sense pages scrolling
thesniffer said:
Is Sense scroll lagging for you?
I'm asking this coz had no problems at all with the original chinese ROM, but after flashing this one got lags during Sense pages scrolling
Click to expand...
Click to collapse
No lags at all. What I experienced was huge battery drain. So, right now, I oam in the process of reverting back to stock ROM. Tired of all these tests. Gonna get SIII tomorrow anyway
So we have fixed 3D camera now? ICS or JB?
Don't seem to see a straight answer. Only that it is using venom tweaks without perms..?
Sent from my N7100 using xda premium
Lothaen said:
So we have fixed 3D camera now? ICS or JB?
Don't seem to see a straight answer. Only that it is using venom tweaks without perms..?
Sent from my N7100 using xda premium
Click to expand...
Click to collapse
Well, we do have full 3D working on a ICS Sense 4.1 ROM
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Hey guys just wondering if there are any devs out there that can work on kernels. I think it would be awesome to have a kernel that includes dt2w. Anyone else as interested in this as me?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
crparmer
not sure if i spelled it right.
thayl0 said:
crparmer
not sure if i spelled it right.
Click to expand...
Click to collapse
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
Yeah but I think he likes to keep thing as stock as possible.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
thayl0 said:
Not really it done a amazing kernal for cm 10.2
And I believe he is working on one for 4.4 kitkat cm 11
Click to expand...
Click to collapse
I know that but when people have asked him to add sleep to wake he didn't seem interested in that I'm not dogging him at all man he great no question asked.
Sent from my HTC6435LVW using Tapatalk
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
crpalmer said:
Adding it takes time, adds risk to the stability of the phone and gives me no benefit. My phone is heavily locked down by my IT department and with a minimum 8 character alpha numeric password, the sweep or double tap to wake is not improving my life.
Click to expand...
Click to collapse
This is why i was trying to shout out to other. I know your work is the real deal man. Its just something I'm interested in. In no way was i trying to insult you.
Kauffman_c said:
I love s2w as much add the next guy..... but try omnirom 4.4, and enable active display.... you might like it better.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what settings you use with active display but I'm not really sold using it. I like sweep2wake as well.
Sent from my HTC6435LVW using Tapatalk
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
yeah some nice s2w like the old cubed kernel so you can do just "back to home" to wake it, its so nice i dont see how ppl dont want it of course unless they have some crazy circumstance like crpalmer just described
but we have a lot of diff roms so something like this would be rather difficult to choose one version of android for this to be implemented on or many kernels, lotta work it seems.
Ask .torrented. He made a s2w kernel a few months ago. He may have a very busy schedule but if enough people ask he may do it.
jamiethemorris said:
Okay, here's a dumb question... Right now we share the AOSP kernel source with the HTC One. Wouldn't flashing a custom AOSP kernel for the One work on the DNA?
Click to expand...
Click to collapse
Yeah I Dont think it's that simple unfortunately.
Sent from my HTC6435LVW using Tapatalk
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
jamiethemorris said:
I don't think one of those kernels would be difficult to port though. I'm just wondering what exactly makes the kernels different, because if you compare the CyanogenMod pages for the DNA and the One, the kernel source link is for the M7 on both of them. I was considering trying to port a kernel myself a while back, but I couldn't find enough information online about it... I think it may be one of those things where if you have enough knowledge of ROM building and git than you just intuitively know how to do it.
Sent from my Droid DNA using Tapatalk Pro
Click to expand...
Click to collapse
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
I couldn't resist, I just had to try it. I figured the worst that would happen is I'd have to reflash my ROM. So I flashed the HTC one sti kernel here: http://forum.xda-developers.com/showthread.php?t=2507710 it flashed and booted just fine and everything works... None of the s2w dt2w features etc are working but it said it flashed successfully so I'm assuming it's running the kernel... I don't remember what it said in about phone before but it currently shows "3.4.10-CM-gbce7128 Robert @ minty #1."
Edit: yeah I'm pretty sure that's the stock kernel...
It was worth a try right?
@crpalmer would you be willing to give me some pointers on porting or building a kernel? I'm somewhat inexperienced with building, so I don't know if I should bother taking on a task like this.
Sent from my Droid DNA using Tapatalk Pro
coachcrey said:
Yeah I'm not sure either. If you wanted to give it a run for your money I'm sure palmer would give you some pointers. I would love to see a dt2w kernel!! Lol
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
crpalmer said:
Do not, really, do NOT flash a kernel for a different phone. The Linux kernel is setup to have the same core files across a huge number of devices but then have device specific files. We share the M7 kernel but we have different device specific files. These files control lots of things but the most important is determining what pieces of hardware are given specific voltages, etc.
If you want to try to build my kernel, you should be able to do so fairly easily. Porting the functionality will require some programming knowledge and some knowledge of git. If you think you can do it, let me know and I'll try to give you some first steps on building my kernel.
Porting a M7 kernel to our device might be hard. There is a high probability that they aren't necessarily keeping up-to-date on the changes to our device specific files. You'd have to figure out if they were and, if not, pull in the missing changes.
Click to expand...
Click to collapse
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
coachcrey said:
I wasn't implying anybody should ever flash a kernel not built for this phone.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
crpalmer said:
My bad. I quoted the wrong post! I just wanted to make sure it was clear that the same source is not the same as safe to flash because we have completely different hardware configuration. So, I guess it was good that I misquoted so that I have a chance to say it a second time!
Click to expand...
Click to collapse
OK right in man. Thanks for all the hard work.
Sent from my HTC6435LVW using Tapatalk
I guess my post didn't go through... @crpalmer what type of programming knowledge are we taking about? My knowledge is limited to some dsdt editing and supercollider... In other words, I'm definitely not a programmer but I understand the general concepts.
Edit: I'm not too experienced with git either but I have built cm10.1 From the source for my nexus 7 a few just as learning experience.
Sent from my Droid DNA using Tapatalk Pro