Related
I am a noob to these forums and this seemed the best place to ask considering it is a Q&A forum. Considering the G2 is a stock android device how hard would it be to make a stock gingerbread ROM for it? Are any devs out there working on it? Is teamdouche working on CM v7 based on 2.3? I have been looking around for any inclination of this but have seen none whilst other devices get gingerbread ported over/compiled for them. Just want to know the status (or hopefully an ETA) on a Gingerbread ROM for the G2. If I posted this in the wrong place or this has been posted before my apologies.
Sent from my HTC Vision using XDA App
I don't know if it's out yet, mang... but I'm sure that once it is, it'll be a hot commodity. The modding community is absolutely amazing and I think they seriously need to be hired by some of the mobile companies out there. Their work is fantastic.
well nobody can make a rom or anything until the source code is released...and that hasnt happend yet. as soon as the nexus s comes out (which is this week) then the source code will be extracted from gingerbread and itll be able to be used. right now we just had a SDK file, and that really isnt used for anything but looks. mainly used for themes and such.
Then why does the EVO have a full working ROM for gingerbread? I believe the DESIRE and the HD2 also have it going.
Sent from my HTC Vision using XDA App
There isn't a working gingerbread ROM for the EVO, it's just FroYo with some parts ripped from 2.3. Gingerbread will be released in a couple of days along with the Nexus S, after which the AOSP will be ported to existing devices - but it'll still be a few days, if not weeks until something stable comes out.
I wouldn't hold my breath for it.
My apologies for my ignorance. I thought they were actual 2.3 builds considering the XDA posted list says "devices running gingerbread". So absolutly nothing can happen with gingerbread until a device with gingerbread (nexus S) comes out?
Sent from my HTC Vision using XDA App
Cyanogen will not port it to the G2until 2.3 is released for the G2.
Sent from my CyanogenMod G2 using XDA app
Veiger said:
My apologies for my ignorance. I thought they were actual 2.3 builds considering the XDA posted list says "devices running gingerbread". So absolutly nothing can happen with gingerbread until a device with gingerbread (nexus S) comes out?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Not a problem, you were just asking
All we have running Gingerbread right now is the android emulator, from which we can pull apk's and libs, but most of them need tweaking to get them to work on FroYo. Plus I don't know if the market works on Gingerbread.
ddgarcia05 said:
Cyanogen will not port it to the G2until 2.3 is released for the G2.
Sent from my CyanogenMod G2 using XDA app
Click to expand...
Click to collapse
Is that an actual statement from teamdouche/cyanogen or just from studying release behavior in the past? When you say release you mean T-mo pushes it as an OTA correct, I know someone on here will "release" 2.3 long before T-mo stamps it for approval.
Sent from my HTC Vision using XDA App
keinengel said:
Not a problem, you were just asking
All we have running Gingerbread right now is the android emulator, from which we can pull apk's and libs, but most of them need tweaking to get them to work on FroYo. Plus I don't know if the market works on Gingerbread.
Click to expand...
Click to collapse
So at the moment there is no actual gingerbread (save for the reveiw models floating around phonedog,mobileburn,etc are unboxing) out just froyo with the modified characteristics of gingerbread? Pardon the question if it seems silly, most of the comment went over my head.
Sent from my HTC Vision using XDA App
I'll bet we have a ported ROM before New Years, usually a huge release like this gets all the attention of the devs. Especially since with perm-root, s-off and several stable 2.2 ROMs, the devs don't have all that much to work on atm.
Team Villain were working on one, but it became clear that there was going to be no way to make Audio work until AOSP is out so its on hold until then.
and without audio a phone is useless, no ringing, no sound in calls, no music etc etc
Lennyuk said:
Team Villain were working on one, but it became clear that there was going to be no way to make Audio work until AOSP is out so its on hold until then.
and without audio a phone is useless, no ringing, no sound in calls, no music etc etc
Click to expand...
Click to collapse
Definatley looking forward to it when Villain gets their hands on the source code. I bet T-mo's is going to be ladened with the same bloatware that their 2.2 install on the G2 had.
Sent from my HTC Vision using XDA App
Well atleast we have the themes for now, that will hold me over for a couple weeks but not to impressed by the nexus s enough to shell out $520 I might just buy vibrant when functional gingerbread port is out allot cheaper and almost same phone well close anyway.
Sent from my G2 Cyanogen 6.1 gingerbread theme
Honestly I would wait if your shelling out any money for anything samsung just placed a MASSIVE order for tegra 2's today which hints at dualcore phones sometime in q1 or Q2 next year hopefully. Wait for the qualcomm dualcore and nvidia dualcore wars to begin.
Sent from my HTC Vision using XDA App
Anyone know roughly how long it takes google to drop the source in aosp after the sdk is released?
ddgarcia05 said:
Cyanogen will not port it to the G2until 2.3 is released for the G2.
Sent from my CyanogenMod G2 using XDA app
Click to expand...
Click to collapse
Highly doubt that's true. I came from a CDMA Hero running CM6 RC1 (Froyo) and as most of us know, the lower end devices (such as the Hero), never got an official 2.2, yet there was a fully functional, highly stable CM6 out for it.
Which ran magnificently BTW.
Ah yeah, those seem to be more like proof of concept. Once a retail version of handsets start coming out with Gingerbread, as well as the source code, I imagine we'll start seeing custom ROMs based off it.
Veiger said:
Honestly I would wait if your shelling out any money for anything samsung just placed a MASSIVE order for tegra 2's today which hints at dualcore phones sometime in q1 or Q2 next year hopefully. Wait for the qualcomm dualcore and nvidia dualcore wars to begin.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thats all i needed to hear...samsung should'nt getanybody money with their softaware build qaulity and support
Gingerbread doesn't seem to be very promising though, what's with all this hype around it?? The update seems pretty piss poor to be honest. Nothing much.
I beleave the Miui rom can be the best rom out there but I hardly see anyone talk about it or talk about working on it for the g2. Is any one in modaco working on this rom yet?
Sent from my HTC Vision using XDA App
cwalton4077 said:
I beleave the Miui rom can be the best rom out there but I hardly see anyone talk about it or talk about working on it for the g2. Is any one in modaco working on this rom yet?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thought it had somewhat active dev already...
http://forum.xda-developers.com/showthread.php?t=871344
Might want to ask over in Modaco though if you are looking for a version from them?
what so good about miui anyway?
i just don't see it as the best rom or anything
to be honest, i like the sense ui more
I personally think it makes a phone into an iphone wannabe. I specifically bought this phone *because* it wasn't an iphone.
Sent from my T-Mobile G2 running Cyanogenmod.
Hm so Nexus S was update to 2.3.7
I wonder if that's some security fix like 3.2.1 was for Honeycomb the other day...?
http://www.androidpolice.com/2011/0...-gwk74-with-google-wallet-for-the-nexus-s-4g/
Is it me or does it make you wonder why they don't kind of insist that 'security fixes' are actually pushed out?
2.2.2 / 2.3.3 are the latest official versions for the Desire - I guess AOSP builds will probably see a quick update sometime in the future
I'm going to have to sync my repository as I didn't even know 2.3.6 existed
Sent from my HTC Desire using XDA App
Am using MIUI android 2.3.5 so I think this RoM will update soon.
Isn't Miui based on Cyanogen?
I can't see any advantage to this update tbh.
Sent from my HTC Desire using XDA App
rootSU said:
Isn't Miui based on Cyanogen?
I can't see any advantage to this update tbh.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Not sure lol I do know MIUI was on 2.3.4 then updated to 2.3.5 not so long ago.
I haven't noticed any AOSP roms going to 2.3.6 either.
I'm happy with my rom on 2.3.5 tbh. I would have been happy on 2.3.4 to fix the clear text password transmission issue, but at the time since 2.3.5 was out, I swa little point not using it.
2.3.6 is just bug fix for Voice, nothing more.
Terepin said:
2.3.6 is just bug fix for Voice, nothing more.
Click to expand...
Click to collapse
Yeah voice search I guess, thats all I could find. Cant find anything for 2.3.7 except google wallet, only for sprint users...
2.3.7 went out for Nexus S
2.3.6 recently went out for Nexus One.
The last few updates I haven't seen any report on anything much interesting being added - but they could also include "security bugfixes" and other undocumented features I guess
I didn't realise that 2.3.6 wasn't out for Nexus One so I wonder if that's why AOSP (and AOSP based Cyanogen and MIUI) ones haven't really gone from 2.3.5 -> 2.3.6 yet?
Probably. I.didn't know but I wouldn't bother unless it offered something
Sent from my HTC Desire using XDA App
TBH this forum seems a bit lonely... and my EpicParts question was easily abandoned
Whatever, greetings and happy new year to every one out there!
Today I happen to dig out a Sense 4 ROM for our E4G which boots, doesn't reboot THAT often and is resized well (what, you want links? I think that's a private workspace and maybe I shouldn't tell). But what bugs me most is that SystemUI (statusbar) always FCs for no reason and I can't do anything with that.
So here I got a HTC Incredible S ("vivo", which is the port base for our Sense 2.1 ROM) with a fully-functional Sense 4.1 build. Everything's working and things are better sized for WVGA. And it's smooth. Considering it's a single core device, I think there is already no obstacle blocking the port (I know that Sense4All project paused because One X is a quad core device and gets all sorts of reboots. Correct me if I'm wrong).
Thus, I wanna ask, as a non-coding noob:
1) Is porting process the same as common tutorials (copying frameworks, libs, etc)?
2) If not, is this even possible (to have Sense 4.1 ported from vivo)?
3) If not, again, what can I do to improve my current build on hand (i.e. simply stopping the SystemUI FC and maybe adding more HWA)? I don't intend to use the ROM as a daily driver... Just a tool for showing off
So... Thanks again for reading the thread and hope you can offer some guidance
Sent from HTC Incredible S @ Sense 4.1
If there was a stable version of Sense 2.1 or 4.0, it would be my daily driver. I really hope this project isn't abandoned.
xDecapitator said:
If there was a stable version of Sense 2.1 or 4.0, it would be my daily driver. I really hope this project isn't abandoned.
Click to expand...
Click to collapse
2.1 is already very usable apart from BT (nah I don't use that), but many devs have already left or are silent. Must be with their new toys. That's why I'm trying to help. If I had time in winter vacation I'll try a bit, but hope not too high
And so I need some guidance and answers... Please. Even one answer will do.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
2.1 is already very usable apart from BT (nah I don't use that), but many devs have already left or are silent. Must be with their new toys. That's why I'm trying to help. If I had time in winter vacation I'll try a bit, but hope not too high
And so I need some guidance and answers... Please. Even one answer will do.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
You can try to pickup where our last dev left off,
http://forum.xda-developers.com/showthread.php?t=1717089&page=18
The issue last reported by xboxfanj was that he too, got many force-closes.
Shinydude100 said:
You can try to pickup where our last dev left off,
http://forum.xda-developers.com/showthread.php?t=1717089&page=18
The issue last reported by xboxfanj was that he too, got many force-closes.
Click to expand...
Click to collapse
I do want to, but I'm not a code dev and know almost nothing except that "brute-force" porting method, and I don't know whether that will work.
I mean, here I got a fully working Sense 4 build on a SINGLE-CORE device, so is this a proof that porting to us is also possible?
Sent from HTC Incredible S @ Sense 4.1
You ported sense 4 to an htc phpne which is much easier than porting it to something not even close to compatible with the hardware so it will be more difficult
Sent from my SPH-D700 using Tapatalk 2
phonehunter59 said:
You ported sense 4 to an htc phpne which is much easier than porting it to something not even close to compatible with the hardware so it will be more difficult
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
But... I said
1) We HAD a now paused project that has ported Sense 4 and made it boot
2) I have a better Sense 4 base ROM (for our device, not HTC's) at hand with fewer random FCs
3) xboxfanj said that the port reboots because One X is quad core, and the ROM will keep searching for the extra cores. But IncS is single core and runs that beautifully (its port is based on One V and Desire X)
And that's why I'm seeking answers.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
But... I said
1) We HAD a now paused project that has ported Sense 4 and made it boot
2) I have a better Sense 4 base ROM (for our device, not HTC's) at hand with fewer random FCs
3) xboxfanj said that the port reboots because One X is quad core, and the ROM will keep searching for the extra cores. But IncS is single core and runs that beautifully (its port is based on One V and Desire X)
And that's why I'm seeking answers.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
Part of the problem is that we couldn't port qualcomm roms which would be stable if they booted, but we never got it booting. Tegra is all intercoded into libs and looks for kernel files we don't have which causes it to reboot and be unstable.
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
Part of the problem is that we couldn't port qualcomm roms which would be stable if they booted, but we never got it booting.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
...And why?
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
...And why?
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
To be honest, we never quite figured it out. We never got a proper logcat, since it only gave us unhelpful information, which means it doesn't even start to fully boot.
xboxfanj said:
To be honest, we never quite figured it out. We never got a proper logcat, since it only gave us unhelpful information, which means it doesn't even start to fully boot.
Click to expand...
Click to collapse
And this means all my expectes efforts should be in vain, huh?
But check this, I got a Sense 4 ROM from marcusant's site and it's a port from Desire Z, based on One V seemingly. So far apart from all the hardware issues (wifi, cam, sensor), only thing that prevented me from sticking to it is that SystemUI often FCs. And I think that is another base to start on, since IT'S QUALCOMM.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
And this means all my expectes efforts should be in vain, huh?
But check this, I got a Sense 4 ROM from marcusant's site and it's a port from Desire Z, based on One V seemingly. So far apart from all the hardware issues (wifi, cam, sensor), only thing that prevented me from sticking to it is that SystemUI often FCs. And I think that is another base to start on, since IT'S QUALCOMM.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
What it called? I must have made that but i don't remember
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
What it called? I must have made that but i don't remember
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
And I think that must be your ROM 'cuz I've never heard of Marcusant doing that...
It's SpiderSense.
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
And I think that must be your ROM 'cuz I've never heard of Marcusant doing that...
It's SpiderSense.
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
I think that is just the original ROM but with modified app and framework.
xboxfanj said:
I think that is just the original ROM but with modified app and framework.
Click to expand...
Click to collapse
Is that so? There are two items in About Phone indicating phone model. One of them says "HTC One V", which I think is the port source, while the other says "HTC Desire Z", which is the device ported to I assume. I know that these can be modded, but why the hell does anyone take the trouble to mod it to Desire Z when we are Epic 4G? Thus I think it's a Qualcomm port.
Have you looked into it yet? Or maybe it's really your work and you know about it?
Sent from HTC Incredible S @ Sense 4.1
AndyYan said:
Is that so? There are two items in About Phone indicating phone model. One of them says "HTC One V", which I think is the port source, while the other says "HTC Desire Z", which is the device ported to I assume. I know that these can be modded, but why the hell does anyone take the trouble to mod it to Desire Z when we are Epic 4G? Thus I think it's a Qualcomm port.
Have you looked into it yet? Or maybe it's really your work and you know about it?
Sent from HTC Incredible S @ Sense 4.1
Click to expand...
Click to collapse
I had probably used the desire z build prop as well so it used some lines for our resolution. It's definitely my work. I remember making it..
Sent from my LG-LS970 using xda app-developers app
xboxfanj said:
I had probably used the desire z build prop as well so it used some lines for our resolution. It's definitely my work. I remember making it..
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
...So this means I should give up on that huh? Sigh.
Sent from HTC Incredible S @ Sense 4.1
You're only limited to the limits you place upon yourself, research, persevere, and you may get it working.
Sent from my SPH-D700 using xda premium
Shinydude100 said:
You're only limited to the limits you place upon yourself, research, persevere, and you may get it working.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Thanks for the encouragement, dude, but Senior III is extremely stressful in China, so I don't have time to look into anything that serious for now.
Sent from HTC Incredible S @ CM10
Today i got a message from HTC saying "Namaste! New android software version 4.2.2 for your HTC Device is here!Please upgrade for better data experience at www.htc.com (data charges apply)".
Is it true that we have now received official jellybean update from HTC ? Can anyone confirm it.
I'm on latest Leedroid rom btw.
I also found something here -
http://technosamigos.com/htc-android-4-2-jelly-bean-update-device-list-schedule/
I don't know if I can believe it. If it's true though this would mean good things for custom ROMs based on stock 4.2 becoming much more stable I would assume?
Sent from my Desire HD using xda app-developers app
4.2.2 Jellybean isn't even on the HTC One yet, whoever sent you this was trying to scam you, so don't bother trying to update
Sent from my Desire HD using Tapatalk 2
I dont think you would get official update notifications with a custom rom. Especially nonsensical notifications about 4.2.
I remenber that with the arrival of the first ICS Rom´s, we receive a mail fron HTc congratulating us on our new terminal. Maybe it´s the same.
Take a look in settings/about phone, maybe ro.product.device is wrong in build.pro and htc is thinking you have another device (One X or something like this)
It is either a prank, or an error. DEFINITELY not an official update. Unrooted explorers also getting this message.
When I flashed cm10.1 Google congratulated me on my new galaxy nexus. Lol. I think previous posts about them thinking we have a different phone are correct.
Sent from my Desire HD using xda app-developers app