Related
which, if any, roms for Android v2.1 up have a working Camera, Wifi and GPS ?
I would love to upgrade my wife's Tattoo to 2.1 or 2.2,
but cannot decide if any of those roms on here actually have a working camera
these are must have for her, and I did see in one post that none of them do have camera working.
believe me I have searched ... but cannot make my mind up either way !
Camera don't fully working on tattoo froyo and gingerbread custom roms yet.
At this time you can take and save photos, but no video and no preview yet.
The developers working on this though and I think that very soon we will have a fully working camera.
All other hardware(FM radio too) work fine.
thanks for that ...
I really appreciate the work of developers, and it will be well worth the wait
dancer_69 said:
Camera don't fully working on tattoo froyo and gingerbread custom roms yet.
At this time you can take and save photos, but no video and no preview yet.
The developers working on this though and I think that very soon we will have a fully working camera.
All other hardware(FM radio too) work fine.
Click to expand...
Click to collapse
carkev said:
thanks for that ...
I really appreciate the work of developers, and it will be well worth the wait
Click to expand...
Click to collapse
hi
question answered thread Closed
pls ask future questions in the Q & A its a stiky or the genral section
Hi All,
I originally posted a thread about this in the General forum, but no-one seems to know how to fix, so I'm hoping one of the super-smart developers can have a go here...
Basically, since the upgrade from Froyo to Gingerbread, the wi-fi now drops at -88dBM even when there is a perfectly useable signal/connection.
Previously I could pick up much weaker wi-fi signals as this cut-off wasn't in place. I now struggle with wi-fi at home (even with a router that's only some metres away downstairs) and in hotels, with the wi-fi dropping out if the phone's held in a certain way etc. Incredibly annoying!
Someone on the Desire HD forum found the code snippet where it mentions the -88 figure, and has managed to change/remove this. It is suggested that this code "error" is part of a Broadcom driver update.
Is anyone able to create a similar uploadable mod for the Incredible S? It doesn't seem to have been incorporated into any of the custom ROMs available, and won't be fixed by HTC either by the looks of things. It's a big problem which many users have encountered since the Gingerbread upgrade.
My original post here: http://forum.xda-developers.com/showthread.php?t=1132261
Desire HD thread here: http://forum.xda-developers.com/showthread.php?t=1058450
Code snippet: https://github.com/LeeDroid-/Ace-2.6.35/blob/master/drivers/net/wireless/bcm4329_204/dhd_cdc.c#L1288
Hope someone can come up with a solution.
Thanks.
Just noticed there is also a thread and fix for the Desire S, that offsets the threshold value.
Desire S thread: http://forum.xda-developers.com/showthread.php?t=1051674
Hope someone can implement a fix for this phone then...
What I have noted when I have tested different ROMs is that with MIUI this problem wasn't. WIFI Connection was more stable and never drops. Might the fix has already implemented there?
I would like this to be cracked by the developers here too, if they can find a way
at cyanogenmod it doesnt drop
but somehow i want to use android revolution hd, without the wifi drop issue
I've mentioned it to Mike1986 (creator of Android Revolution) a fair few times but he doesn't seem interested in fixing it which is a shame. Hence why I am appealing to the other developers on here to fix.
If it's been done on Desire S and Desire HD, why not this phone?
as far as i know it's a kernel issue
so the unity kernel must be changed
http://forum.xda-developers.com/showthread.php?t=1058450&page=7
read that thread, basically to be used it has to be made into the kernel
That's strange - some people say it needs to be built into the kernel, however if you look on the Desire S forum (link provided in first posts), they have a fix included in one of the ROMs, and the kernel is the same one the Inc S uses, from MDJ.
Ill make the edit to -108 from snq's tread and Ill post a test kerenl for you guys to test and let me know if it worked. Look for it this afternoon US time Id say about 4pm.
http://forum.xda-developers.com/showthread.php?t=1039004
So CM7 was a stellar success for our tiny lil device called Tattoo.
Now that CM7 is over, we'll are eagerly waiting for CM9. I posted this thread to know if Tattoo is going to be supported in the CM9 builds. If anyone of you has an idea of what is going on, you can reply here. Also you can use this thread for dev purposes.
Others here, you can list out what features you want to see on out Tattoos running CM9. This can come of great help to the devs until the actual thread comes up.
So when many devices have got early CM9 builds, why not us? arco68 and KalimochoAz, you there?
The CyanogenMod team already announced that one phone which will not get the upgrade is the Motorola Droid because of it's outdated hardware. You know, Droid is really similar to Tattoo specwise. Same CPU specs, same RAM amount, same internal memory.....
You draw the conclusions.
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
sunitknandi said:
pretty bleak future for us indeed. but the hero and the G1 are running early builds of it already. so if G1 can do, why not Tattoo?
Click to expand...
Click to collapse
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
BilboPC said:
Any hope for us. Be patient. They only write about Droid1: http://www.cyanogenmod.com/blog/cm9-progress-update
Click to expand...
Click to collapse
This blog post pretty much confirms that we won't be getting CM9.
Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One.
Click to expand...
Click to collapse
Our device is MUCH less-powerful than the QSD8250, which is a 1.0-1.2GHz CPU and Adreno 200 GPU System-on-a-Chip.
if that is true, wildfire wont get it too.
My guess it it will run. But should be optimized heavily for a smooth experience.
Sent from my HTC Tattoo using XDA App
I'm afraid the low resolution will be the show stopper there.
Maybe possible but it will be light version of ICS a few of the ingredients may be removed.
The screen is 2.8" n this is maybe the drawback...
I have installed ICS on G1. Its horrible ROM, Very Laggy and still needs lot of development for smoother experience. They haven't fixed the rotation problems yet. It looks to me Tatto0 will have a hard time with CM 9 because of its lower quality hardwares.
Tattoo is a 2 years old phone
Once we made it 2.1/2.2
It great already
And now we even have 2.3
What are we still asking for
As google told before
4.0is for high end
So let's enjoy the extra bonus that we get
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA App
There was a Christmas gift to buzz community from Arco
http://forum.xda-developers.com/showpost.php?p=20639586&postcount=61
which i think is a good news for Tattoo as well in terms of CM9
i still have hope!
it might not be a perfect version of android 4, but at least we can try and have fun a little bit while we wait for next year's christmas for a new phone!!
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
mattia29 said:
Look at this
http://www.youtube.com/watch?v=Ym4A82ft5pw
It's ICS running on htc g1, the first android phone! I hope we can run it also on our tattoo
Click to expand...
Click to collapse
Yes, it's running, but as you can see it's too slow, really.
Yes but tattoo has a little better specs than G1
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
That's awesome, man. I would done it if I had knowlege
arif-ali said:
Hey all,
If no-one is looking at porting CM9 to Tattoo, I could have an indicative look at doing it; no promises though; as I am doing it for HD2 at the moment, where I am spending all my time
I may have a go in a few days.
Although I may need some assistance with drivers and kernel later on
Click to expand...
Click to collapse
Please do it if u have time.
Update on compilation
Hi all,
Everything I do is all open, so you will see what I have done; this also gives others the chance to contribute
If someone wants to see my progress, then you can go to the following git repo
https://github.com/arif-ali/android_device_htc_click
and when I have a build it will be located here
http://cyanogenmod.arif-ali.co.uk/rom/test
So far quite a bit compiles, working on the wpa_supplicant part now. Looks like it may be a hack or need to look somewhere else.
I've had the Tattoo for 2 years now, but don't really know the HW much, so much research will be required. I've just installed nfinityGB, as and when arco built it.
If someone can give any input, it may speed up my work; and it will be appreciated.
Edit 1:
* Got passed the wifi, just got the drivers from gingerbread (for my notes)
Code:
cd system/wlan
git clone git://github.com/CyanogenMod/android_system_wlan_ti.git -b gingerbread
mv android_system_wlan_ti ti
sed -i s/LOCAL_MODULE_TAGS.*/LOCAL_MODULE_TAGS\ :=\ optional/g system/wlan/ti/sta_dk_4_0_4_32/config/Android.mk
* Need http://forum.xda-developers.com/showpost.php?p=20737947&postcount=27 for compilation as well
Code:
unzip ../webrtc.zip -d external/webrtc/
Edit 2:
Good News; first compile done.
Bad News; it's 4am in the morning, and I can't be bothered to test
I have no idea if it is going to work or not, and if someone is really adventurous, then feel free to try flashing the file from the following URL in about 20 mins i.e. better to try 04:30 GMT to be on the safe side
http://cyanogenmod.arif-ali.co.uk/rom/test/update-cm9-click-20120101.zip
system is going to be 162M, and gapps can be downloaded from http://cyanogenmod.arif-ali.co.uk/misc/gapps-ics-20111128.zip
Personally, I won't be able to test until tomorrow now
Edit 3:
NVM, this won't work, our system is only 150M; I will give it another go later
Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off
MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know
Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot
{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD
ROM Updated: July 20, 2016 - Update notes
This post Updated: April 24rd, 2016
If you have been here before, or if you know what to do, go right ahead and skip to the last pages for the most recent update notes. Or, if you need a bit of a starting point or got stuck along the way, it might be useful to read the remainder of this post first. Understandably the installation of this ROM didn't immediately go smooth for everyone, so if you run into troubles don't skip to the end but rather spend some time to read through the entire thread. And you can always use the search function. Doing this will probably be quicker than waiting for someone to solve your problem, especially if it's not a new problem. Plowing through the thread is probably the faster alternative.
So that all being said - Hiya! Welcome to the one and only place where you can find info and support for my unofficial port of Cyanogenmod 12.1, for the HTC One M8s. This phone is very different from the M8 and no one really knows why the folks at HTC decided to give it this name; the looks may be similar to both phones, but the M8s comes with an octa-core snapdragon 615, a 13MP camera, and a stronger battery than the M8. Under the hood you can find an msm8939, and unfortunately not as much memory as one would hope. Still, the phone works pretty good, and at least this ROM (in my opinion) is faster and snappier than HTC's original Sense ROM.
Although this ROM is not supported by the Cyanogenmod project in any official capacity, I did get some great help from some of the CM developers and from other people. Special props to @root-expert, @Rashed97, @invisiblek, @intervigil and @uberlaggydarwin for helping, and providing me with some moral support when despair was getting the best of me.
So that all said and done, let's get to it!
Port Information
All the stuff you would hope would work, works: the mobile radio, camera, wifi, GPS, NFC, audio, notification LED, sensors, Bluetooth, and the power consumption is pretty low, which is good.
There are a few things missing; the #1 requested feature is "wake phone on double tap", but I have no idea how to add support for it. I'll need someone to let me know how, and while I'm not actively searching for this myself, if someone knows, drop me a line.
Apart from this, the Dotview case thing isn't supported. And the same applies here: if someone knows how to add support, drop me a line.
My plan for many months was to get this ROM ready to be included officially by Cyanogenmod. This is not on my todo list anymore, but if someone else still wants to do the legwork, you're free to go ahead. Please keep me posted in that case.
Finally, I haven't gotten around to getting SELinux done, and I doubt I ever will. There is just not enough demand, no one requested this feature, and it's a pain in the ass to get to work.
From january of 2016 I took some time off and from april 2016 I will bring out updates at a slower pace. It's not that I stopped having an interest for this ROM, but the developers of CM are focusing less and less on version 12.1, they're putting most of their efforts in CM13 these days. Apart from this I don't think that the demand for anything missing or new is that important to merit the amount of research it demands from me. Adding to this, is that HTC provides no dev support, and the information lying around on the Internet for this phone is not exactly stellar either. So: starting from April 2016, and when time allows, I will continue to provide small updates, once a month at the very least.
So... what about CM13?
I don't have a clear answer for this. As of april 2016 we have still not heard anything officially from HTC other than "HTC will support the update to Android Marshmallow for the HTC One M8s." They have said this for a long time, and until they have released the relevant components like the kernel and their own ROM, I don't think it's possible to get CM13 to work - too much proprietary stuff is required. So until HTC delivers, I can't answer this.
CM12.1
If you are looking for the repository and/or a log of changes take a look at Github. There you can find the M8s-dev organisation and the device tree I use to build the updates.
The juicy stuff
Please make a donation if you value all the work and dedication I've put into this port. It took more than 6 full time months for me to produce, so believe me when I say it was no easy thing to create. I'm sharing it for free and hosting it myself. So a donation really does make all the difference.
And here you go:
Download CM12.1.
Adios,
-voidzero
here is cm 11 thread but don't know about m8s .
http://forum.xda-developers.com/showthread.php?t=2743579
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
here is cm 11 thread but don't know about m8s .
http://forum.xda-developers.com/showthread.php?t=2743579
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Hate to contradict you but there is a very fundamental difference between m8 and m8s, meaning the chipset is different...the topic you pointed is for m8 and I doubt the compatibility with m8s
Sent from my HTC One M8s using XDA Free mobile app
---------- Post added at 08:46 AM ---------- Previous post was at 08:45 AM ----------
Also the cm install app says m8s is not supported
Sent from my HTC One M8s using XDA Free mobile app
First post updated: if I can find someone who wants to mentor me, I'm going to try and get cm11 and cm12 to build for the HTC One M8S.
Not much response yet. I'm going to try and build CM11 and CM12, even if it's just for myself. Who knows, this might become a popular phone one day.
But it seems that this is not the case right now. So I'll play with this at an easy pace, But if anyone wants to chime in later, feel free to ping me. Or take over, if you already have experience building CM11/CM12.
Small and unfortunate update: I've posted on cyanogen fb page about our model and the response was that there is no plan on developing a Rom for us...yey, no
Sent from my HTC One M8s using XDA Free mobile app
is77gal said:
Small and unfortunate update: I've posted on cyanogen fb page about our model and the response was that there is no plan on developing a Rom for us...yey, no
Sent from my HTC One M8s using XDA Free mobile app
Click to expand...
Click to collapse
Ok.. "no plan" might just mean "maybe someday", and maybe it will help if we do a bit of work first.
We could also use a separate forum on xda for the m8s, because it is a different phone, and a quick search for "htc m8s" on Twitter tells me that the phone is being used by more and more people. It will probably become a popular phone, and why not, the octacore processor is pretty nice, so is the 13MP camera...
So we can just continue, although I will admit, due to the hot weather where I live I haven't done anything so far yet.
Experts who have ported CM before, make yourselves known if you would like to help... :good:
derp
CM12 or anything like this would be very nice for the m8s. Unfortunately I don't know anything about "cooking" a custom rom.
On my M7 I had AICP and I loved it very much
eltasmanico said:
CM12 or anything like this would be very nice for the m8s. Unfortunately I don't know anything about "cooking" a custom rom.
On my M7 I had AICP and I loved it very much
Click to expand...
Click to collapse
Agreed. I had not built CM12.1 before, only CM11. I don't think it's easy to support CM11 for the M8S, I tried to do it, but got stuck when trying to compile it... after I merged config files etc I found out that it's not easy to support this hardware (arm64-v8a).
It'll be optimal if someone more advanced will take over from me at some point, and for this week I'm a bit low on free time, but I have finally synchronised my repository and built CM12.1 succesfully for my supported HTC One S (ville). So now I can see about porting the M8S, for that I will take a look at the sources for the M8 and M9 and it will probably take a lot of trial and error. So please bear with me...
voidzero said:
Agreed. I had not built CM12.1 before, only CM11. I don't think it's easy to support CM11 for the M8S, I tried to do it, but got stuck when trying to compile it... after I merged config files etc I found out that it's not easy to support this hardware (arm64-v8a).
It'll be optimal if someone more advanced will take over from me at some point, and for this week I'm a bit low on free time, but I have finally synchronised my repository and built CM12.1 succesfully for my supported HTC One S (ville). So now I can see about porting the M8S, for that I will take a look at the sources for the M8 and M9 and it will probably take a lot of trial and error. So please bear with me...
Click to expand...
Click to collapse
Hey man, I just wanted to say thanks very much for starting this thread. I will help and support in anyway I can, just got an M8s yesterday. Good luck and I'll stay tuned to this thread for anything I can help with.
Hi
Why can not change dpi by editing build.prob file
I need 280 dpi but in display setting just see 320 for minimum
Is there any way for android 5.1.1
Thanks
Sent from my One M8 using XDA Free mobile app
I also have a m8s. But i do not know anything Bout these rom making.. looking forward for your assistance guys. Please tell me why the hell this ir blaster is not working!
@jd1001 thanks for the kind words. You gave me some extra motivation! Heh, I wrote a reply earlier but it got discarded by the damn mobile app. In short, last week other tasks kept me busier than expected, but I intend to spend a lot of time on this project this week starting later today. I'll keep you guys posted. The more I use Sense on this M8s the more I miss Cyanogenmod, so I am definitely gonna continue now that I have more time. Stay tuned!
@babakhad I think you've posted in the wrong thread, this is for the M8S, it's different from the M8 you seem to be using!
@maduwaXtreme I don't think the M8S has IR, the M8 does, not sure about the M8S though!
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
DACATA said:
http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
Click to expand...
Click to collapse
What about that link, dacata? Did you see I am a regular participator of that thread? It's about a custom recovery. Not about CM12 specifically.
voidzero said:
What about that link, dacata? Did you see I am a regular participator of that thread? It's about a custom recovery. Not about CM12 specifically.
Click to expand...
Click to collapse
yes.. Pandora custum rom beta ..Oo
DACATA said:
yes.. Pandora custum rom beta ..Oo
Click to expand...
Click to collapse
Sorry are you saying there is a ROM out for the m8s?
Sent from my HTC One M8s using XDA Free mobile app
hi all I also have the m8s and now have got twerp recovery and supersu installed rooted ready for a custom rom but I have had no luck in finding one any help would be appreciated
thanks
jd1001 said:
Sorry are you saying there is a ROM out for the m8s?
Sent from my HTC One M8s using XDA Free mobile app
Click to expand...
Click to collapse
yes.. its in beta status.. but you have root.. and busybox is working too.. only xposed framework dont wont work