NexusHD2 Android Forum

I might stop developing CM 10.1.2 if there's not any big source code update.
I also built a CM 10.2 ROM but encountered some bugs so far.

Here is an update to the softkey mods for V2.6 of Tytung's Jellybean ROM. There are two modifications, landscape softkeys and a soft power button.

The installer ZIP file can be downloaded from this link: https://dl.dropboxusercontent.com/u/22856583/NexusHD2-JB_V2.6-SoftkeyMods.zip. The file is flashable from recovery. There are individual options to select the landscape softkey mod and the power button mod in any combination.

I suggest that you first install or update your phone to V2.6 of Tytung's ROM and boot it up before you install these mods. A few minutes after boot-up, go back to recovery and install these mods.

Installing the power button mod adds two options to the CyanogenMod navigation bar editor, an invisible power button and a visible power button. After installation, you have to turn on the mod by going to Settings->System->Navigation Bar Buttons and layouts. Click the lock icon, then the small plus sign at the left of the navigation bar. Scroll to the power button option you want (either invisible or visible) and click it. Finally, click the lock icon again.

If you previously had the power button mod installed and you do an update, you don't have to turn-on the power button mod per the previous paragraph. The settings will be preserved through the update.

Note that Tytung reduced the navigation bar height in this version of the ROM, so the previous LockFix mod is no longer needed. And the reduction in height addressed Elveneleven's request.

EDIT - the download file has been updated to fix the issue with the navigation bar height.

tytung wrote:I might stop developing CM 10.1.2 if there's not any big source code update.
I also built a CM 10.2 ROM but encountered some bugs so far.

Hi Tytung,
You are really fast:mrgreen:
Maybe you can alter the Rom name of the new cm10.2 rom when you got a release candidate so that we can test the new one without overwriting cm10.1 v2.6. That would be
btw. Just downloading and testing v2.6.

@agbommarito and tytung

Thanks for new softkeys mods and the 24dpi height of Navbar :mrgreen::cool::cool::mrgreen::mrgreen:

sent with Tapatalk 4

amazing work from genius man .. thanks very much and keep going

Anyone watching the SecureRandom flaw, that cripples the security of most Android apps relying on random numbers? CM ticket here: https://jira.cyanogenmod.org/browse/CYAN-1954 More info here http://www.symantec.com/connect/blogs/a ... sands-apps and in-app workaround from Google here http://android-developers.blogspot.ie/2 ... ughts.html.

From looking at the workaround that Google posted it seems to me this 4.2.2 CM 10.1.2 ROM is vulnerable because it is SDK API version 17. I have no idea though, how to get ahold of the patches, that Google provided to OHA partners. Bug is quite a bummer if you care about app security, not just your Bitcoin wallet.

Hi,

dunno what happened. Avira isn't detecting a the obad-trojan in V2.6 anymore.
Anyways..... installed 2.6 this morning and it looks really awesome.

Thanks tytung for your great work.

Elveneleven wrote:
Hi Tytung,
You are really fast:mrgreen:
Maybe you can alter the Rom name of the new cm10.2 rom when you got a release candidate so that we can test the new one without overwriting cm10.1 v2.6. That would be
btw. Just downloading and testing v2.6.

@agbommarito and tytung

Thanks for new softkeys mods and the 24dpi height of Navbar :mrgreen::cool::cool::mrgreen::mrgreen:

sent with Tapatalk 4

Do we really need to change the ROM_NAME of the NativeSD install path if all the basic features work well on CM 10.2 ?
Do you all prefer reused NexusHD2-JellyBean or new NexusHD2-JellyBean-CM as ROM_NAME? Please share your comments.
Anyway, I will create a new topic when I release a new CM 10.2 ROM.

Hello,

tytung wrote:Do you all prefer reused NexusHD2-JellyBean or new NexusHD2-JellyBean-CM as ROM_NAME?

If all the basic features work well on CM 10.2 I don't see a need for a new Name.
I only see a benefit for a new name for beta-testing...

Ciao,
Joachim

@Tytung, I first want to thank you for all your efforts in putting together this ROM. After Reading your previous posts on this thread, it is my hope that you'll continue developing this now very stable CM-10.1.x branch even as you shift your efforts towards CM-10.2. This is especially important in light of Cyanogen's announcement in their most recent weekly blog that CM-10.1.3 will be released in the next couple of weeks.

From every thing I've read on the CM and xda forums, CM-10.2 is a rewrite compared to a simple update. Some users will have to do clean installs when making the transition, because of system settings getting overhauled, and file system reorganization. Some apps fail on it, others have glitches. Things are getting moved around, included in one build, but not the next. It's because of this, builds from the CM-10.2 branch are currently in flux. Right now they're more 'alpha' than 'beta' releases, IMHO.

This is my only communication device. More than anything, I need stability. This is why I use your ROMs in the first place. I'll follow along with great interest as you proceed with CM-10.2, but I won't or can't switch until it's been proven stable. In the meantime I hope you won't completely abandon CM-10.1.x and will update when CM-10.1.3 is released. TIA

Edit: As to naming the new ROM based on CM-10.2, may I suggest that you keep "NexusHD2-JellyBean" and just augment the new CM-10.2 builds with "beta" until CM-10.2 is stabilized. For example, the first release based on this code could be called, "NexusHD2-JellyBean-CM10.2 V3.0-beta1". The next beta would be, "NexusHD2-JellyBean-CM10.2 V3.0-beta2", etc... When CM-10.2 goes gold, the first stable release would be "NexusHD2-JellyBean-CM10.2 V3.0". I suggest this is because you (Tytung) have become synonymous with "NexusHD2". This is your trademark (perhaps you should trademark it).

If someone types into any search engine "NexusHD2" your ROMS and forum posts come up to the top. Many others link back to here and your old ones at xda. There are numerous Youtube videos of people using or installing your ROMS. They're known all over for their stability. Keeping the naming structure consistent helps in reinforcing your well earned reputation, and as well makes things easier for those trying to find you over here. Just my 2 cents.

Ciao

@Tytung back to this ROM. Unfortunately for me, after using this ROM for a day, my observation is the change you made decreasing the button size may increase the desktop, and solve the unlock screen issue, but makes using them more difficult. There is now a much smaller "sweet-spot" to touch and activate them. I find myself now having to press multiple times where I didn't before (at least it seams that way).