yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] MoeNeXus:
Coz China is its birthplace :D

Sent from my Nexus One
[Nexus One Android Development] jbbandos:
MIUI is developed in China. Its sponsors now have even released a phone - check xiaomi.com for the phone, miui.com for the ROM in Chinese and English.
[Nexus One Android Development] Wylker:
Well thanks for the responses, I was worried I was connecting to the wrong content servers or something. Anyway this mod is really cool, it's a little "iphone-y" but I think I just need to get used to not having an app drawer. The speed is great and using Wildmonk's kernel I'm getting battery life comparable to CM. Really nice work!
[Nexus One Android Development] eidros:
Any mirror site?

Hi, I am having serious problem downloading the latest update from where I am. Never had problem before. Is there a mirror site that I can try to download from?

Finally got the the update downloaded!
[Nexus One Android Development] eidros:
N1 behaving strange!!!

Hi guys, I really need help on what to do next!

I successfully flashed one of the MIUI 4.0.3 ICS ROM a couple of weeks back just to try it out :( It was so so but the camera was not working that I decided to come back to QND MIUI.

However, when I reflashed (with a full wipe X5 times and formating system, data and boot) I started having lots of FC and the performance was sluggish, especially stock messaging app. I get more FC's after making or receiving a voice call. Miss calls are not saved and I cannot inout new contacts. Avatars in my messaging app keeps disappearing or flashing, etc etc, you guys get the idea :(

I tried wipping clean, formatting with every update, right up to this latest one 2.3.9 but still the problem is there. I keep fixing permission and wiping cache/dalvik and reinstalling but all in vain :(

I decided to start over;

1. Copied my SD card on my laptop and backup using TBP

2. Using 4EXT, full wipe, clear caches, format system, data, boot and sd-ext.

3. Remove the SD card and reformatted using the SDFormatter.

4. Installed, repartition using 4EXT; 1024 ext 4 and the rest Fat 32. I have a 16 MB SD card class 4.

5. Reflashed 2.3.9, booted and copied the SD card content and using TBPro reinstalled apps.

5. Sadly, same problem.

I am out of ideas, what to do next! I like to think the N1 is not dead. I was not having any problem prior to flashing the MIUI ICS ROM :(

Need help please!
[Nexus One Android Development] net.cat:
Did u restored the proper hboot config?
[Nexus One Android Development] eidros:
I did not change my hboot with blackrose, if that is what you mean? I used the MIUI.us 4.0.3 ICS mod that did not require a new hboot. Would it still corrupt my hboot?

Running info in 4EXT recovery, this is what my N1 is showing;

system size: 145.0 MiB and 1.2 MiB free

data size: 196.2 MiB and 105.0 MiB free

cache size: 95.0 MiB and 88.2 MiB free

is this normal?
[Nexus One Android Development] jbbandos:
If you install the QND XPART+Odex version, you need a bigger system partition.Which one did you install?
[Nexus One Android Development] eidros:
Hi Jose,

I always install the XPART regular version of your rom. However, since net.cat suggested in an earlier post, the 'hboot reconfig idea', it sent me on a search for this topic. I have upgraded my hboot to 0.35.0017, wipe cache and dalvik and re flashed your XPART 2.3.9. Now it appears that the FC's have gone and the UI are smooth again :)

Let see what happens when I take an incoming call :)

[Edit] My N1 is behaving normally now when taking and receiving calls :) The MIUI messaging app is still occasionally giving an FC but I have rebooted again to see if that will settle the code :)

[Edit] So what happend to my hboot when I flashed the MIUI ICS rom? Did it change it or reconfigured it?
[Nexus One Android Development] eidros:
Thank you for this idea. it sent me searching for 'hboot reconfig' and stumbled on an upgrade note. I did not realize that my N1 was on an older version. So I flashed the upgrade and that did the magic, brought my N1 back to normal life :)

So BIG thank you once again for the suggestion.
[Nexus One Android Development] jbbandos:
Glad that it works now! As to what happened when you flashed the ICS ROM, I have no idea...
[Nexus One Android Development] petran07:
Hello

I have some problems WITH MY PHONE

I dropped down and when OPENS MY DOING ALMOST STRAIGHT reboot In all TI ROM MIUI

THE KYANOGEN 7 I have no problems WHAT TO DO;
[Nexus One Android Development] Androidity3000:
Please take the time to convert your comment to English so we can understand your problem and possibly help you. Thanks bro.

I have the XPART ROM and it runs absolutely perfect. This is the longest I have ever been on one ROM. No reboots, freezes, etc. for me.
[Nexus One Android Development] walliester:
hey jb,I was browsing around for my friend lg optimus,and I found on another forum this mod for beats on all gingerbread 2.3.x and all I could say is wow,it does work 100% was thinking if you could or try to put it in your ROM,

ok here is the, link http://xdaforums.com/showthread.php?p=23143266
[Nexus One Android Development] jbbandos:
Seems like you read my mind... I tried to add this last week and it would boot loop, maybe yesterday’s version will work. I'll give it a try!
[Nexus One Android Development] petran07:
Hello I have about 5 months the Roma habits and I am very pleased

3 days ago but I dropped the phone and since then can not work on the Roma can only M7

What can I do;
[Nexus One Android Development] jbbandos:
From what I understand your phone no longer works with MIUI after being dropped, but still works with CM7? Try removing and re-inserting the uSD card, and as a last resort re-partition and re-format it using 4EXT recovery. Probably it is only the uSD that is giving contact problems.
[Nexus One Android Development] petran07:
I did that you told me but I have the same problem

What else can I do;
[Nexus One Android Development] johnnydvc:
Hi,

I'm having some problems in my phone on latest's releases of xpart odexed version.

The phone runs great with good performance, but sometimes I start getting fc's from google framework and a bunch of apps (ex: keyboard, facebook etc..), for example 4ext updater tells that there's no space on /data or no root previlege, but if i try to "su" on terminal it works fine, so no root problem i think, and there's 70% of space free on /data (BR 220/16/200), about updating busybox i think this rom provides the latest, so no problem here. I've tried almost everything, complete wipe 5x, restored only apps with titanium (no system data or config), reformated my sd card, reinstalled latest blackrose, tried other kernels but this issue persists.

My sdcard is formated with one 1gb ext4 partition on 4ext recovery, both partitons are perfectly aligned, and i have dalvik cache in internal memory.

The strange thing is that after a normal reboot, the phone comes back to normality for a few hours or even 1 day or 2.

It has happened to me 2/3 times the phone lock with black screen and touchpad lights on, battery pull, but not too often.

I'm starting to think that my SanDisk 16Gb class4 performance has degraded a little to run xpart and i'm thinking that go to a2sd may be the only solution.

Any thoughts on this?
[Nexus One Android Development] timmae2:
same prob here in last versions. try to wipe cache. works for me
[Nexus One Android Development] johnnydvc:
Ok, thanks usually i wipe dalvik cache, cache and fix permissions, but for now i'll try to wipe only cache to see if it gets any better, if no i think i'll test a2sd version w/ stock hboot to see if it goes more stable.
[Nexus One Android Development] jbbandos:
I've had that a couple of times, and when I use adb to check what is going on usually I find that sd-ext gave a hardware error and is mounted r/o instead of r/w. I was thinking it was my N1, which always had problems with uSD cards, but maybe it is a more widespread problem. I also had this with a2sd and xpart without odex, so maybe it is the kernel (I'm using stock), or there is a problem with the sd controller on a whole batch of N1s.
[Nexus One Android Development] Alex240188:
ah, you might be onto something there, i have always had problems with the SDcard on my N1, phone will lock up, reboot and its not even detected that the card is there, have to reboot about 10times before it actaully starts reading it again
[Nexus One Android Development] sl8125:
Anyone has the link to the latest rom version?
[Nexus One Android Development] timmae2:
first post?! O_o
[Nexus One Android Development] walliester:
any news on the update bro,
[Nexus One Android Development] eidros:
+1 exactly same problem!

I thought my hboot was corrupted from flashing MIUI ICS ROM so I upgraded my hboot, reformatted,uSD, full wipe several cycles and normally after a day of normal performance, the FCs are back.

Ocassionally the phone freeze up with swype, whatsapp and a few google apps.

Let us know if you solve it with the a2sd ROM.
[Nexus One Android Development] johnnydvc:
Well I've tested wiping only cache and it worked well for one day, then after a call, black screen and only hardware keys light up, battery pull. I'm using KGPNeok 3.9Ti w/ smartassv2, min cpu245mhz, but had the same issues with stock one.

Maybe i'll try a2sd with BR in stock partition layout since it doesn't require so much of sdcard and see how it performs then i'll give feedback.

All I can say for now is that I've used a2sd in the first versions of this rom (when xpart was very unstable) and never had these issues.

Thanks for the tips :)
[Nexus One Android Development] jbbandos:
I've been trying to fix the problems with superuser rebooting the phone instead of asking to give message or call permissions with an app. I can release a ROM today, but still haven't found the root of the problem, so I'd rather try and see if I can fix it this week before launching a new ROM.

As there aren't many (if any) differences from last week, I ask you guys to be patient. I'll still launch next week's ROM, even if I can't fix superuser.
[Nexus One Android Development] jbbandos:
Guys, what theme are you using? Strange as it seems, some MIUI themes have a tendency to freeze the phone. There is one I quite like, that looks like a leather handbook, that I had to give up as my phone would freeze like crazy and reboot a lot with it. Switching to the stock theme fixed it.

Another thing that reduced freezes and reboots a lot was to backup my sdcard, and repartition it with 4EXT, to make sure the partitions are aligned and clean. That gave almost new life to the phone.

Can you try one (or both) of these and see if it helps?
[Nexus One Android Development] johnnydvc:
Hi, actually my sdcard since i use xpart had always been formated with 4ext recovery just to ensure that. Although I've backed it up, and reformated everything from scratch, but the phone behavior was the same.

For theme i use a mix of them, different ones in status bar, fonts, icons, etc.. i haven't tried to use the full stock one.

Now i moved to a2sd with stock partition layout (still BR hboot) and so far so good, everything smooth and no phone freezes or force closes, i hope it keeps running like this as i was tired of rebooting and battery pulling the phone everyday. I'm using exactly the same theme configuration and restored all apps, system settings, theme and data with miui backup and till now not a single issue.

Maybe my sdcard isn't fast enough to run xpart script or the sdcard controller of nexus has stability issues whit it, thats my toughts.

Thanks for this great rom jb, and for providing various versions so it can fit almost everyone's needs! :)
[Nexus One Android Development] eidros:
Hi,

This is great that you have narrowed it to the Xpart messing up with the uSD. I am thinking of moving over to a2sd too but I have about 60 apps that I installed on my N1. How many apps can you move over to SD? I also note that you are using MIUI backup successfully. They must have ironed out the bugs from the backup.

Would you be kind to list down your complete steps from scratch how you set up your N1 with the a2sd including backing up and restoring your apps?

BIG Thank you in advance.

---------- Post added at 10:58 AM ---------- Previous post was at 10:15 AM ----------

Hi Jb, I use stock theme and did a clean format with 4EXT, partitioned, fix and alignment check all the time but the behavior is the same; excellent for a day and then the FCs starts building up again over time it gets worst then the freezing up starts, a reboot will fix it for a while then the cycle begins :(

The thing is, did not have this problem before. I have been using your Xpart ROM ever since you start building it and had no issues until this last couple of months.

Any other suggestions?
[Nexus One Android Development] jbbandos:
:( Not really. Did you try using the app killer (long press on home, left button) from time to time, does it change anything? I am trying a couple of things this week, changing my approach to building this ROM, we'll see if it helps.
[Nexus One Android Development] net.cat:
The 3.7 is more stable than the 3.9 ;)
[Nexus One Android Development] net.cat:
Jb do you think this might be integrate into your rom?

http://xdaforums.com/showthread.php?t=991276
[Nexus One Android Development] johnnydvc:
Ok, no problem! :) I used latest 4ext touch recovery on this process, with 1gb ext4 partition.

Here we go:

I did a full backup with miui app, then applied stock partition sizes with latest blackrose hboot which I changed later to (Sys/Cache/Data)145/50/241, this configuration gives me more room on data partition as 95mb cache is completely useless IMO.

After that entered in recovery and full wipe 3x (wipe menu -> format all partitions except sdcard), then flashed a2sd 2.3.9 rom and kgpneok 3.9Ti kernel (stock is good too, but at least in my phone this one runs smoother with good battery life too, using smartassv2). Then reboot phone and install terminal emulator from market or replace it with miui backup as i did if you already had it. Go to superuser app and enable root permission, then, terminal emulator and type "su" allow root, then type the command "a2sd reinstall" the phone will reboot and then you're ready to replace your backup with miui app, i replaced all my apps and in system selected only call logs, sms, system definitions, desktop layout and theme (it's possible to see some apps force close during restore process, ignore it, here only facebook app did it, but no problem at all). After that (it's not obligatory) but i went to recovery, wiped cache+dalvik cache, and fixed permissions.

I also enabled zipalign on boot in a2sd gui app.

And that's, it i think didn't miss something.

I think you wont have space problems with 60 apps (of course it depends of the size of your apps) if you use this partition layout, and you can always move dalvik cache to sdcard to give you even more room on data partion if you need it, i have about 50apps installed with dalvik on internal storage and no problems, just make sure that there's no apps on your app manger -> sdcard tab, if there's any selected you should move it to internal storage as it is now symlinked tou your sdcard ext partition.

At least, here till now (2.5 days of usage) i see no performance difference from xpart at most important at all it's running rock stable. :)

---------- Post added at 04:19 PM ---------- Previous post was at 04:13 PM ----------

Here used 3.7 for some time, but decided to try 3.9 despite some comments, i have no issues till now everything as good as 3.7 in my experience. ;)
[Nexus One Android Development] net.cat:
have been the lockscreens updated to the last release!?
[Nexus One Android Development] jbbandos:
I don't think so, but anyway, the mechanism seems now stable, so it shouldn't be needed like it was from 1.6.17 to 1.6.24.
[Nexus One Android Development] jbbandos:
And just a few hours later, here is another release. This time only a update pack, supposedly fixes the slider at the bottom of the screen, and has some updated translations.

Also, as I messed up with the XPART rom, the XPART update pack has a fixed build.prop identifying itself as XPART.
[Nexus One Android Development] pseudoheld:
just a little heads up.

i was using trackball alert (which worked fine) but the nag message of the light version bothered me.

so you might wanna try light flow:

http://www.appbrain.com/app/light-flow-lite-led-control/com.rageconsulting.android.lightflowlite

the lite version works fine without nag and the pro version is quite a bit cheaper than trackball alert pro.
[Nexus One Android Development] hughey2k2:
how is the xpart working has anybody tried it yet?
[Nexus One Android Development] athost:
To my mind XPART is working perfect. Fast and stable.

I'm happy :)
[Nexus One Android Development] jbbandos:
For me it worked until the SD card overheated and started disconnecting. My N1 doesn't work for long periods with any XPART I've tried yet, it is either a controller or physical connector problem, it just heats too much and starts disconnecting the SD card.
[Nexus One Android Development] jbbandos:
V3 now online, as a service pack. More translation updates, and a fix for the status bar FCs in the Italian translation.
[Nexus One Android Development] timmoty_g:
hi jbbandos,

same here, but mine was working fine with XPART using 1.6.24, but then i start using 1.7.1 everything went bad.

is it possible it's due to kernel integrated in 1.7.1 doesn't really support XPART?

i saw in XJ's thread that he supplied different kernel for those who want to try XPART. i installed XPART in a DESIRE using that that kernel and has been fast and stable so far.

I've tried the kernel, but the build is meant for DESIRE, do you know where I can get such kernel for N1? I'm going to try out kernel from Rod and we'll see...

regards.
[Nexus One Android Development] timmoty_g:
Sorry man, the XPART is still falling apart after a while.

I'm now testing MIUI_NX, the D2EXT version, so far so good, there must be something missing on your version.
[Nexus One Android Development] jbbandos:
Well, good for you if it works well, go for it. I always liked his ROMs, and one of the reasons I started mine was because he disappeared for some time and I started learning how to build a ROM to be able to get the latest stuff.

Anyway, for me every XPART started falling apart after some time. As I wrote before, it is like my N1 can't handle the extra SD writes and reads. And that happened with my XPART, with Rodriguez XPART, with everything I tried. It took more or less time, but in the end always ended up the same way. I might check dRaCID01's take on XPART to see if it works on mine, but nothing should be different - we both are getting our scripts from XJ ROM.

As for your ideas on the kernel, I've thought about it. I'll have to ask XJ where can I get the kernel sources for the A2SD and the XPART kernels, to compare them with each other and then with Wildmonk's kernel, to try and find if there is some tunning we can do to get XPART working stable on a N1 like mine.
[Nexus One Android Development] jbbandos:
Ok, I went looking into my ROMs and found one error in my xpart scripts and another in my installer script, added from 1.6.24 to 1.7.1, apparently when I was trying to get it to work on my N1. Thanks for the report, I'll release it as a full ROM including the updates ASAP (it will take at least a couple of hours to upload, unfortunately).

I have now to check if dRaCID01 adds anything to the XPART scripts, but this update is more urgent. I have a feeling the solution might reside in the kernels - if I can somehow lower the heating when using the SD extensively, I'll be able to use XPART on my N1.
[Nexus One Android Development] jbbandos:
First of all, a big apology for all XPART users. While trying to get XPART to run stable on my N1, I edited the scripts, and failed to completely restore them before releasing 1.7.1. The result is that one of the scripts had an "IF" missing, and that would cause data corruption. I've now fixed that, and released the ROM again. I also took the opportunity to re-release the A2SD version. I've added all the fixes in the two update packs (V2 and V3) and have finally noticed that the wrong install script was being used (not that it was broken, but it missed some customization and identification of which version it was flashing).

Once again, apologies to everyone, the ROMs are in the OP, and please report bugs as soon as you find them.
[Nexus One Android Development] incredulous:
jb, I really appreciate all the work you're putting into getting XPART working without being able to properly test it yourself.

However... I have now installed 1.7.1V4 and I am having a different issue now - I usually check that it's working by looking in Titanium Backup to see what it says for internal ROM and A2SD. They are usually the exact same amount when XPART is working right but with V4 internal is saying 202mb and a2sd is showing the EXT4 size.

It's as if the ROM isn't working with the 2 EXT partitions properly.

I'm trying to flash wildmonks kernel now to check if its kernel related.

EDIT: I flashed wm's kernel and I am still having the same problem. Now I'm gonna flash the format zip, then V4 and then do the a2sd killer and then data2sd installer. :)

EDIT: Right, I flashed the A2SDKiller and then flashed the Data2SD Installer and all is working as it should be now :)
[Nexus One Android Development] jbbandos:
I'm flashing XPART now on my N1, it should hold enough time to let me check what went wrong this time.

Edit: Ok, just found out I uploaded the wrong file. :( This week everything goes wrong with XPART. I'll upload the correct one ASAP.
[Nexus One Android Development] timmoty_g:
don't worry man, I'll check your post now and then, I'm backing up mine and will download your very very latest once available.

Then I'll backup one more time using nandroid and give your version a try.

Please correct me if if I'm wrong, since your XPART and MIUI_NX D2EXT are basically the same, I should be able to flash yours after clearing the cache and dalvik cache, right?

One more thing I'd like to highlight to you that MIUI_NX, somehow, it's able to add-up my EXT4 with the available Internal Data.

My EXT4 is 2GB (after formating it's shown 1.79), after full flash of your version, I would only get around 1.69GB left.

Using MIUI_NX, after fresh install I can get total space of 1.88GB with 1.84GB available.

Regards,

Timmoty
[Nexus One Android Development] jbbandos:
Ok, the correct version is up now. I flashed it on my N1, and got 1GB free, so it should work. I'll try again to see how long does it hold now that the camera reset has been fixed. If it doesn't crash and burn until Friday, maybe I'll keep using XPART.
[Nexus One Android Development] jbbandos:
Hi Timothy,

My XPART should be the same as NX D2EXT. We are using the same scripts, developed by MIUI and patched by XJ. I've just checked, and there is no difference. So yes, you should be able to use this without a full wipe. The only thing that changes is that NX formats /data when installing, and I leave it. That was one thing I didn't like with dRaCID01 A2SD ROMs, that I always had to restore everything when flashing a new version. That said, maybe it makes sense with XPART to wipe /data whenever installing a new ROM. But afaik, you'll never combine both sd-ext and the internal /data in a single partition, there is nothing in the scripts (at least that I can find) to do that. Maybe I'll have to see if I can find the difference in the few minutes my N1 works with XPART before it starts giving mmc io errors like crazy.
[Nexus One Android Development] timmoty_g:
I agree, it's better to separate them apart, it's cleaner that way?
[Nexus One Android Development] jbbandos:
I don't even know how to combine them, or what NX is doing if it is indeed combining both partitions. All I've seen from the scripts indicates NX doesn't do it.