[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by imohtep

But i need full data for my job and my dialy uses, in my personal opinion an android phone without data is a normaly phone only sms and calls

And What application do you recommend to get the good logs? I really like to work together to find the solution to this problem

Well obviously data is nice, but if you want to save battery disable it.

There's no app to get SoD logs. last_kmsg are the only way, please follow this thread.

[muziling]

Finally, easy to prevent erase or overwrite protected partition

platform/msm_shared/nand.c

int flash_erase(struct ptentry *ptn)
{
    unsigned block = ptn->start;
    unsigned count = ptn->length;

    if (ptn->perm == PERM_NON_WRITEABLE) {
        dprintf(INFO, "%s partition is protected, can't be erased.\n", ptn->name);
        return -1;
    }

    set_nand_configuration(ptn->type);
    while(count-- > 0) {
        if(flash_erase_block(flash_cmdlist, flash_ptrlist, block * 64)) {
            dprintf(INFO, "cannot erase @ %d (bad block?)\n", block);
        }
        block++;
    }
    return 0;
}

int flash_write(struct ptentry *ptn, unsigned extra_per_page, const void *data,
        unsigned bytes)
{
    unsigned page = ptn->start * 64;
    unsigned lastpage = (ptn->start + ptn->length) * 64;
    unsigned *spare = (unsigned*) flash_spare;
    const unsigned char *image = data;
    unsigned wsize = flash_pagesize + extra_per_page;
    unsigned n;
    int r;

    if (ptn->type == TYPE_MODEM_PARTITION)
    {
        dprintf(CRITICAL, "flash_write_image: model partition not supported\n");
        return -1;
    }

    if (ptn->perm == PERM_NON_WRITEABLE) {
        dprintf(INFO, "%s partition is protected, can't be overwrited.\n", ptn->name);
        return -1;
    }

Tested pass:

E:\adb-tool>Fastboot flash TPCAL x:\cal.raw
sending 'TPCAL' (128 KB)... OKAY [ 0.110s]
writing 'TPCAL'... FAILED (remote: flash write failure)
finished. total time: 0.345s

E:\adb-tool>Fastboot erase TPCAL
erasing 'TPCAL'... FAILED (remote: failed to erase partition)
finished. total time: 0.692s

[mbellot]

Originally Posted by muziling

New LK can use fastboot update LK itself, but I don't know how to compile source code to ruu_lk.img.

Don't tast29 and flash my NBH, no need to re-flash NAND rom(assume you are use ACL newest nbh), direct run into android then dump wifi data.
After this, can flash ACL nbh back, no need to task29

Don't do "fastboot erase WIFI", it's safe.

Also, weekend is OK too.

I haven't upgraded to the newest LK yet. Because of the "fun" I had with the last update I decided to wait until ACL pushed a new release.

I'll see if I can get it done this weekend.

[muziling]

Originally Posted by mbellot

I haven't upgraded to the newest LK yet. Because of the "fun" I had with the last update I decided to wait until ACL pushed a new release.

I'll see if I can get it done this weekend.

Thanks, I got that file from others, write back to my phone, now RHOD400!!!
But I always hope you can give me a copy, I can compare what different between them.

[[ACL]]

Originally Posted by muziling

Finally, easy to prevent erase or overwrite protected partition

platform/msm_shared/nand.c

int flash_erase(struct ptentry *ptn)
{
    unsigned block = ptn->start;
    unsigned count = ptn->length;

    if (ptn->perm == PERM_NON_WRITEABLE) {
        dprintf(INFO, "%s partition is protected, can't be erased.\n", ptn->name);
        return -1;
    }

    set_nand_configuration(ptn->type);
    while(count-- > 0) {
        if(flash_erase_block(flash_cmdlist, flash_ptrlist, block * 64)) {
            dprintf(INFO, "cannot erase @ %d (bad block?)\n", block);
        }
        block++;
    }
    return 0;
}

int flash_write(struct ptentry *ptn, unsigned extra_per_page, const void *data,
        unsigned bytes)
{
    unsigned page = ptn->start * 64;
    unsigned lastpage = (ptn->start + ptn->length) * 64;
    unsigned *spare = (unsigned*) flash_spare;
    const unsigned char *image = data;
    unsigned wsize = flash_pagesize + extra_per_page;
    unsigned n;
    int r;

    if (ptn->type == TYPE_MODEM_PARTITION)
    {
        dprintf(CRITICAL, "flash_write_image: model partition not supported\n");
        return -1;
    }

    if (ptn->perm == PERM_NON_WRITEABLE) {
        dprintf(INFO, "%s partition is protected, can't be overwrited.\n", ptn->name);
        return -1;
    }

Tested pass:

No, bad method. We arent supposed to keep those partitions. So what i might end up doing is reading, and removing them from the ptable. flash_erase is actually stock code from google/ca since it's not meant to check permissions. But really dood, you are wasting my time with this because you decided to wipe your own nand ? come on man stop spamming my thread.

[trevoroni]

Finally got around to updating to the new LK and recovery and getting my CID. So here it is.
CID: TELUS001

Edit: And my phone is a Rhod500 with a Rhod400 keymap

[resinis]

might there be an app in the marketplace that would automate the connection/disconnection of the data line?

i get about 5 hours on a battery too... and whats funny is if i am streaming online radio in wm6.5 i might get 2.5 hours on a battery charge. while in xdandroid i usually get 3-4hours. so while xdandroid cant sleep like wm6 can, it seems to use less battery power for at least that one task.

but if we can get xdandroid to last all day like wm6 can without user intervention then i would definitely go nand. wm6 might be slightly faster, but android runs so much more fluently... plus there are a ton of apps

[milda25]

Originally Posted by resinis

might there be an app in the marketplace that would automate the connection/disconnection of the data line?

i get about 5 hours on a battery too... and whats funny is if i am streaming online radio in wm6.5 i might get 2.5 hours on a battery charge. while in xdandroid i usually get 3-4hours. so while xdandroid cant sleep like wm6 can, it seems to use less battery power for at least that one task.

but if we can get xdandroid to last all day like wm6 can without user intervention then i would definitely go nand. wm6 might be slightly faster, but android runs so much more fluently... plus there are a ton of apps

I'm managing data connection manually using standard settings (or widget data on/off on home screen). But be sure that data off brings you relative little battery life more. I have off all what I can (data, background data, autosync, gps positioning, tower positioning) and I have total battery life about 7-8 hours. This is very bad time. I hope there will be some optimalization soon, but it not depends on me. I'm waiting now for a new battery and I will see, what happened after use this one ...

[imohtep]

Hi, i think the battery drain with data service is critical in this rom, i have 3 or 4 hour battery life with only whatsapp and push mail, and in winmo i have 8 hour with push email and messenger online; i need data all time for my work

I like this rom (without SOD) but battery drain is critical, for this reason lamentably i roll back to winmo i hope this and SOD have any solution in the future release...!!

Thanks to all developers with this great effort and hard work have managed to extend the useful life of our phone..

[htrakr]

I never really had any issues with battery life and usually lasts the whole day (but then again I am not a massive data user (twitter, facebook and gmail and some app updates) and I have wifi on pretty much the whole day and only a few calls/texts and less than 30 minutes of GPS)
However I noticed something interesting after installing the battery icon mod from UOT kitchen (By itself it is great instead of the useless icons that come stock).
Normally the battery meter is useless and would jump 20-30% randomly and vary from 20% to 90% irrespective of what the actual battery was.
But after the battery icon mod now the battery is very stable and has gone down from 95% to 40% in a very linear way without randomly jumping around. I am sure it has nothing to do with the mod as it only mods the framework-res and systemUI apks and doesnt touch the drivers.
Is there some type of log I can pull to see how the battery is affected