yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] thrik:
Trying to get some help with M2SD?

I'm a complete noob to A2SD, luckily it was extremely easy within Samuaz' ROM (with iA2SD), all I had to do there was reboot after flashing it.

Here it seems a bit more complicated, and although I have 1 GB ext4, I keep on running out of space.

:\

Any suggestions on what I should do? I understand M2SD can be configured in the Terminal, but I'm not sure what commands to run...
[Nexus One Android Development] pconwell:
I'm still getting the "/cache cannot download" error with the new update. I enabled m2sd cache, but it didn't seem to fix the issue.

Anyone else seeing this still? Or is there a workaround I missed somewhere?
[Nexus One Android Development] uoY_redruM:
Is there a way to add the "Favorites" folder? It was automatically there with first boot on Medroid but I never did figure out how to actually create one...

Pictures attached show what I mean:

EDIT- Won't let me attach two photos but its a little folder at the bottom right that expands when clicked.
[Nexus One Android Development] cpm:
Just drop your icons on top of each other and it'll create a folder for you. You can then give the folder a name e.g. Favorites
[Nexus One Android Development] uoY_redruM:
Oh, cool, thank you.
[Nexus One Android Development] uw748:
Does the current CM9 include the CM7 option to customize menu/search button behavior? Because I currently need them to trigger tasker tasks in temasek CM7 kang.

Thanks in advance
[Nexus One Android Development] :
Had the same issues, no gps lock yet gps app showed 12 sats running. also had no data connection when trying maps. i pulled sim and played around till it worked--not sure what fixed it--if fixed permanently? ICS wont let you restore apns with my apn restore app. Network showed simple selected not epc.tmo apns and i can't view them. also with this rom unlike cm7, with same maps version, voice doesn't give name of street to turn on, just says turn--don't see why rom would effect that. Will test battery tonite/tomorrrow, i just flashed over last version.

Loving this rom am going to try the beta chrome also

Ken
[Nexus One Android Development] cpm:
Doesn't look like it. As far as I know CM9 is said to offer less configurable options, as CM7 was deemed to have too many!
[Nexus One Android Development] iakughan:
when the phone is charging heats. reaches about 40° C

Inviato dal mio Nexus One con Tapatalk 2
[Nexus One Android Development] fegato:
Is flash player working in your browser?

mine isn't.. I mean I don't remember if it's normal for this rom or I should have messed up somethin?

THANKS

edit: OK actually I messed up something.. Solved
[Nexus One Android Development] dk_zero-cool:
Not sure. Read that it replaces framework parts (Services.jar). I'm not gonna include something that touches the original files of the ROM. Something goes wrong with this, I am the one getting massive amounts of bug reports on something I have nothing to do with. It's the same as it was with the CM9 Reloaded Mod which was not included for the very same reasons.

Edit:

But post a link and I will have a look at it.
[Nexus One Android Development] PSeeCO:
And it comes to be a really well known bug that affects many users...sorry dk ^^
[Nexus One Android Development] MoeNeXus:
Did I mention that I had a problem with swype?

Sent from my Nexus One
[Nexus One Android Development] ctfrommn:
Ive had nothing but problems modifying the services.jar file to use that script. I would definitely vote against doing so. I had issues with programs no longer working, home and menu buttons not working, wifi lost....way to much trouble for the very minimal gains...if anything I would like to see the start up tweaks implemented in zyr3x's implementation of AOKP...those actually helped.
[Nexus One Android Development] PSeeCO:
Stop now, you're scaring me!!! :eek:
[Nexus One Android Development] ctfrommn:
Is easily reversible, I just dont see any benefit to outway all the side effects.
[Nexus One Android Development] wollac11:
Yes I think it might require a modification to the services.jar file. I can see why you might not want to include but many users have reported very good performance gains from using it. Perhaps it could be offered as an option in aroma with a disclaimer included?

Anyway it can be found here: http://xdaforums.com/showthread.php?p=16635544

I personally would like to see it included but respect your decision should you decide against it. Thanks for such a prompt reply and for building this amazing ROM.
[Nexus One Android Development] dk_zero-cool:
Well don't have to look at the script to know that I am never going to include this. I have never been the big fan of rules and this guy is setting way to many of them. It is to much about credits and attention, and to little about the actual script.
[Nexus One Android Development] wollac11:
Okay yeah that's fair enough. How about the startup tweaks that ctfrommn mentioned earlier instead?
[Nexus One Android Development] dk_zero-cool:
They sounds interesting enough to take a look at
[Nexus One Android Development] ctfrommn:
The more I look at them, I think most have already been integrated into the last few builds...but anything that helps is good I guess.
[Nexus One Android Development] npiper05:
What number to use in the US?

I'm hoping to get Wifi tether working and I live in the US. What should I set this number to?

Thanks
[Nexus One Android Development] time_shock:
The original is set to 11.. some of us live in areas where there can be up to 2 additional channels, which make 13

The numbers 11 and 13 don't refer to the exact channel used, it's just the total number of channels available in your region.

If you use wifi tether i don't think you'll need to change this. This usually affects those of us who have our routers set to channel 12 or 13 but the phone's original setting has it limited to 11.
[Nexus One Android Development] cAnArdtichAud:
stuck in boot

Hi all,

I've resized successfully with blacRose my N1 stock 2.3.6.

wiped dalvik cache, then installed the last full rom using CWM recovery.

The install goes ok, I don't choose the Mount2SD script coz I already use Link2SD.

But the device is booting and booting and booting and never giving the hand back.

I tried the RC6 update 1 and the result is the same.

Any clues to help me ? FYI my SD is partitioned for Link2SD. I think the prob is somewhere else though
[Nexus One Android Development] cpm:
Try using 4ext recovery instead. Use it to re-partition your SD card.

I'd be very confident this will fix your issue :)
[Nexus One Android Development] ai6908:
Where are you stuck at? At animation or before animation? If it is before animation, then your sd card partition might be wrong. Try partitioning with 4ext recovery, that is the best out there.
[Nexus One Android Development] jrs007:
when I try to see some videos it gives error.
[Nexus One Android Development] Kibb:
Did you format your sd-ext?
[Nexus One Android Development] johnnydvc:
Hi,

I have installed the latest version of this rom and it's very good, huge work done here! Thank you! :)

But the only issue here is the video recording which is very slow, on recording and watching (almost useless for me), tried stock and shakey kernels but the same behavior on both, video playback doesnt work (as expected because of camera fix) but with mx player ist's ok.

Is there any way to fix video recording to be smooth (any option or something) ?

(did a clean install)

Thanks in advance.
[Nexus One Android Development] Melkizedek:
Do I need to wipe something before doing an update from the previous version?

Thanks
[Nexus One Android Development] XeloOw:
Yep , just cache and Dalvik Cache
[Nexus One Android Development] djmfxp:
freez on boot splash!

[/COLOR]

OK

i remove battery 2 more times, and boot device correctly

BUT

display dont turn back on after power off device
[Nexus One Android Development] cAnArdtichAud:
Thx,

as my Ext (partionned via cmw) contained all my moved apps (link2sd), I did'nt want to format it ! Link2sd allows me to relink the partition and have all the apps reinstall on a fresh ROM.

Nevertheless, I tryed the RC6 upd0 and it worked!! ..Strange..

I've bought EXT4 and have reformatted my Ext coz Link2sd finally couldn't recognize it.

The /sdcard is not formatted with EXT4 but it works, no more stuck on boot during the animation.

I fear to use another update of your rom since this one works, I don't know why.
[Nexus One Android Development] AndyBurns:
I keep seeing people recommend doing wipes of cache and dalvik when upgrading between BCM releases, yet as far as I can tell the aroma installer

does these wipes for you

... or am I wrong?
[Nexus One Android Development] dk_zero-cool:
That is correct, but I have given up trying to explain that to people :)
[Nexus One Android Development] Melkizedek:
Thanks all for the explanations, in fact I asked because I thought that the update function that I saw in the Aroma installer could do the necessary operations.

Anyway... I tried now and from the actual 3.6 update 1 version it denies me the update, strange!

With a new install (without -manually- cleaning anything) it seems to work.
[Nexus One Android Development] cpm:
This will continue to happen. But don't despair. It's simply due to a growing user base for your rom DK. New users will ask such questions, and those who have been using it longer will help them along. Nature of the beast, and proof of growing popularity :thumbup:
[Nexus One Android Development] ai6908:
If they read the message that is displayed during installation, they probably would have figured it out by now...;):D
[Nexus One Android Development] net.cat:
Hi guys! I comming back to this ROM and since some things changed, I'd like to know which kernel performs better: BCM or the shaky's one?

thanks in advance ;)
[Nexus One Android Development] r1enh:
Monkeyrunner

Monkeyrunner tool from the sdk doesnt work with this rom... it works with aokp from zyrex..

Can you meaby have a look at it dk?
[Nexus One Android Development] clustered:
how I could make the notification drawer will lock when the screen is in lock mode.. sometimes in pocket, trackball woke up the device and the notification drawer scroll and did enable/disable what I don't want... thanks for your advise..
[Nexus One Android Development] raist1976:
Just disable the trackball wake ... :) I find it quite annoying.

Only reason people want trackball wake is when they broke their power button ...

You'll find the setting at the bottom of Display settings.

---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------

I find that the phone is quite stable with BCM.

Had problems when using shaky's kernel ... but maybe unrelated because since then I reinstalled 3.7U0 from scratch (before updated from 3.5)

---------- Post added at 11:19 AM ---------- Previous post was at 11:18 AM ----------

Same as the 3x wiping helping getting better results ... urban legends are still strong :)
[Nexus One Android Development] masantula:
If you select the fix during the installation than video playback breaks. Use MX player. Works great. Its on Android market. Free version is available.
[Nexus One Android Development] masantula:
I've had better performance and zero issues with shaky's kernel with governor set to smartassV2
[Nexus One Android Development] masantula:
Instead of disabling trackball unlock, change your lockscreen to password or pattern. This will prevent the notification drop down in lockscreen. So even if trackball gets pressed no issue
[Nexus One Android Development] clustered:
Just disable the trackball wake ... :) I find it quite annoying. Only reason people want trackball wake is when they broke their power button ... You'll find the setting at the bottom of Display settings

Yes.. my power button is broken, that why I really need trackball wake..

---------- Post added at 06:35 PM ---------- Previous post was at 06:06 PM ----------

thanks for your advise.. it works when using passwd or pattern... hope could works for slide too...
[Nexus One Android Development] dk_zero-cool:
I like it because I hate where the power button is placed which is not broken. I like Sweep2wake on my one x for the same reason ;)
[Nexus One Android Development] ctfrommn:
Stock BCM....no contest...shaky's is a bit of a battery hog.
[Nexus One Android Development] johnnydvc:
+1 for stock bcm, at least here in my little experience it performs better with better battery life too.

Any thoughts on video camera recording? On my phone the recorded videos are like frame by frame, very laggy. Watched on pc and it's the same. Just curious because I've read on some posts that it was smooth.

Thanks.
[Nexus One Android Development] ~semsem~:
+2
[Nexus One Android Development] xyrovice:
Great work on all the recent updates DK.

Quick question regarding something I saw in the changelog:

I see it says you added a script that powers down the CPU to a "powersafe" (powersa

v

e?) CPU governor when the screen is off. Does this mean we no longer need to add a screen-off profile in SetCPU/ROM Toolbox? Is this active regardless of what governor we choose (currently using lagfree and it's working like a charm).

Thanks again for all the work brother.
[Nexus One Android Development] ai6908:
Been running 7.0 for about 3 days, and so far so good. No major concerns including battery life and performance, based on stock installation.

I did notice that "Vibrate and Ring" gets disables when switching sound profiles. Is that a common thing with android, or is it an issue with ROM?
[Nexus One Android Development] raist1976:
I guess preferences is subject to the user :) I find the power button ideal where it is on the nexus one. For example on the HTC sensation of my wife, the power button is on the top right and I find it not easy to activate... but maybe because I'm used to my nexus one ;)

More seriously, I hate trackball wake beause in a pocket or in a bag it will wake the phone very often ... not wise for the battery...
[Nexus One Android Development] dk_zero-cool:
The script will change it to powersave when the screen turns on, and back to whatever governor you used when the screen turn on. This along with the governor CM option in Settings, you don't need SetCPU.

And I have added this and more scripts as option in Aroma for the next build, so people who do not like it, can uncheck it during install :)
[Nexus One Android Development] Mogomra:
I keep getting the error described here about the "parse error." I'm thinking it's probably because I'm using the Chrome Beta as my browser. Has anyone figured out a work around for this?
[Nexus One Android Development] LeoLeal:
+3
[Nexus One Android Development] cpm:
As a matter of interest, if you're using SmartassV2, it was my understanding that a screen off profile wasn't required anyhow, as SAv2 sleeps at the minimum frequency anyhow.

Of course built in powersave mode would be more useful if using other governors like OnDemand.

Since I always use SAv2 I've been using just the CM7/9 performance settings and haven't used setcpu since.

Would I be right in my understanding?
[Nexus One Android Development] CrustyMcLovin:
Had the same issue... Only way I found to get it working was to restore from my titanium backup. I had a backup of both Swype and Swype Installer. I restored both and then had to run the Swype Installer to register Swype again. Once I did that everything worked fine.
[Nexus One Android Development] Kibb:
SmartAssV2 sleeps at 384Mhz and not the minimum set frequency, which means that if you set the minimum to 128Mhz, it will still work between 128Mhz and 384Mhz. With PowerSave, it sleeps at the minimum frequency set. So if you set the minimum to 128Mhz it sleeps only at 128Mhz.

If your minimum frequency is 384Mhz or higher, having powerSave doesn't make a difference, it works the same way as SmartAssV2.

The issues mentioned above about crappy music playback are when the minimum frequency is set to a low value like 128Mhz, which is not enough to perform both music playback, cell and wifi standby as well as any other task.
[Nexus One Android Development] Dukas:
Tethering solution

After been upset for awhile not able to use the tethering I finally found solution.

https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether

is working perfectly on RC3.7U0 build.
[Nexus One Android Development] Kibb:
WiFi Hotspot works fine for me
[Nexus One Android Development] Dukas:
Is looks fine (at least on my device) but no external device (iPad, laptop, etc.) was able to connect.
[Nexus One Android Development] newhere:
can i have this rom without using blackrose or any partitioning tool??
[Nexus One Android Development] cpm:
No.
[Nexus One Android Development] Atermoon:
I really don't get people who are ready to flash a ROM without even reading the first post. :confused:
[Nexus One Android Development] newhere:
i have read the post "This ROM needs at least 180mb on the /system partition. You can use BlackRose to re-partition your internal nand" but i don't really know if it is A MUST or not

I donno what is the size of the system partition on a nexus one
[Nexus One Android Development] n1newbie:
default system partition is 145. so it makes blackrose a MUST :)
[Nexus One Android Development] newhere:
Ok thank you so much :)
[Nexus One Android Development] Mogomra:
That sucks. I don't have a TB backup for Swype since I've always had more luck just installing from the beta installer.

e: I even pushed the stock browser, and removed the Chrome Beta via ADB, and had no luck. Wonder what the deal is.
[Nexus One Android Development] louyaorong:
It seems HTML5 video on stock browser is broken. Anyone notice it?
[Nexus One Android Development] cpm:
Actually after doing some more research I have to question the info you have provided - please correct me if I'm wrong.

Smartass (v1) was I believe limited to 384MHz minimum during screen off.

SmartassV2 however lowers itself to whatever value is specified in the system file sleep_ideal_freq. Looking at the value of this currently shows 245000, which equates to 245MHz min during sleep.

Now, Shakys kernel allows 128MHz, so perhaps we need to ask the obvious question. What if sleep_ideal_freq is set to 128000? Will that provide better screen off battery saving for SmartassV2?
[Nexus One Android Development] xyrovice:
I don't mean to interject but I'd figure I'd share this before I hit the hay:

In theory this does provide better battery savings, and I've never dealt with SoD's when bottoming the freq's out for a screen off profile (ie 128mhz min/245 max was never a problem for me...not 100% sure about 128/128).

A RECENT PERSONAL FINDING of mine, though, that might be important to some:

Using Shaky's Kernel with the latest update (3.7?) I did basically what I've always done regarding CPU set up, except I

did not

make a screen off profile as I'm under the impression one is already scripted into the ROM. My set up at the time of the finding (pretty simple): 128 min/1036 max using the lagfree governor.

The problem

: I was playing music stored on my SD card through Google Play Music. I found that, when turning the screen off (and therefore activating the powersave/min freq script) the music became VERY laggy. The phone woke without any lag and raising the minimum freq to 3xx mhz (forget the exact number...next step up though as Shaky's doesn't seem to have a slot for a 245 mhz freq) fixed the problem.

Thus, it became clear to be that limiting the min freq to 128 might not be beneficial/optimal under certain circumstances. For example, navigation type applications may suffer as well as music playback. Just a thought/warning.

FWIW I have since flashed the stock BCM kernel after my only hot reboot for weeks on Shaky's. Weird moment where I searched my phone for a contact and went to filter the (stock/default/google?) search app's results to only show contacts. It froze and hot rebooted. Haven't tried again.

I would like to therefore pose a couple of recommendations, as well as a couple requests actually:

Rec's:

1) Besides SoD's, be aware of decreased performance when lowering min/max freq's (specifically for "screen-off" profile type situations).

2) The best config I've found is (if the kernel freq's allow it) to set your screen-off profile to 128 min/ 245 max. This allows for the greatest battery savings while still giving the CPU some room to work.

Requests (Kernel related):

1) I don't know if Shaky might be reading this, but I want to point out that I think the freq table for the kernel of his that's included is flawed: for me, the bottom two notches are BOTH 128 mhz. It then goes straight of to 3xx mhz (384?). There is no 245. All I'd ask that be passed on is that Shaky rectify the freq table to bring back the 245mhz frequency.

2) If it's possible, DK, I know one luxurious aspect of a high end kernel is a plethora of governor options. I personally have found myself missing the lazy governor sorely as it's always been my personal fave. If it's not too much trouble, maybe we could get a couple more? I know smartassv2 is crucial and therefore present, but it's always nice to have options. Thanks in advance.

Lastly, Thanks for all your hard work on the ROM!!
[Nexus One Android Development] ai6908:
I agree with your findings here 100%. However, having very low CPU speed causing SOD has been an issue from good old WM days. Our devices just cant handle below certain CPU speed.

Personally I am using 384 cpu speed with smartass, and i dont see any decrease in battery life.
[Nexus One Android Development] Kannibalism:
im using the same as you and i cant complain either :P
[Nexus One Android Development] cpm:
Perhaps this isn't quite true? Each Nexus One has its own tolerance at each end of the scale. So some can handle 128MHz minimum with no issues, whilst others suffer from deep sleep SOD. Ditto for maximum MHz.

Personally I've never had a problem with 128Mhz.

Its only through trial and error that you get to know your own little Nexy ;)
[Nexus One Android Development] dk_zero-cool:
Update is out. I finally got the USB Tethering fully working (Without any hacks). I will play with the MTP later.
[Nexus One Android Development] uoY_redruM:
Can you do a simple update from 3.7?

I'm back on the N1, my Galaxy Nexus was stolen from work on Thursday by a temp labor worker :(

At least you're still developing here!
[Nexus One Android Development] Kannibalism:
great update mate making the video camera work has improved :)

EDIT: Added BCM Boot Annimation (By @EverSonny) my bootanimation is still the CM9 one :P
[Nexus One Android Development] kurt.gomez:
yeah... the new update is great... awesome work dk :D

btw... those of you having problems with swype... this is not a ROM specific issue... the new BETA package gives a parse error for many other users... i had the original ICS beta of swype backed up with TB so all i did was restore and the run the update from swype settings...

this is a known issue and this is what the app developers have to say on the swype forums

""""

Notice: Although this issue is currently affecting some Swype Beta users, our priorities are set on releasing new versions of Swype. This means the beta version and bugs within it likely won't get much attention until the next iteration, which we'll have an announcement about very soon.

If you are getting the parsing error when trying to install the Swype Beta, it's recommended that you follow the steps below:

1. Remove all Swype Beta-related APKs from your device.

2. Ensure a stable connection (preferably WiFi).

3. Re-download and run the Swype Beta Installer (here is the link to the Swype Beta Installer: http://beta.swype.com/android/get/).

Many users have found that simply waiting for a few hours and trying again at a later point in time works.

""""
[Nexus One Android Development] Nato154:
wipe cache for update or full wipe for clean install?
[Nexus One Android Development] dk_zero-cool:
The installer, as always, will handle cache, dalvik and the system partition. As for full wipe, I don't know. Try without, if you get issues then do full wipe.
[Nexus One Android Development] Nato154:
Thanks for the help :D