yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Robbie P:
Hi mrs8an, and welcome to the forum.:)

If you are using a Tmobile usa hd2 you should be OK. So I assume you are using an international HD2 with less nand space available.

If so, you might want to create an ext4 partition on your sdcard and use the nand with dataonext install option. There are links in the first post of the rom thread on how to do this, but remember to back up your sdcard first. Probably the best option is to use your recovery to create the ext4 partition on your sdcard.

If not, and you have a tmobile usa hd2 use the hd2 toolkit, linked in the rom first post, to create the required partitions in nand.

If you have problems in the future with any rom, the more information you can give, the easier it will be for people to find a solution;)

Good luck.
[HD2 Android Q&A, Help & Troubleshooting and Genera] -pixelfreak-:
re

yes i think the same your ext4 partition does not exist, or is not formatted.

pixelfreak
[HD2 Android Q&A, Help & Troubleshooting and Genera] i6231701:
Can the background process limit be changed by shell script, i.e. using init.d to set it at boot? Since a reboot resets the settings made in developer options to "one".
[HD2 Android Q&A, Help & Troubleshooting and Genera] twoxx:
SWAP-File in NOS-Injection

Hi there!

In init-d-script "nos-injection-4cylturbo" ist this line:

#

#=============================

# SWAP ON ====================

#=============================

#

dd if=/dev/zero of=/cache/swapfile.swp bs=1024k count=600

mkswap /cache/swapfile.swp

fi

swapon /cache/swapfile.swp

Why is nos-injection creating a swapfile in cache-partition? what type of swapping is this?

I am asking, because i am using a separate swap-partiton on my sd-card and i enable swap-script in aroma-installer,

but i don't want to have 2 swap-functions in my rom.

If this swap-file is really needed:

My sd-card is a sandisk 64gb extreme. If i create a second sd-ext-partition and create the swapfile on sd-ext 2 -> will my system be faster than it is with swapfile on internal cache-partition?
[HD2 Android Q&A, Help & Troubleshooting and Genera] -pixelfreak-:
re

the nos script make the swap settings better. old settings are overwritten and replaced. the swap file is in the cache is normaly. all working files have a a small part in the cache. you must nothing delete or change. you can test a install with delete your swap partition on your sd card and make a non swap install

pixelfreak
[HD2 Android Q&A, Help & Troubleshooting and Genera] twoxx:
Yes i know, that most of the files, apps and so on are writing some things into cache-partition.

I think:

the nos-injection script is creating a SWAPFILE in CACHE-Partition. If i use nand or dataonext-installation --> Cache-Partition is on NAND-Memory of hd2.

This nand-memory on my hd2 is slower than my sd-card-memory. So reading and writing on that swapfile on NAND-Cache-Partition might be slower than reading and writing on a swapfile that is located on my sd-card. I think moving this swapfile form nand-cache to sd-ext on sd-card will speed up the system a little bit.

instead of /cache/swapfile ----> /sd-ext/swapfile or /sdext2/swapfile

Hi Pixel:

Ich hab schon verstanden das NOS injection das System etwas schneller macht. ABER: Nos-Injection scheint in der Cache-Partition ein Swapfile anzulegen. Wenn ich die NAND oder DATAONEXT-Variante verwende ist die Cache-Partition im NAND-Speicher vom HD2.

Der Nand-Speicher müsste jedoch langsamer sein als der Speicher der SD-Karte, weil der NAND-Speicher techinsch viel älter ist als die neuen schnellen Sd-Karten.

Meine Überlegung ist:

Wenn man also dieses Swapfile anstatt in der Cache-Partition des NAND-Speichers auf der schnellen SD-Karte anlegt, beispielsweise

in der SD-EXT-Partition oder vielleicht sogar noch besser in einer zweiten SDEXT-Partition um gleichzeitige Zugriffe auf die Karte nicht zu behindern, müsste das ja einen Geschwindigkeitsgewinn mit sich bringen oder?

Leider weiß ich jedoch nicht, wie ich dem Rom beibringen kann, dass es beim Einschalten des HD2 automatisch auch die zweite SD-EXT-Partion mountet und ich durch ändern des nos_injection-Scripts von

/cache/swapfile in: /sd-ext/swapfile oder eben /sdext2/swapfile dann das swapfile auf die zweite sd-ext-Partition verlegen kann.

Ich frage mich allerdings, wieso nos-injection überhaupt noch ein zusätzliches swapfile erstellt und was wird da "geswappt"? Das normale Swappen geht ja über die Extra-SWAP-Partition und mit extra-Swap-Script in init-d.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Canterbury:
Volume Button track advance

Evening,

Just installed and all seems running smoothly!

This is my second try with AOKP, first being not very enjoyable (and not this ROM)after running Nexus CM10.1 v2.3.

One issue i can't seem to locate to fix is the "next track, previous track" using the volume bar. -Hold down to advance track when screen off-

Worked by default on previous non AOKP roms with PowerAmp installed. (and other audio players).

Any help greatly appreciated.

Cheers
[General Questions and Answers] Class_of_punk26:
well tmobile now uses the 1900 mhz bands and im using a htc amaze now and have 4g in my area so does that mean ill get 4g on the htc one x+ or just edge speeds? thanks :)
[General Questions and Answers] Class_of_punk26:
I guess there is no answer to this or the answer might be too obvious maybe I should just buy a at&t phone and find out the only HTC one phones I saw on eBay doesn't come with a money back guarantee I'm guessing since T-Mobile updated to the 1900 MHz it will work well I'm bout to take a $700 dollar risk wish me luck :)
[Sprint HTC EVO 4G LTE] itscomptech:
ok so i have a sprint evo 4g flashed with flashtotalk to cricket. downloaded their messaging app for mms use. still glitchy. it is rooted and using viperrom. JB 4.1.1. i downloaded titanium backup and made the apn backup/restore program a system app thru titanium backup pro. i went and deleted apn settings in APN backup/restore and tried to restore a cricket mms apn xml file i had. it errored. i reset the phone. its never booted right since. the HTC white splash screen comes on and the vibrator doesnt turn off. just hangs. i turn off the phone and do the power+vol down to go into recovery. it hangs at the recovery screen the lists fastboot,recovery. etc. it does not allow vol up down or power to change anything. like its frozen. does not run a xxx75img check either. can not get into fastboot obviously to RUU. So what do i do? did like a NAND chip (emmc?) get corrupted that holds the fastboot/hboot firmware???
[Sprint HTC EVO 4G LTE] scottspa74:
Don't know anything about using other carriers, sorry. Consider this a bump, though, lol.
[Sprint HTC EVO 4G LTE] thicklizard:
Does your pc recognize it when plugged in?
[Sprint HTC EVO 4G LTE] itscomptech:
used to the first few times then nothing. turns out i was right about it being a board issue. i pulled the whole phone apart and did a reflow (heat gun both sides for several minutes) put it back together and it works like normal. obviously a break in solder somewhere.
[Sprint HTC EVO 4G LTE] scottspa74:
Damn. Good job :eek:;) Hats off to you. :thumbup:
[Nexus 4 Q&A, Help & Troubleshooting] ptrm2:
My data manager no longer stays on the second position in my notifications tray. It is not app specific as both data managers didn't do it. See in my screenshot the calender reminder appears above the data manager? Is there a way to make the data manager stay at the top?
[Nexus 4 Q&A, Help & Troubleshooting] S /\ M S U N G:
I don't think there's really an easy way to control that. I believe it's always newest to oldest from top to bottom in the notification tray.

Also, I think you forgot to attach your screenshot :)
[Samsung Galaxy Nexus] tiny4579:
This thread is dedicated to my CM10.1 builds that will be built whenever I get around to it which will be at least weekly.

When I build it, it's always synced to the latest CM source along with a few additional cherry picks that either add functionality or are bug fixes/improvements.

Download ROM

Use official gapps or one of the below gapps packages

If you want to use the CM camera, wipe /system and flash the ROM and these gapps:

http://mbqonxda.net/tiny4579/gnex/gapps-jb-20130301-no-camera.zip

*New* 7/19 gapps with updated camera and Play Store (based on 3/1)

http://mbqonxda.net/tiny4579/gnex/gapps-jb-20130719-TINY.zip

Mirror (thanks MBQ_ for hosting space):

http://mbqonxda.net/tiny4579/gnex/cm10.1

You can help MBQ_ with hosting costs by donating to him.

Features

CM10.1

Linaro optimizations and commits

Usually the latest Tinykernel, sometimes a pre-release

MIUI style Battery bar

Bugfixes and improvements from github and gerritt to dalvik including memory leak fixes

TODO

Add goo.im update support and instructions to github repo

Build Instructions

Check here if you're curious.
[Samsung Galaxy Nexus] tiny4579:
Flashing Instructions

A. Coming from a different ROM

1. Factory reset (recommended) - dalvik and cache is automatic here

2. Wipe system

3. Flash ROM and goo.im gapps

B. Coming from one of my previous builds or a CM10/CM10.1 nightly/unofficial.

1. Wipe dalvik and cache (standard recommendation)

2. Flash ROM
[Samsung Galaxy Nexus] tiny4579:
Mods / Fixes

None at the moment - camera working in latest build
[Samsung Galaxy Nexus] zoomy942:
Omg omg omg!
[Samsung Galaxy Nexus] djquick:
Weeeeeeeeeeeeeeeeeee
[Samsung Galaxy Nexus] klobkelosh:
Awesome tiny! Downloading!
[Samsung Galaxy Nexus] zoomy942:
Miui battery bar? I'm not sure I'm familiar with that

---------- Post added at 03:43 AM ---------- Previous post was at 03:07 AM ----------

Download page isn't working?
[Samsung Galaxy Nexus] klobkelosh:
Download link should be http://goo.im/devs/tiny4579/gnex/cm10.1

---------- Post added at 10:06 PM ---------- Previous post was at 09:51 PM ----------

Successfully installed and running. Will report back tomorrow. Thanks for this tiny!
[Samsung Galaxy Nexus] RTNDO128:
Are the Linaro builds any better/different than the official CM10.1 builds?
[Samsung Galaxy Nexus] a1exus:
May consider to come off stock Rom for this)
[Samsung Galaxy Nexus] MBQ_:
Which toolchain are you using bro? I kept getting errors when attempting to build with the linaro toolchain (13.01)
[Samsung Galaxy Nexus] tiny4579:
I'm on 13.03 but that's not the problem. Check the linaro rom thread in general for tips. Also I opted for loosethisskins build project instead of eug89 as I build cm and that has system environment variables that can be set to control some settings in the build.
[Samsung Galaxy Nexus] MBQ_:
Gotcha. Thanks bro.
[Samsung Galaxy Nexus] tiny4579:
Yeah the links were my bad. That's what happens when I start a thread when I'm tired. Its all fixed now.
[Samsung Galaxy Nexus] MBQ_:
Hahaha, been there before. I once messed up the build.prop because I almost think I drifted off into sleep as I typed... scary stuff ;p
[Samsung Galaxy Nexus] craigacgomez:
@tiny4579... thanks for this... I've been using TinyKernel for quite a while now... but I have a question about your CM10.1 build... What memory leak fixes did you include? I'm curious!
[Samsung Galaxy Nexus] klobkelosh:
Tiny, reporting in. I'm having terrible battery life. Just saw a massive draining wakelock that sucked my battery down in 1.5 hours. Odd thing, it was Google+ that held the lock, I've never seen that before. Same exact setup as I run on cm10.1 nightlies.
[Samsung Galaxy Nexus] tiny4579:
I was planning on adding more information about what I did but wanted to get the build up.
[Samsung Galaxy Nexus] tiny4579:
My battery life has been consistent. Reboot and see if you have the issue. It could have been stuck on syncing something. I never auto sync google+.

I think you answered your own question about the cause when you said Google+ held the wakelock.
[Samsung Galaxy Nexus] klobkelosh:
Yeah I'm chalking it up to coincidence, but wanted to put it out there unless there was some fix you may have implemented that would cause this.
[Samsung Galaxy Nexus] tiny4579:
I didn't have my fixes for camera with Linaro. I have those in now. I switched my build directory to build m7 and when I switched back to GNex I didn't have those commits in so it broke camera on 5/16. I wish I saw this before you guys started wiping or I'd say hold on I'll check it. Also the camera issue has nothing to do with the gallery app but rather a Linaro optimized libc that doesn't work right without some commits needed to fix the camera.

Also superwipe is silly and multiple wipes is just unneeded and just wears the flash out faster. If you guys can wait a bit I'm cranking out a build now.
[Samsung Galaxy Nexus] omniatic:
Didn't wipe anything yet...figured I'd wait and see if it was just a matter of swapping a lib file or something.

No rush...

Thanks,
[Samsung Galaxy Nexus] tiny4579:
I pushed up 5/17 to correct the camera FC issue. I've removed 5/16 from goo due to the camera issue. 5/16 should disappear from goo and 5/17 should be available now.

You could just push the libc.so from 5/6 to /system/lib but the pie improvements if you use pie make it worth updating. Personally I find it improved a lot as Pie is more integrated into the framework.
[Samsung Galaxy Nexus] gkaurin:
Thank you for the info on super wipe. I didn't want to wipe but when I did a clear cache I think I hit wrong tile in twrp and all was lost so I just went ahead with a clean. downloading now, Had a current TB so all went quick.

Thank you for the fast build and am glad it wasn't a crazy hard fix.
[Samsung Galaxy Nexus] tiny4579:
It's usually easy to fix things when you know what the problem was. The fact that I saw the same error from my first Linaro build indicated what I needed to do to address this.

I've updated the manifest files so for those that want to build Linaro based off of my builds can download them or check out the changes.
[Samsung Galaxy Nexus] gkaurin:
is it me or is goo just slow today?
[Samsung Galaxy Nexus] tiny4579:
It uploaded fairly quick but it could be slow on downloads.
[Samsung Galaxy Nexus] zoomy942:
I'm downloading it now. Will use with 4.0.1 new WiFi.

---------- Post added at 08:20 PM ---------- Previous post was at 07:41 PM ----------

Done. Downloaded a bit slow but goo.im is kinda like that.

I noticed CFQ was still default scheduler - that your preference?
[Samsung Galaxy Nexus] tiny4579:
I try to keep defaults. ROW might be better but CFQ is the default in the AOSP kernel.
[Samsung Galaxy Nexus] gkaurin:
Birty flash and working like a champ. Again thank you for the quick turn around.:good:
[Samsung Galaxy Nexus] zoomy942:
Flashed and ready. 350/1350 with cfq. Nice work. Really really great.

I saw you added deadline tweaks? Would that advantage it over cfq?
[Samsung Galaxy Nexus] zoomy942:
What black magic is this??

This ROM is indescribable. WOW
[Samsung Galaxy Nexus] zoomy942:
Still UI studder free!
[Samsung Galaxy Nexus] zoomy942:
Tried both and you are right. CFQ as default is smoothest. Tried deadline and it was fine but jumpy sometimes. CFQ stayed smooth. I'll try noop and SIO next.
[Samsung Galaxy Nexus] nitsua98:
I hate that stupid ui lag. It's been on all the ROMs I've used besides cm based and stock based. Idk if its that sysui mem leak or what but now I'm just sticking to cm.
[Samsung Galaxy Nexus] zoomy942:
For me this is the very first one that doesn't lag and studder
[Samsung Galaxy Nexus] Skyh:
I'm enjoying this version of CM very much.. except I still have the same issues with Spotify that I've always had with this Galaxy Nexus and CM, and apparently nobody else but me has -- the audio constantly pops and sputters and drives me insane.

I've done about as much Googling as I possibly can to avail, but recently came across this bit of changelog for some AOKP based ROM or something:

* Devices running alsa (everyone but Hero, Fire and Aurora/Elf with MultiUser kernel) can disable alsa standby by editing "snd.card.alsa.standby=1" to "snd.card.alsa.standby=0". This will fix latest Skype (and possibly other chat apps) issues, but may lead to some "pops" when the device enter/exit suspend.

Tiny (or anybody else), any idea if this is disabled on your build of CM? If so, any idea if I can modify it without a rebuild?

Thanks for any help/suggestions..
[Samsung Galaxy Nexus] laureanop:
Did you try increasing your screen off min cpu speed to 700 ?

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] Skyh:
Yeah, I've just about tried it all in that regard.

Heck, I even removed the limit and ran with the Performance governor and still no change whatsoever.

After trying out all the governors, schedulers, high frequency settings, etc, it's lead me to think there's something else going on (although that's also me thinking that Spotify couldn't possibly be struggling while I'm running at 1.2 GHz..)

So after lots of fruitless searching I came across the changelog bit above, and I'm hoping maybe there's something to it.

Thanks for the suggestion, though.
[Samsung Galaxy Nexus] laureanop:
ITiny after a weekend of Rom hopping the results came back the same as two weeks ago : even though most roms have adopted the 64 mb heap growth limit, straight cm and your cm are the only ones that don't suffer from home re draws ( 4-8 second re draws) after using ram intensive apps. Also os lag is at a minimum with cm, while the other straight aosp roms suffer from major os lag at times.

Any idea as to why that is ?

By the way the only additional options I enable on other roms are center clock with date and pm, and increased nav bar opacity

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
I don't have an idea on that sorry.

On the other mods, center clock is a messy cherry pick. For the nav bar opacity, do you mean brightness?

Also, a correction on above. I think you mean screen off maximum. You can't set screen off minimum without an app.
[Samsung Galaxy Nexus] tiny4579:
I didn't make any changes to this, and this is the first time I've heard of this option. If it's just a config file or build.prop edit then yes you should be able to modify it with a file editor and reboot.
[Samsung Galaxy Nexus] zoomy942:
We discussed that the latest version of this ROM had the CM kernel. Is it stock CM or Linaro build CM kernel?
[Samsung Galaxy Nexus] j0hnnyth3f0x:
Hey tiny, been using your kernels since you started them, usually with mmuzzy's builds but I had to try your cm build and I'm loving it! Smooth and quick, but I have a question for you or any of the other gurus here. Whenever I end a call, the screen stays black unless I push the power button. I didn't experience this on the official cm builds, but I ran their kernel too. Now I'm using your 4.0.1 old wifi kernel so I can use pgm. Would the pgm module cause this?

Sent from my Toro
[Samsung Galaxy Nexus] tiny4579:
Stock. It doesn't really make a difference anyway. Linaro doesn't build on CM's kernel.
[Samsung Galaxy Nexus] ATTACK:
I'm having the same problem. When I receive a call or end a call, the screen stays black/off until I press the power button. I just figured that it was a CM bug...
[Samsung Galaxy Nexus] tiny4579:
Possibly but I think I've run into it without pgm.
[Samsung Galaxy Nexus] MR H3LLMAN:
I didn't know linaro won't build on cm's kernel. May need to get at you privately about this but how did you get this working? Did you just add the stock kernel into your source instead?
[Samsung Galaxy Nexus] omniatic:
Maybe it's just me...I've tweaked the auto brightness settings a number of different ways, but it still doesn't seem to be working. Anyone else?

Aside from that, still running great. Any chance of an update build soon?
[Samsung Galaxy Nexus] tiny4579:
What's not working? I won't have time for a build this week. Maybe next.
[Samsung Galaxy Nexus] omniatic:
The brightness level doesn't appear to change with different light conditions. Tried adjusting the calibration settings, no change.

Like I said, maybe it's just me. I'll try some more adjusting and see what happens.

No rush on a new build, just thought I'd ask.

Thanks,
[Samsung Galaxy Nexus] tiny4579:
New build up! I figured it was long enough. It has the new custom brightness sensitivity as well as a few changes to PIE. This one features a linaro compiled CM kernel as well.
[Samsung Galaxy Nexus] cujo6801:
Ooo would like to try that kernel
[Samsung Galaxy Nexus] zoomy942:
What's the custom brightness you mentioned?
[Samsung Galaxy Nexus] tiny4579:
In auto brightness settings there is an option to select brightness sensitivity now.
[Samsung Galaxy Nexus] zoomy942:
Thank you. I'll try it here in a bit
[Samsung Galaxy Nexus] un4givn85:
what cm build is this based on?

is there any benefit, besides the linaro optimizations, to switching from cm10.1 RC4?
[Samsung Galaxy Nexus] tiny4579:
Battery bar. And it's built from CM at the moment it's built. If tiff don't care for either of that stay on the official build.
[Samsung Galaxy Nexus] nitsua98:
Yes!!! CRT disable! Too bad it doesn't fade.
[Samsung Galaxy Nexus] zoomy942:
Holy crap!!!
[Samsung Galaxy Nexus] tiny4579:
Yeah, I wish they added this thing while my Galaxy Nexus was still my daily driver. This animation was a lot better in 4.1 but turning it off in 4.2 helps quickness turning off the screen a lot and it never worked well on 4.2.

By the way, there's a new build up. I wouldn't have uploaded it but I decided to tackle a Linaro 4.8 build and this one is successful. Let me know if there are any issues. The kernel is compiled with the Linaro 4.7 toolchain (stock CM kernel with a patch to make it work with Linaro.
[Samsung Galaxy Nexus] nitsua98:
Dang goo is so slow and the download keeps dropping
[Samsung Galaxy Nexus] sruel3216:
Not using ur kernel?
[Samsung Galaxy Nexus] tiny4579:
Nope, I decided to make it more universal and the kernel version I was using had the WiFi drivers that don't work on WEP. This decision was spawned by the tethering issue in one build and from there I decided to keep it stock and people could flash the kernel they wanted.
[Samsung Galaxy Nexus] zoomy942:
Installed. Will update later.

---------- Post added at 02:05 AM ---------- Previous post was at 01:57 AM ----------

So with the linaro based kernel is it more up to date versus your tiny kernel?
[Samsung Galaxy Nexus] tiny4579:
My kernel is built with Linaro. The one in the Rom is stock cm.
[Samsung Galaxy Nexus] zoomy942:
Okay. I misread your post about kernel being built with linaro this time.
[Samsung Galaxy Nexus] tiny4579:
No it is with the Linaro toolchain but there are no other changes. Not sure what you mean by up to date.
[Samsung Galaxy Nexus] zoomy942:
Sorry for the confusion.

I just meant some kind of linaro build that is in the ROM.

But I see now. Linaro ROM then flash your seperate linaro based kernel.
[Samsung Galaxy Nexus] tiny4579:
The kernel in the ROM is built with linaro but it's CMs kernel. If you want a different kernel you need to flash it separately.
[Samsung Galaxy Nexus] zoomy942:
Thank you.

I have it installed and using your kernel as well with stock speeds. Will report back.

I love auto brightness settings and no CRT option.
[Samsung Galaxy Nexus] zoomy942:
I've looked all over to enable the battery bar but am coming up blank.
[Samsung Galaxy Nexus] omniatic:
I've still got it, probably because I did a flashover. But you are right, it's not an option in the settings/system/status bar anymore.
[Samsung Galaxy Nexus] tiny4579:
Yeah, the settings part didn't get built in the last build. Next build should have it in settings. If you need it, flash the first build then add it then dirty flash the second build. You can even dirty flash the first build and enable it then dirty flash the second build after setting it up.
[Samsung Galaxy Nexus] zoomy942:
I don't mind waiting for the next one.
[Samsung Galaxy Nexus] zoomy942:
I might give the older version a try and dirty flash to the newer to get the battery bar.
[Samsung Galaxy Nexus] zoomy942:
Anyway or feature that could be added to hide the WiFi indicator?
[Samsung Galaxy Nexus] tiny4579:
Use expanded desktop.