yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Trialz Nexus One:
This ROM is solid and stable. Everything I need works. The incoming caller ID double photo is there but I never thought it was a bug but actually by design. The fore image is sharp while it shows a larger blurred image as background. I like this so if it is a bug, Mr Fuzz if you change this, give us who like this an option to retain this format for caller ID.

When new ROM is released I just backup existing ROM, wipe dalvik + cache, install the update, install the gapps and reboot. The configurations remain from the previous install. I have not done a full wipe since trying this ROM in December 2012.
[Nexus One Android Development] Trialz Nexus One:
Improved incall ui! Really enjoying the update. See screenshot below.

I am using Ice10 theme by Bhupatib.
[Nexus One Android Development] FuZZ__:
Set contact photo in high res will remove double photo, but if in low res the double photo appears as effect and large photo is blurred.
[Nexus One Android Development] FuZZ__:
ROM updated! check out changelog on OP...featured new weather widget,enjoy!
[Nexus One Android Development] Trialz Nexus One:
I am really liking the lock screen weather widget changes.
[Nexus One Android Development] Cabronbr:
chache size and ohter

i know the the hboot partitions must be 220 for system but what about cache the others?

thanks
[Nexus One Android Development] 350Rocket:
Deleted, figured it out. A little bit confusing rom, and had to replace the mms.apk because it didn't list the messages in order, but it's probably the fastest rom I've had on this. I've been using Jellybean for the past 3-4 months though. Just tried CM7.2 again and then this.
[Nexus One Android Development] iRAY:
I've just switched to update-CyanMobile-eXperience-N1-20130123-Release.zip (called 2.3.8) ROM from CM 7.2.0.

A few notes:

1) Settings - CyanogenMod - Performance - Scrolling cache - must be set to ALWAYS DISABLED (it is a common error, CM7 is also affected - otherwise scrolling is choppy if any transparent theme is used)

2) (SOLVED) Click on any contact in Contacts = force close (editing works fine) (tried to use CM7 Contacts.apk and ContactsProvider.apk and it works fine then) => resetting Contacts storage and re-syncing helped)

3) Settings - CyanogenMod - Display - Turn-off-screen animation has no effect (it does not work)

4) SD-EXT is not mounted some times on boot, using Link2SD now (Mount2SD did not work properly for me)

Any suggestions? :)
[Nexus One Android Development] iRAY:
Anybody else is experiencing issue no. 3?
[Nexus One Android Development] FuZZ__:
1) already Force enabled on our github

3) WIP.It doesn't work on all adreno 200 devices for now since our sf is totally different from CM7.

4) don't use any a2sd script... we already has native a2sd so it could breaks some.
[Nexus One Android Development] 350Rocket:
Mounts2sd is working here. Native a2sd didn't work on first boot. Can't remember exactly what happened I had to mess around before I could get it to work but its working fine now.
[Nexus One Android Development] FuZZ__:
ROM updated,enjoy :)
[Nexus One Android Development] iRAY:
Thank you for replies and thanks for new update! I'm gonna try it soon!

The reason why I'm not using built-in A2SD is that 2nd partition was not mounted some times (have no idea why) and the other reason is that when using Link2SD I can see and filter what was linked, what is on SD card etc. Built-in app manager does not support it.
[Nexus One Android Development] Trialz Nexus One:
To use Mounts2SD app, you first have to enable the "Mount SD-ext on boot" option in Settings, Development. If this is not done, prepare for some grief.:)

I have been using Mounts2SD for some time; are there any pointers on using a2sd in this ROM? Would love to use what is already in the ROM rather than installing and using another app.
[Nexus One Android Development] FuZZ__:
Is there any clue when it fails? such as boot sequence log would be appreciated.
[Nexus One Android Development] iRAY:
I'm sorry I can not provide any log for this. I just updated to the latest ROM build and I've managed to work Mounts2SD (there was a lot of playing because of previously linked files by Link2SD).

New ROM is very nice. There are big improvements in settings. Thanks!

Currently I'm experiencing only two issues:

1) When display goes off, phone shortly vibrate (and after few seconds it starts to vibrate again for a very long time). Solved by disabling Haptic feedback (hope I'm translating it right) in options for touch keys etc (however I like vibration for touch keys :) ).

2) There is a problem with font. Some symbols are not properly displayed (running Czech locale/language). You can see it, for example, when you are choosing in Fb app if you want to see "Most recent" or "Most important" news (check it out you will see what symbol I mean). But this is just a very tiny issue :)

Thank you for all your hard work!!!
[Nexus One Android Development] FuZZ__:
alright,at least Mounts2SD doesn't break anything,it would be okay.

about your issues: Well,we've recognized both of them.something went wrong with Haptic feedback after recent Activity Manager changes,still investigating. Fortunatelly HOME/SEARCH keys works fine,just get weird feedback when you tap that.Tha't why now Haptic feedback default disabled,out temporarily solution :o

about fonts...I get what you mean.Have you already tried various fonts available in interfacce tweaks? use robot solved my language(Japanese) issues but maybe need to be tested on various locales and support more fonts?
[Nexus One Android Development] iRAY:
Yep. Changing the font helped. I just love the default one and not Robot :)))) That thing with Haptic is fine. I just wanted to let you know about it.

Btw animation when display turn off is still not working properly I think (some times there is an animation and sometimes not... and sometimes I see this animation when I wake up my phone).

Btw2 when display turn off and I try immediately wake up phone, nothing happen. Must wait few seconds. Have no idea whats wrong.

Just a tiny note: search button works differently to stock/CM7 ROMs. It should carry out app specific action or general Google search otherwise. Now it is doing nothing when there is no specific action in app (I know it is possible to setup app for this button but then app specific actions are override and do not work).

Again, thanks for all your help and work!!! This is for sure the best ROM for N1 (for daily use). It will just take a time to get rid of all issues because it is pretty complex ROM!
[Nexus One Android Development] gregferns:
Hi guys, anybody know how to disable the pie ?
[Nexus One Android Development] FuZZ__:
uh,currently there is no way to disable it except enable navigation bar.
[Nexus One Android Development] gregferns:
Thanks fuzz, ok by notification bar do you mean the one where there are settings for soft touch buttons?

All in all the Rom is much smoother now than when I had tried it earlier. Also, if there is no possibility to disable pie can we add apps to it or other stuff like in lmt app?

Thanks

Greg
[Nexus One Android Development] zagzag99:
You can't disable, but you can drag it to change it's gravity location to the sides or the top edge of the screen, so you won't trigger it when sliding your finger from bottom up.
[Nexus One Android Development] FuZZ__:
yeah,that's it :) just realized enable navigation bar and set visibility to disable can hide both of them.
[Nexus One Android Development] iRAY:
It seems I've just discovered a new bug. Lock screen is not displayed some times (or multiple times in series when waking up). I will try some lock screen app replacement to see if it'll fix the problem.

Update: This problem is with Lock screen style "Circles". Now running "JB (Rings)" and it works fine so far.
[Nexus One Android Development] iRAY:
Another bug: when you open up Market app and select some installed App then when you press "Open" button Market force close/crash. And if you click notification of newly installed app nothing happen but app is installed fine (can be caused by Mounts2SD? Can anyone else test? I have "app", "dalvik-cache" and "cache" folders moved to SD card).
[Nexus One Android Development] gregferns:
Hi there,

I have the same setup as you with Mounts2SD and i get the same force close on apps in the play store,

but not the other bug of notifications.

greg

---------- Post added at 07:39 AM ---------- Previous post was at 07:27 AM ----------

Yes, this works,,,, both nav bar and the pie are disabled.

In fact i wanted to disable it to use LMT pie and gestures....

@fuzz - To improve on the pie function i think you should check out the below thread on LMT

http://xdaforums.com/showthread.php?t=1330150
[Nexus One Android Development] gregferns:
Icon name problem

An issue --

Please see the screen shot attached :

How can i get the ICON NAME to show up properly, right now it is like SQUEEZED...

thanks

greg
[Nexus One Android Development] gregferns:
@fuzz.

Can you pls see the attached screenshot?

See the download notification, the progress bar is merging with the text above it.

Can you tell me what needs to be done to rectify it?

Thanks

Greg
[Nexus One Android Development] iRAY:
The same issue here.
[Nexus One Android Development] iRAY:
I solved that issue with fonts and symbols.

I've compared all CyanMobile font files with CM 7.2 N1 nightly and there was a difference in size of DroidSansFallback.ttf file (the one in CyanMobile is much smaller). I've copied this file from CM7 and all works fine.
[Nexus One Android Development] iRAY:
I've tried to run with m2sd.disable_cache_folders = 1 (Disable cache folders for market and packagemanager) but still keep crashing.
[Nexus One Android Development] gregferns:
I would say better provide @fuzz with a logcat and let him have a look, till then I think you continue using as you are...
[Nexus One Android Development] iRAY:
The problem is there is nothing in log... Market just crash (not force close).
[Nexus One Android Development] FuZZ__:
Verified.Looks good to me, approved :good:

---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------

dude, first revert to stock built-in a2sd then issues persist give me a logcat. :)
[Nexus One Android Development] iRAY:
Such action does not make a sense. If issue will persist, it means log will be still totally empty ;)
[Nexus One Android Development] iRAY:
Regarding Market crash: today I've found out that it does not crash in all cases. For example opening Boat Browser is fine but when try to open AdAway Market app crash. Both apps are on SD-EXT since app, dalvik-cache and cache folders are on SD-EXT.

---------- Post added at 07:09 PM ---------- Previous post was at 06:18 PM ----------

AdAway is working because it was moved to SD-CARD (FAT32) so it is definitely something related to Mounts2SD.

---------- Post added at 07:28 PM ---------- Previous post was at 07:09 PM ----------

UPDATE: AdAway is NOT working because is moved to SD-CARD (FAT32). Apps on SD-EXT can open via Market with no problems.
[Nexus One Android Development] iRAY:
Okay so after further testing. Market crash is not related where App is placed. It seems it crashes when you try to open app which contains some libraries no matter on storage (SD CARD, SD-EXT, Internal).

Can anyone else try to reproduce? (you need an app with libs and then press Open button in the Market app)
[Nexus One Android Development] FuZZ__:
I told you REVERT TO STOCK A2SD... furthermore, you've been warned don't use any a2sd scripts.case closed :eek:
[Nexus One Android Development] iRAY:
You didn't get it. Please read it again. I'm experiencing this issue no matter on Mounts2SD, built-in A2SD or with no SD-EXT at all (it means this problem is still there when clean CyanMobile ROM is loaded and SD Card is removed). Hope it is clear now.
[Nexus One Android Development] FuZZ__:
Then you needn't reported such as "something related to Mounts2SD",could led someone to wrong direction.

And why you haven't posted logcat yet even though I asked for? report without it do no help,just in case you don't know what is like debugging.

---------- Post added at 08:16 PM ---------- Previous post was at 07:52 PM ----------

uploaded new build,enjoy improved Pie controls ;)

---------- Post added at 08:56 PM ---------- Previous post was at 08:16 PM ----------

just took a logcat,this is a same issue related to intent woes we've recognized possibly causes by recent big ActivityManager changes.

Still investigating but might take times...hold :)
[Nexus One Android Development] iRAY:
Thank you for new ROM update! :)

I'm sorry for my reports. They were confusing I know. I just wanted to let you know asap and sending multiple messages wasn't an attempt to make it more urgent :)

The problem with logcat is that log is totally empty. I mean completely. Simply nothing. Hard to believe I know... I also know no logcat = no fix so I will try to play with that more.
[Nexus One Android Development] FuZZ__:
Ah,I got it.I thought that's weird there are no log when something FC's... hmm,but adb working just fine?

BTW, now we've found possible causes that issues.I will release new build when verified actually fixed it.
[Nexus One Android Development] iRAY:
Yep. There is nothing in a log (Market simply crash). adb is probably working but have no idea how it can be useful (maybe I look a little bit skilled but I just have 10+ year experience with running a linux, not android). If you can point to some directions I can try to do it.
[Nexus One Android Development] iRAY:
It seems like I've found another issue (maybe more easily reproducible): If I try to open any document via Google Drive App it always fail (no force close, no crash but dialog informing loading has failed, then if I re-try with Try again button it just return to documents list after few seconds).
[Nexus One Android Development] FuZZ__:
What happen when type "adb devices" in terminal?

Have you configured your environment? http://wiki.cyanogenmod.org/w/Doc:_sdk_intro
[Nexus One Android Development] Trialz Nexus One:
Hi Guys...was facing the same issue with the market force closing when trying to open an app from within market after installation or update of an app was completed. I backed up my installation, full wipe all but the sd card, then restored the backup. Force close on market no longer happening.

---------- Post added at 08:27 PM ---------- Previous post was at 07:48 PM ----------

Was premature...market force closing still for some apps. Sorry for the above post
[Nexus One Android Development] iRAY:
Good to hear because I've had to switch back to CM7.2 nightlies so I can not provide info anymore. I've played a lot with that but no luck, no log :(
[Nexus One Android Development] iRAY:
And I want to correct something because previously I reported it wrong.

That switch in Settings - CyanogenMod - Performance - Scrolling cache - must be set to ALWAYS DISABLED (previously I said ALWAYS ENABLED what is in CM7 by default and it is wrong). It probably means then there is everything ok in CyanMobile since as far as I remember it is set by default to Always disabled.
[Nexus One Android Development] FuZZ__:
eh,wat?? Lol

But it's okay,we've changed default value not because you had requested but that's our decision...

Anyway,it's just set as default.user can make a choice if they doesn't like it :)
[Nexus One Android Development] FuZZ__:
new build uploaded,fix some bug... enjoy :)
[Nexus One Android Development] Trialz Nexus One:
Nice update Fuzz...no FC when opening app within android market.
[Nexus One Android Development] FuZZ__:
just uploaded new build.lots of bug fixes and new features...have fun :)
[Nexus One Android Development] gregferns:
Oh boy. I just installed freshly the latest build. Can I install over it? Do I need to wipe dalvik +cache?
[Nexus One Android Development] FuZZ__:
wat? Do always wipe dalvik and cache...that won't wipe your data :)
[Nexus One Android Development] Trialz Nexus One:
I have updated and so far so good. I have not played with the pie as yet and will do so later.
[Nexus One Android Development] gregferns:
I wiped dalvik and cache but many of my apps are not showing and all settings are gone. I use mounts2sd with data, apps and all cache in sd-ext as I have too many apps. I can't use the in built a2sd as it gives no space errors.
[Nexus One Android Development] FuZZ__:
hmm,doing it wrong always??
[Nexus One Android Development] Trialz Nexus One:
I can answer or attempt to answer this one for you Fuzz as I am using mounts2sd...

When updating, you wipe the dalvik and cache, apply the update, flash gapps, flash mounts2sd zip from dk zero thread then reboot.

What he can try is just reflashing the gapps and then mounts2sd and reboot.

I hope rule number one is followed....ALWAYS back up previous Rom before updating.

:)
[Nexus One Android Development] gregferns:
Yes , rule no 1 is always followed.... :)

But I got it right. Reinstalled m2sd selected my config and rebooted. It optimized all the apps and everything is ok now.

Am only facing one issue home button is not responding.

Thanks trialz... by the way if you flash directly dkzero's , do you get all, I mean data, apps, cache and dalvik on sd-ext?
[Nexus One Android Development] Trialz Nexus One:
Hi...there is plenty advice on DKZero's thread so we should not hijack Fuzz's CyanMobileX one with this. So here is what I do quickly:

Just go to the M2SD app, then menu and settings...ensure that the Configure Busybox and Install Script are both done and have green ticks. If not, just click each and they will do their thing. Next go to Configure. the options I tick are applications, Dalvik and Cache; Swap Partition (but only do this if you have a swap partition defined), and File System Check. Exit M2SD and reboot the phone...

That works for me.
[Nexus One Android Development] gregferns:
Thanks. I won't hijack this thread any more but just a word, what you replied was not what I had asked.

Anybody know how to disable persistent Google search bar on desktop home screens?
[Nexus One Android Development] FuZZ__:
Now I tottaly don't see your problem...just dispose it do no help? :eek:
[Nexus One Android Development] gregferns:
It's ok. Forget it. Sorry.

I solved it....
[Nexus One Android Development] impactor:
There is no "Not Working Part". Should I then assume EVERYTHING works?
[Nexus One Android Development] ertoalb:
Hey Fuzz_ this is a great rom, pretty much everything works, but I'm having an issue, I'm trying to download a large apk (50mb+) from play store but it fails because the download goes to cache partition, the rom have something to link the download dir to the SD card? Something like:

adb shell
# cd /cache/
# rm -R download
# mkdir /mnt/sdcard/marketcache
# ln -s /mnt/sdcard/marketcache download
# chown -h system.cache download
[Nexus One Android Development] FuZZ__:
Sorry but I don't think it does work.

---------- Post added at 03:51 PM ---------- Previous post was at 03:51 PM ----------

just uploaded new build.

We've switched to LegacyLauncher since ADW Launcher has been deprecated...so requires full wipe,enjoy! ;)
[Nexus One Android Development] masantula:
Been using CM 7 and think need a change so trying this ROM, looks promising...

Will update if i run into any issues, which i doubt. Thanks again

EDIT:

I have to say this ROM has got to be the best ROM i have ever used, from the bootloader to the interface, it truely is amazing, i love it. Just what i was looking for, having the stability of GB and the features and interface of JB. Awesome. Hats off :)
[Nexus One Android Development] FuZZ__:
ROM updated,have fun! :cool:
[Nexus One Android Development] gregferns:
I am on your rom the one before this.

Is it ok to just wipe dalvik + cache??

Because i see some commits in the changelog..

thanks

greg
[Nexus One Android Development] masantula:
This might be a silly question but I don't see an icon for picking up or dropping a phone call. Got two phone Calls and I tried to press everything, all soft keys but couldn't work it.
[Nexus One Android Development] gregferns:
The same issue here. But a workaround is to press menu key to answer the call. And you can try to use back key to end the call.
[Nexus One Android Development] gregferns:
I have another problem. If i restore apps with titanium my home button stops working. I thought titanium may be the problem, but i just installed latest version without any wipes over the previous version. All apps are ok after reinstalling mounts2sd but the home button doesn't work.

Any ideas?

Greg
[Nexus One Android Development] masantula:
Sweet, thanks. That worked. Shh relief. Lop.. great
[Nexus One Android Development] gregferns:
OK, The correct solution to this is as below :

Settings -- CyanMobile Settings -- Calls -- Disable or UNTICK ----- BACK BUTTON END CALL and MENU BUTTON ANSWER CALL

and TIck or select ALLOW INCALL UI TOUCH.

This will bring back the "NORMAL" option of slider to answer or reject. Try it, it worked for me.

Hit the thanks button if i helped you !!!! Cheers :)
[Nexus One Android Development] FuZZ__:
If you already on LegacyLauncher,it's fine.

---------- Post added at 11:54 PM ---------- Previous post was at 11:45 PM ----------

never have had such a issue but at least you should do a wipe cache and dalvik before flashing.

What kind of apps you had restored via Titanium backup? restore system apps might be introduced issues like you having.
[Nexus One Android Development] gregferns:
Anyway, i did a full wipe and so far no problems.

thanks @fuzz, good build...
[Nexus One Android Development] masantula:
That Worked for me, appreciate it :)
[Nexus One Android Development] gregferns:
In fact, try keeping all 3 ticked. That way can use all of them during calls.... :)
[Nexus One Android Development] Trialz Nexus One:
Hi All...is anyone experiencing FCs with im+ and Tunein Radio with the latest build 20130225074019?
[Nexus One Android Development] FuZZ__:
on startup? uh,already fixed up some breaks on last build, hope should be fixed on next build ;)
[Nexus One Android Development] Trialz Nexus One:
FCs was on startup of the apps. Testing the new build now...20130301193556
[Nexus One Android Development] Trialz Nexus One:
Hmm...I did a full wipe. Google Play

now FC. I installed tune in radio from backed up apk and it runs fine. Did not load anymore apps as this was not possible given Google play issue. I will try once more on the weekend.
[Nexus One Android Development] FuZZ__:
You are doing something wrong.if you're using any a2sd script,please stop using it.