Page 3 of 3 FirstFirst 123
Results 41 to 49 of 49
Like Tree10Likes
  1. #41  
    Quote Originally Posted by Preemptive View Post
    Hmmm... is that perfectly cromulent?
    I think cromulence would only come if someone can get this upgrade to work.
    Author:
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    GO OPEN WEBOS!
    People asked me for a donate link for my non-catalog work, so here you are:
  2.    #42  
    I've recently had some time - and ideas - to try to figure out what might be happening with this.

    Just like the first time around, an article on HackaDay inspired me. This time, it was an account of someone with a Nexus 5X sending their broken phone off to a shop in Shenzen, China, and the process of getting a CPU replacement, also upgraded that phone's RAM from 2GB to 4GB. Upgrading RAM on a Nexus 5X | Hackaday

    The user got the phone back and it all worked - the Android kernel recognized the extra RAM with no modifications, no difference in the boot loader, etc.

    Well, maybe if I installed one of the recent versions of Android onto my TouchPad with the 2GB RAM chip installed, maybe the Android kernel would see the extra RAM, where webOS wouldn't? It's worth a try, right?
  3.    #43  
    I ended up having other problems with the original TouchPad I installed the 2GB RAM chip into, so I got another TouchPad. Before I swapped out the 1GB RAM to 2GB, I installed moboot 0.3.8 and the latest nightly build of Evervolv Android for the TouchPad (7.1.2, I think). When I booted into Android, it saw the 1GB of RAM in the Android Settings app, like I would expect it to.

    I did the "surgery", and installed a 2GB RAM chip like before, and turned on the TouchPad. The surgery was successful - the patient survived, and I first booted into webOS, to make sure everything was working normally. It seemed to be.

    Now on the original TouchPad, when I used novaterm to access the Linux CLI on the TouchPad, I could see that the TouchPad only saw 512MB of RAM, instead of 2GB like I was expecting. So I was expecting the same thing on this one as well, but instead, I got a surprise.

    First, I noticed that I did not get the moboot menu that let me choose between Android and webOS, etc. It skipped right over that and went right into booting into webOS. OK, well, let's novaterm in and see what's going on with the RAM:

    Code:
    root@webos-device:/# free -m
                 total       used       free     shared    buffers     cached
    Mem:           919        338        581          0         16        136
    -/+ buffers/cache:        185        734
    Swap:          511          0        511
    root@webos-device:/#
    Wait, what? Now with this other TouchPad, I see 1GB, not 512MB like before? What's going on?
    poehoes likes this.
  4.    #44  
    I examined the contents of the /boot partition to see what might have happened to cause moboot to not show the menu and skip right to webOS. Everything looked fine there, but even after rebooting again, it just never displayed the menu and skipped right to webOS.

    So, I decided to soft-link the uImage to uImage.evervolv (I think that was the right name) and force the TouchPad to boot to Evervolv Android. That's when it got even stranger - Android only partially booted. I never got the "splash" screen - just a black screen, but the backlight was on. I tried access the Android shell via the USB cable, and that worked - I got a shell prompt.

    I didn't capture the results of running "free -m" like I did under webOS, but Android only saw somewhere between 300MB and 400MB, and the logs were filled with "out of memory" messages. (!) So that would explain why I didn't ever see the Android GUI. But why the heck did Android see so little memory? And why did webOS on this TouchPad see more than webOS on the first TouchPad I upgraded to 2GB?

    Well, when I forced this TouchPad to boot into Android by fiddling with the files in the /boot partition, I realized that I didn't know how to modify the /boot partition from Android, so I decided to run the webOS Doctor on it.

    After that was done, I again used novaterm to login to the Linux command line, ran "free -m", and this time I got 512MB of RAM total.

    Uhhh..huh? The same TouchPad...in 3 different situations...came up with 3 different totals of available RAM??? How is that possible?
  5.    #45  
    I figured out at least part of the answer, and the answer is moboot.

    You see, I saw 1GB of RAM in webOS when the TouchPad had moboot installed, and I then booted into webOS.

    After I doctored the TouchPad, the doctoring process re-built the /boot partition, and removed moboot, and when I booted the freshly doctored TouchPad, that's when I saw only 512MB of RAM.

    When I next re-installed moboot on the freshly-doctored TouchPad, and used it to boot to webOS, I again saw 1GB of RAM. (!)

    OK, so it's not all of the 2GB of RAM I have installed, but there is CLEARLY something going on at the bootloader level that influences how much RAM the TouchPad sees. I suspect it has to do with where in physical RAM the Linux kernel gets loaded, but right now, that's just a guess.
    Preemptive, kimsan and KURT B like this.
  6.    #46  
    More progress!

    The good news - I now have a TouchPad that recognizes more than 1GB of RAM!
    The bad news - it doesn't recognize all of the 2GB, and it's not quite stable.

    It took some time to research and learn how to setup a build environment for the moboot boot loader. And also to find where in the moboot source code it tells the linux kernel how much RAM the TouchPad has. And more trial and error to tell it how much extra RAM was available. (It turns out it's not just an extra 1GB, as would seem to be logical)

    Here is what the relevant part the boot logs and command line output look like:

    Code:
    [    0.000000] Memory: 101MB 1408MB = 1509MB total
    [    0.000000] Memory: 1469944k/1469944k available, 75272k reserved, 0K highmem
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    [    0.000000]     DMA     : 0xff000000 - 0xffe00000   (  14 MB)
    [    0.000000]     vmalloc : 0xe0000000 - 0xfa000000   ( 416 MB)
    [    0.000000]     lowmem  : 0x80000000 - 0xdfe00000   (1534 MB)
    [    0.000000]     pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    [    0.000000]     modules : 0x7f000000 - 0x7fe00000   (  14 MB)
    [    0.000000]       .init : 0x80008000 - 0x8003f000   ( 220 kB)
    [    0.000000]       .text : 0x8003f000 - 0x80744000   (7188 kB)
    [    0.000000]       .data : 0x8076c000 - 0x807f1080   ( 533 kB)
    Code:
    root@webos-device:/# free -m
                 total       used       free     shared    buffers     cached
    Mem:          1435        454        981          0        116        143
    -/+ buffers/cache:        194       1240
    Swap:          511          0        511
    root@webos-device:/#
    I quickly did a memory "stress test" by loading up a bunch of apps and web pages, and this is where the bad news come in. It seems as soon as webOS wants to access any of the additional RAM, it reboots. :-( It did this more than once, so something still isn't quite right.

    I may have to make some changes to the kernel as well, so more research is needed.
    MudShark22 likes this.
  7. #47  
    I have to admire your persistence! I've delved into my bucket of ignorance to come up with an idea!
    If you have to change the kernel, then it will be a custom kernel. We already have those from webOS Internals. Any chance that one of those will work better? I think it might be unlikely. But what about the LuneOS kernel - made for newer configurations?. But now I'm thinking the kernel might be specific to the H/W...

    Someone feel free to educate me!
  8.    #48  
    Good thought. I have used both stock webOS kernel and webOS Internals UberKernel with the same results.

    -- Sent from my Palm TouchPad using Forums
  9. #49  
    Wow, glad to see some progress has been made, but I'm not sure that it's entirely helpful. I suspect that bootie needs to understand the RAM to properly initialize the hardware.. but I hope I'm wrong, and a way can be found. If you do find a way, I'd gladly finance a set of upgrades for my devices :-D I'll poke at another contact that might know something, but at this point, most useful information is in a memory hole.
    Author:
    Remove Messaging Beeps patch for webOS 3.0.5, Left/Right bezel gestures in LunaCE,
    Whazaa! Messenger and node-wa, SynerGV 1 and 2 - Google Voice integration, XO - Subsonic Commander media streamer, AB:S Launcher
    (1:39:33 PM) halfhalo: Android multitasking is like sticking your fingers into a blender
    GO OPEN WEBOS!
    People asked me for a donate link for my non-catalog work, so here you are:
Page 3 of 3 FirstFirst 123

Similar Threads

  1. Cannot upgrade to 3.0.5 through Touchpad. What to do?
    By joeybadoey01 in forum HP TouchPad
    Replies: 8
    Last Post: 03/16/2012, 08:36 AM
  2. robotek upgrade for touchpad??
    By vella_ in forum webOS Apps & Games
    Replies: 21
    Last Post: 10/07/2011, 08:14 PM
  3. Can't yet Touchpad to upgrade from 3.0.0 to 3.0.2
    By HckrAdm2005 in forum HP TouchPad
    Replies: 7
    Last Post: 08/29/2011, 02:14 PM
  4. I would attempt
    By taglioni in forum Palm Pre and Pre Plus
    Replies: 1
    Last Post: 01/01/2010, 01:28 PM
  5. Should I attempt it on my 180?
    By GregP74 in forum North American Carriers (GSM)
    Replies: 3
    Last Post: 09/09/2002, 06:20 AM

Posting Permissions