yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] jbbandos:
XPART!

Now, thanks (again) to xavierjohn22, here is my first XPART ROM. XPART is a Data2SD variant that is reputed to be fast and stable.

You can use it wih one FAT32 and one ext3/4 partition, as A2SD, but the recommended fastest setup is one FAT32, one large ext4 (for your data partition), one smaller ext4 (cache), and a swap partition. I'm not that much of a fan of a swap partition, as I am always afraid it will wear out the SD card precociously, but most people report it working well.

There is a great howto by docmjldds in Rods ROM thread.

Just remember, XPART isn't as widely used as A2SD, and might be less mature. As always, I take no responsibility for any problems.

Ah, and I'll keep doing the A2SD ROMs, my aim is to make these two very similar, only differing in the specific scripts.
[Nexus One Android Development] MR_EVIL:
X part....wooooow jbbandos the real game begins on Nexus one.......

i was waiting for this to happen since a long time........thanks xavierjohn22 n jbbandos ......downloading it
[Nexus One Android Development] hughey2k2:
Thanks I'm going to try it myself right now.
[Nexus One Android Development] jbbandos:
First impressions with XPART:

1st boot, with only a single ext4 partition, everything fast and smooth. However, I made the mistake of restoring the system settings with MIUI backup, and then wondered why Titanium couldn't get root. Decided to try the 4 partitions setup (FAT, 1GB ext4, 200MB ext4, 128MB swap). Then I found out it seems like the restore of system settings messes up Titanium (no idea why), so another 5 full wipes and reflash.

Now, with 4 parts, the first boot had FCs like crazy, and some icons were missing from the desktop. Opened a terminal, su, ran fix_permissions, and hot booted - FCs gone, but since the desktop was still missing stuff I juts wiped the "Launcher" data in Titanium.

Result - seems very fast, very smooth. Will restore all my 130 apps to see how it goes...

Edit: the problems with Titanium were because I restored the backup I had made with MIUI backup over the one I disponibilize with the ROM. I wiped the data with the applications manager, and now Titanium works.
[Nexus One Android Development] MR_EVIL:
can u pls upload it on mediafire links...
[Nexus One Android Development] ultra99:
hmm, great initiative!! might try it.. :)
[Nexus One Android Development] jbbandos:
I have a slow ADSL - it takes me over 30 minutes to send it to multiupload, and another 30 to send to the ROM Manager server (when it doesn't give a cache error and makes me start the upload again). Maybe someone else can upload it for you?
[Nexus One Android Development] ultra99:
i can help out....tell me what you want me to do?
[Nexus One Android Development] jbbandos:
Sunil1981 wanted a mediafire link for my ROMs, and I don't have the time to upload them there now, can any of you guys do it?

Thanks!
[Nexus One Android Development] MR_EVIL:
wooooooooow it is just amazing rom xpart is very smooth........
[Nexus One Android Development] Guineapig:
voip issue

Hi,

I have 2 phones with the same setup for voip, one on cm7 and one on this rom.

I can make calls with the built in voip client over 3g for both but i cannot receive calls over 3g on this rom. But if i turn wifi on it works perfectly fine.

Thanks!
[Nexus One Android Development] jbbandos:
I don't have a way to test this right now, as I don't receive voip calls and don't have a voip incoming number. Anyway, I'll check the framework settings to see if there is a setting to allow incoming voip over 3g, as there is for outgoing.

In the meantime, why don't you try a client like CSipSimple? I'm using that one after getting fed up with the limitations of the internal client.
[Nexus One Android Development] Guineapig:
I'm going to try Csipsimple tomorrow. Thanks!
[Nexus One Android Development] DEADover:
About XPART Version - after the installation of several programs, i decided to move dalvik cache to ext with A2SDGUI and during reboot - stuck on X screen :(

Wiping the dalvik cache and cache did not help - reinstalling the rom now...

Update: Or it makes no sense to transfer dalvik cache to ext because internal memory=sd-ext with XPART?
[Nexus One Android Development] jbbandos:
Reminder to self: remove/disable the a2sd script on next xpart version.

You're right, it makes no sense to transfer dalvik to ext, precisely because now your data partition is mapped to your first ext partition. And since dalvik, by default, is on the data partition, it is already on ext. I wonder what did the a2sd script, probably deleted most stuff from the data/first ext partition.
[Nexus One Android Development] DEADover:
TB (3.8.7 Pro) can't restore backupped apps (only apps, without data) in batch - progress bar stucked at 0 and nothing happened...

Update: It was TB bug (maybe)...after reboot it works. Sorry :)
[Nexus One Android Development] jbbandos:
Same version here... Did you by any chance backup using encryption? I've given up on it for now, after I found out that some times it gives that exact behaviour (stays forever at 0%, be it restoring or verifying) and sometimes FCs. I now do all my backups without encryption and verify them afterwards.

Try the previous backup of the app that is hanging, or restoring a different app.

Another problem with TB Pro, is that if you tell it to sync to market you need to have already added your google account and have accepted the market disclaimer before being able to restore.
[Nexus One Android Development] DEADover:
Finally after TB restored all my apps - notification bar disappeared (reboot did not help) and a large number of applications give me FC's or can't be execute....arghhhhh! :mad:

Reinstalling ROM now...FTW! :D

PS And no - I don't use encryption in TB.
[Nexus One Android Development] jbbandos:
Ouch... Well, for me the XPART only worked well after three reboots and one reinstall. I recall that docmjdds used to advise wiping 5 times, installing, booting, letting it sit for a while, rebooting again, and if there were no FCs to start restoring, but only apps. I managed to restore apps+data after the second install, but one thing I did make sure is that all ext4 partitions and the fat32 partitions were mounted, by opening a terminal and running "mount", before restoring anything. If the partitions weren't all mounted, either waited or did another reboot.
[Nexus One Android Development] jbbandos:
Class 10 is made for long continuous writes or reads, and sucks for short bursts; also, class 10 cards seem almost to use a volatile cache, and are a lot more prone to corruption when you reboot your phone or the card gets reset - which happened a lot with the class 10, at least from looking at the logs, and never happens with the class 4.

Finally, the class 10 card heated a lot! With the class 4 the phone temperature stays normal, with the class 10 it was clearly hot, and was easy to pinpoint the card position.

Besides, my Sandisk class 4 shows better read speed and almost the same write speed as my Patriot class 10 on all tests. And with the Sandisk I never have corrupted backups with Titanium, or FCs with XPART

Check around, the impact of journaling on the life of your card is something like a few minutes less on a decades life span. I am using ext4, and the XPART scripts convert your ext partition to ext4 automatically.
[Nexus One Android Development] ocujos:
Check out this in-phone micro SD card test results. eg. Sandisk 8GB Class 2 outperforms Lexar 16GB Class 6!!! It's an eye-opener!

Sandisk Class 4 (32Gb in particular) random read/write performance is better than any other card on the market. As most apps and data on Xpart ROM are located on the ext partition, random read/write performance is very important as the phone constantly reads/writes to "internal" flash (ie. EXT partition).

Also worth noting is that Sandisk never released a 32Gb class 6 card for a good reason: their class 4 card performs better than many class 6 cards eg. my (now dead) Lexar Class 6, 16Gb card is slower than Sandisk 32Gb class 4!
[Nexus One Android Development] malavan:
market fc on A2SD 1.10.23 .
[Nexus One Android Development] jbbandos:
Known bug (on google side) when you're not in an English speaking country but have set your language to English. Switch to the local/SIM language, open market, then you can switch back to English.

It has been discussed on this thread a few times already.
[Nexus One Android Development] ocujos:
I've been exploring various ROM/Call recorder software combos for a while now. The only one that I've found to work reliably is CM7.1 stable + Wildmonks kernel + CallRecorder 1.0.38 Alpha.

CallRecorder 1.0.38 unfortunately doesn't work on QND MIUI 1.9.16 with Wildmonks kernel. Has anyone got CallRecorder working on QND MIUI?

QND MIUI is my prefered ROM. Unfortunately, I have to stick with CM7.1 until MIUI works with CallRecorder.
[Nexus One Android Development] jbbandos:
What happens with Callrecorder and MIUI? Did you try now that the MIUI devs have changed the way call recording is handled by the superuser tool?
[Nexus One Android Development] ocujos:
On 1.9.16 there is just silence in recorded audio. I will re-test this on 1.10.28 QND MIUI when it comes out.
[Nexus One Android Development] Atento:
Does the wildmonks kernel support 2 way call recording on CM7? I am trying to find a way to do it in N1, but I just find out that the Miui rom does it.
[Nexus One Android Development] ocujos:
As per my previous post: yes. You need CallRecorder 1.0.38 Alpha.

Please note that unlike other apps out there, CallRecorder records the audio stream from both parties: ie. it doesn't need speaker to be turned on! There is one thing that can be enhanced: my voice volume is bit low compared to other party.
[Nexus One Android Development] pseudoheld:
having a strange new issue. happened a few time so far but again this morning.

i was browsing my newsfeeds and then suddenly the app just shut down.

also the tasker icon dissapeared from my statusbar meaning that shut down too.

the phone however stayed on and responsive and i could launch apps again and after about 10 seconds tasker restarted itself aswell.

here is the log of it happening:

http://pastebin.com/9xurEuug

maybe you can have a look!
[Nexus One Android Development] jbbandos:
Hi guys,

I've just released 1.10.28, so enjoy it. I've finally found a old bug on the XPART scripts, and with that fixed you can now wipe dalvik-cache both in 4Ext and CWM recoveries without entering a boot loop at restart.

Have fun!
[Nexus One Android Development] jbbandos:
Strange... I couldn't find anything that would explain why your browser disappears after a visit to androidpolice.
[Nexus One Android Development] jbbandos:
Attention, it seems that the "sharing to facebook" bug (image deleted when sharing from the gallery to facebook) is still present in this MIUI version. So either use an alternative gallery, or share to google plus, email, anything but facebook.
[Nexus One Android Development] xavierjohn22:
yeah use quickpic or something in market. my wife just hit me with the tab. her picture disappeared the other day. wahaha.

Sent from SGT running MIUI
[Nexus One Android Development] jbbandos:
Ouch... :)

At least my wife's Blade is still without a MIUI version (being an ARMv6 CPU), so I don't have the risk of having that happen to me...
[Nexus One Android Development] pseudoheld:
well as i said it ain't just the browser. it seems to be EVERY RUNNING application that just terminates.

i'm thinking it might have to do with low memory. maybe my rss reader (feeldy) overloads the memory and then the lowmemory settings start reacting and killing off apps...?! just guessing ;)
[Nexus One Android Development] jbbandos:
Could be, as the rss reader is filling the log. If one app is active and "hogging" memory, the android task manager will start killing others.
[Nexus One Android Development] MaDInDy:
Can I wipe cache+dalvik cache and update from 1.10.23 to 1.10.28 via 4EXT 2.2.7 RC5 ?

Thanks. :D
[Nexus One Android Development] jbbandos:
I've tested that a few times with XPART, to make sure I had fixed the boot loop bug... :)

In fact, you should always wipe dalvik when upgrading. Until now that only worked with Amon Ra's, now you should have no problems with 4EXT and CWM
[Nexus One Android Development] ocujos:
I can confirm that wiping cache/dalvik in 4ext no longer causes boot loop (or in my case "stuck" X sign). 4ext is by far the best recovery on N1.
[Nexus One Android Development] MaDInDy:
Now, I updated to 1.10.28 and no issue.

Thanks. :D
[Nexus One Android Development] Pochemuchka1977:
Hi,

Can you please elaborate a little more about "vold mod, to allow fast usb transfers again (please test)" ?

Thanks
[Nexus One Android Development] doitmyself:
XPART 1.0.28 works smooth and stable!Nice work!:D

Only a little EXT space recognition error:

But "MIUI XJ D2EXT X-PART 1.10.28 - 2.3.7 GS 3P FINAL" is correctly identified the EXT space on Desire.

http://xdaforums.com/showthread.php?t=957291，
[Nexus One Android Development] pseudoheld:
i think its a mod that was made for Cyanogen and JB cooked it into the Miui rom.

lots of people were having abismal transfer speeds when connecting their phone via usb cable. i for one was getting about 100kb/s as transfer speed. after jb added the modification i am now getting 6mb/s.

just check your usb transfer and report back if you are getting good or bad speeds.
[Nexus One Android Development] jbbandos:
Basically, the vold in MIUI and CM7 has a bug that makes USB transfers slow, and the one I am using brings back 3-4Mbps transfers when mounting the N1 sdcard on a PC.
[Nexus One Android Development] jbbandos:
That is to be expected - the xpart script I'm using is different than the one XJ uses, mine mounts loop filesystems on top of the ext partition for extra speed and reliability, so it probably confuses MIUI space checks.
[Nexus One Android Development] thatguyzx:
Instead of removing the sidekick app, just place GoogleSearch.apk from the market in your system/apps, and reboot. This way GoogleSearch overrides search button, and your sidekick multitasking still works. I use root explorer, I'm sure you can do the same with adb.

If there was any way to get stock multitask instead of sidekick, that would be great. Sidekick takes a while to pop up on my phone. So much that it's faster to launch from home. Perhaps I'll try 3rd party tasking apps.
[Nexus One Android Development] timmoty_g:
Hi JB,

With the recent build, newer than 1.9.16, I always have problem with the SQLITE.

After trying and troubleshooting, it appears that my sdcard partitions (along with the scripts in init.d) caused the problem.

My sdcard (kingston class 10) was partitioned into 3, SWAP (128MB), EXT4 (2048MB) and FAT32 on the rest of space.

The scripts in init.d of 1.9.16 skips the SWAP partition (I somehow think the SWAP never really works) and correctly mounted the EXT4 as the Internal Storage, I checked this through "df -h" command from Terminal Emulator.

However, the init.d scripts of newer ROM versions (upto 1.10.28) would reformat the 128MB SWAP partition to EXT4 and mounted as /data/data, and the ROM would use this partition as "data storage" of users' installed apps, which of course it gets filled up very fast. Again, I checked this using "df -h" command in the terminal emulator.

So I reformat my sdcard into just 2 partition (4GB EXT4 and FAT32 for the rest) and up to now still no sqlite problem. I've checked the mounted parition using "df -h" and all looked good, there's only 1 /data partition (the EXT4 partition).

I'll monitor this and will feedback to you in few more days.

Thanks and regards,

Timmoty
[Nexus One Android Development] jbbandos:
Hi Timmoty,

The idea with having a second ext partition is to have the applications data (/data/data) there, so as to reduce corruption risk while not affecting the speed. For this end, in Rod's original version journaling was turned on only for the second ext partition. After looking around and testing a bit I ended up enabling journaling also for the first partition, as it had a very negligible effect (read: non-mensurable) on speed.

Right now the only advantage of having the second ext partition is to have data writes separated, to a smaller partition, having a higher probability of being all committed if there is a reboot or a shutdown.

Having said all that, your problems might also be related to having a class 10 card. I propose a test - if you have titanium backup pro, try backing up all your apps, then verify all of them. If any fails verification - time to change the card to a class 4 Sandisk, like I did.
[Nexus One Android Development] k3vink3vin:
I found that SOME animated buttons are slow, for example the brightness slider and all ON/OFF switches in Settings, which is very unresponsive. It's been like that since it first booted, and it is not limited to Settings. Scrolling is fine though.

Is this happening to me only?

running a newly installed 1.10.28 XPART build with WM kernel
[Nexus One Android Development] timmoty_g:
I think it's better to stay off WM kernel for this version, I also found it to cause the rom to be unstable.

Regards,

Timmoty
[Nexus One Android Development] k3vink3vin:
Just wiped dalvik-cache and flashed intersectraven's kernel, didn't resolve the problem. Setting Animation to Off didn't help either.

While dragging on sliders (such as Brightness in Settings), the phone gets laggy :confused:

Other than that I didn't encounter any issue, very smooth overall, with both IR's and WM's kernels. Except some apps take longer than usual to start, eg. WhatsApp may take up to 5 seconds.

Thanks for trying to help :)
[Nexus One Android Development] ocujos:
There is also Pershoot kernel you may want to try. It's one of the best kernels for N1.
[Nexus One Android Development] k3vink3vin:
Wiped dalvik-cache and flashed, didn't solve the problem either...

So I guess it's only me? :(:(

Might as well try flashing the whole thing again.. and the A2SD version too..

Thanks for trying to help :)
[Nexus One Android Development] ocujos:
I've just installed 1.10.28 XPART (again). I first did a full wipe in 4EXT recovery before flashing. The old camera bug is still present on this ROM: when Autofocus is enabled and Auto Flash (default), camera never turns the flash for the first photo. 2nd and subsequent photos turn the flash on.

This is a deal-breaker for me. Sorry, but I can't use this ROM until camera (flash) bug is fixed. CM7.1 does not have this problem.
[Nexus One Android Development] k3vink3vin:
Wiped all and flashed Xpart version, no joy.

And flashing the A2SD version fixed it :D

Turns out my sdcard prefers A2SD

Now my only wish is that I can convert from Xpart to A2SD without wiping, which may not be something straight forward...
[Nexus One Android Development] timmoty_g:
Hi ocujos,

I personally don't have issue with the camera flash, it's working as expected.

With auto focus, however, I noticed that I have to wait till it finished focusing, only then the flash will get triggered automatically.

Regards,

Timmoty

---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------

How many partitions are you using?

What is the speed and brand of your sdcard?

I use Kingston class 10 with only two paritition (Fat32 and EXT4) so far so good.
[Nexus One Android Development] ocujos:
I don't understand this: I do a 3x full wipe in 4EXT recovery, do the install, then install Wildmonks kernel and then reboot. As soon as I enable auto-focus, the very first shot is without flash (I take photo in a totally dark room, so flash must come on).

Which kernel are you using Timmoty? WM kernel is the only thing different from a standard QND XPART ROM on my N1.
[Nexus One Android Development] doitmyself:
Can you re-upload QND-MIUI-MULTI-XPART-1.9.16?

Thanks.
[Nexus One Android Development] jbbandos:
Here you go:

http://www.multiupload.com/WMTIF671BV
[Nexus One Android Development] jbbandos:
Don't even try converting from Xpart to A2SD or vice versa. It's a lot easier, safer and faster just to wipe and reinstall.

What SD card do you have?
[Nexus One Android Development] k3vink3vin:
Two partitions (same as yours).

It is a Toshiba 4gb class 4 for your record.

I actually prefer using A2SD as there is more control on what to move to the sdcard. Now I have the apps folder and dalvik-cache on my sdcard, while leaving /data/data in internal storage.
[Nexus One Android Development] jbbandos:
A class 4 card should work with Xpart (but my Kingston 8GB class 4 didn't), but for that small amount of storage you're indeed better with A2SD.
[Nexus One Android Development] doitmyself:
Here is the MiUi official stable(2.3.x) version download link. It's not same as the dev-builds(1.x.x).

For some reason it's not public, I'm thinking perhaps this might be useful to you.

http://bigota.d.miui.com/2.3.5b/miui_NexusOne_2.3.5b_dbytx30ouo_2.3.zip

http://bigota.d.miui.com/2.3.7a/miui-ota-bravo-2.3.5b-2.3.7a-x5p0hw0f.zip

Thanks again for all your hard work.
[Nexus One Android Development] jbbandos:
1.11.4 up, so have fun!

PS: Anyone knows how to get fastweb Italy to install the ADSL line I've asked over a month ago? :)
[Nexus One Android Development] :
For those of us with broken power buttons (or would prefer) the Vol-skip instead of the 4-way reboot menu is there anyway to switch this?
[Nexus One Android Development] jbbandos:
You can flash the zip from the first post here. As my problem is the opposite (vol-down is starting to fail), I don't have much use any more for the Vol-skip mod, so I'll choose the 4-way whenever I can't include both.
[Nexus One Android Development] :
Thank you, I did notice it on the credits you gave but was unsure if it was still useable as this is the first (or will be) MIUI rom I've tried as not long had my N1. Appreciate your time answering.
[Nexus One Android Development] net.cat:
Did u call them? Usually in italy we are preatty fast to catch moneys!
[Nexus One Android Development] jbbandos:
:)

They claim there is some sort of technical problem, so my guess is that telecom is giving trouble...
[Nexus One Android Development] net.cat:
Really strange ... LOL Telecom damn them!! :P
[Nexus One Android Development] ocujos:
Every time I install a new QND MIUI XPART ROM i get the same problem: when Auto focus is enabled in camera, flash fails to fire on the first shot! I've had this problem with the last 3, 4 ROMs. I just can't believe I'm the only one with this problem!? Sure you guys use your N1's in the dark and take some photos? This is so annoying as I have to use CM7.1 which is not my preferred ROM (but is the one where camera works as expected).

I have a 32Gb Sandisk Class 4 card with two partitions 1.1Gb EXT4 and reminder FAT32. Before I flash the ROM in 4EXT recovery I do a full wipe 3 times. When the phone boots for the first time, I open camera, change Focus to Auto and then take a photo in a dark place (yes, I usually flash ROMs at night :) )

Default flash setting is Auto, so I leave than alone. The very first shot fails to activate the flash. I can easily reproduce this problem at any time.

CM7.1 on the other hand consistently behaves as it should: under same circumstances it fires the flash.
[Nexus One Android Development] walliester:
it happens to me, sometimes i just always have on ....
[Nexus One Android Development] timmoty_g:
Hi ocujos,

I did tried using WM kernel and experienced the same thing you've described, the flash went alternative on then off then on again then off again and so on...

I'm testing it by taking a series of pictures in total darkness.

But when I change back to default kernel, it was smooth, the flash always fired as expected.

Regards,

Timmoty