Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS! - Page 341

**arrrghhh** · #**3401** (**permalink**) 07-29-2010, 09:54 AM

Quote:

Originally Posted by Mylt1

you need a lighter rom to get the most out of android. its not running all by its self. it is merely running on top of WinMo. im actually running an older SSK 6.1 rom with 50% available at boot and usually run 45% free there after.

Not true. We've all done a lot of testing, and the ROM seems to have no effect on Android. It doesn't really run "on top" of WinMo - Android literally takes over the hardware. Sure, WinMo helps by initializing some pieces of hardware (I think only the display/touchscreen remain...) but Android boots WinMo out of memory. Hence the reason you have to soft reset to get back to WinMo - there's nothing of it remaining when you run haret.exe!

So if you *think* it's running better because of your ROM... you're probably just experiencing what is called the "placebo effect"! Gotta love it.

**Mylt1** · #**3402** (**permalink**) 07-29-2010, 11:30 AM

Quote:

Originally Posted by arrrghhh

Not true. We've all done a lot of testing, and the ROM seems to have no effect on Android. It doesn't really run "on top" of WinMo - Android literally takes over the hardware. Sure, WinMo helps by initializing some pieces of hardware (I think only the display/touchscreen remain...) but Android boots WinMo out of memory. Hence the reason you have to soft reset to get back to WinMo - there's nothing of it remaining when you run haret.exe!

So if you *think* it's running better because of your ROM... you're probably just experiencing what is called the "placebo effect"! Gotta love it.

if that is the case, then android takes up more memory than even the worst winmo rom i have made.

**arrrghhh** · #**3403** (**permalink**) 07-29-2010, 11:42 AM

Quote:

Originally Posted by Mylt1

if that is the case, then android takes up more memory than even the worst winmo rom i have made.

How do you mean? For a while there, Android didn't even have access to all the memory banks available on the device... You do realize that this entire project is reverse-engineered, right?

**Mylt1** · #**3404** (**permalink**) 07-29-2010, 01:49 PM

yes, and if its booting winmo from the ram and taking it over then it uses more ram that winmo, a lot more. im going to experiment a little this afternoon just to see what, if anything, changes.

**Mylt1** · #**3405** (**permalink**) 07-29-2010, 02:20 PM

Quote:

Originally Posted by arrrghhh

Not true. We've all done a lot of testing, and the ROM seems to have no effect on Android. It doesn't really run "on top" of WinMo - Android literally takes over the hardware. Sure, WinMo helps by initializing some pieces of hardware (I think only the display/touchscreen remain...) but Android boots WinMo out of memory. Hence the reason you have to soft reset to get back to WinMo - there's nothing of it remaining when you run haret.exe!

So if you *think* it's running better because of your ROM... you're probably just experiencing what is called the "placebo effect"! Gotta love it.

hate to say your wrong but, you are. the available mem in winmo does indeed effect android. i just tried 3 different test 2 of the 3 failed to load android and cause the phone to reset. the first was off a fresh reset, nothing running other than winmo(used task manager to kill everything running). used resco file explorer to open sd card and run haret. android booted normally with this method. next, reset phone and allowed everything to start normally. this time i opened up several apps in winmo that i know remain open according to task manager. i opened enough apps to get the mem usage up to 68%. then attempted to boot android. same as before, opened resco to sd card and run haret. got the scrolling as normal then, screen went black and phone reset. 3rd test was the same as the 2nd but only 65% mem usage. again, phone failed to boot to android and again rest back to winmo.

so, if winmo has no effect on android then how do you explain this? juse in case you dont believe me, tonight when i get home i can make a video to prove this. it was repeatable time and time again.

forget to add, this is a crippled VZN Touch Pro running SSK's 6.1 build 21054

88fingerslukee · #**3406** (**permalink**) 07-29-2010, 02:21 PM

Does anybody have the issue where the latest zimages (anything after "htc-msm-linux @ 20100715_202510") breaks charging?

By break, I mean that it ends up just thinking the battery is fully charged immediately after plugging in. Then when you unplug it'll go back to it's old state (usually almost empty).

**arrrghhh** · #**3407** (**permalink**) 07-29-2010, 02:27 PM

Quote:

Originally Posted by Mylt1

forget to add, this is a crippled VZN Touch Pro running SSK's 6.1 build 21054

I believe this is your problem but either way, I still disagree with your methodology. It's not consistent, or accurate in any stretch of the word. Besides, I'm mainly relaying information I've received from developers and testers. If you can find a consistent accurate way to test memory in Android, I'm all ears. But your method is neither.

Quote:

Originally Posted by 88fingerslukee

Does anybody have the issue where the latest zimages (anything after "htc-msm-linux @ 20100715_202510") breaks charging?

By break, I mean that it ends up just thinking the battery is fully charged immediately after plugging in. Then when you unplug it'll go back to it's old state (usually almost empty).

Yes, I believe however it is still charging, just not showing it correctly. This has been a reported issue over @ XDA tho, and I can confirm it on my device.

**Mylt1** · #**3408** (**permalink**) 07-29-2010, 03:00 PM

Quote:

Originally Posted by arrrghhh

I believe this is your problem but either way, I still disagree with your methodology. It's not consistent, or accurate in any stretch of the word. Besides, I'm mainly relaying information I've received from developers and testers. If you can find a consistent accurate way to test memory in Android, I'm all ears. But your method is neither.

how can you say that when it boots fine when there is nothing running in the background other than winmo itself? seems that somewhere between 60 and 65% mem usage and above can and does cause issues with android booting. and really, anything above 65% usages prevents android from booting period. so you just dismiss problems that people find because you dont believe in the way there finding them? thats real scientific. as far as my method, it most certainly is "consistent". if your using 65% of your mem in winmo according to task manager and android wont boot and its the same thing every time your using 65% thats consistent and repeatable. last i knew, something that was repeatable from start to finish with the same results was proof of concept with a scientific experiment. most developers and testers are running andriod off a fresh boot. they arent thinking about the "what ifs" like what if someone has been using there phone for the morning then wanted to switch over to android without doing a reboot or using something like task manager. again, i just ran the phone up to 65% usage and yet again, android would NOT boot. this may not be a problem for sprint users but for those of us that are VZN users it is indeed an issue we need to be aware of. so if a rom your using is not running less than 60% on boot then you can have issues with android not running. so wouldnt you say thats rom related?

so, any VZN users. you need to be running a pretty effecint rom if you want to run android too. if your running near the 60% mem usage mark then you need to either reboot or use something like task manager to kill any apps that are running in the background(IE they dont close all the way) before trying to boot android. another option is, if you want to run just android, to make a stripped down custom rom. 6.1 is a good option an you will need to drop the pagepool to get it as low as you can.

88fingerslukee · #**3409** (**permalink**) 07-29-2010, 03:21 PM

Quote:

Originally Posted by arrrghhh

Yes, I believe however it is still charging, just not showing it correctly. This has been a reported issue over @ XDA tho, and I can confirm it on my device.

Thanks, I'll keep an eye on it.

Anybody notice that the headset audio is now working? I've tested and it works including the headset mic! Awesome!

**Mylt1** · #**3410** (**permalink**) 07-29-2010, 03:28 PM

Quote:

Originally Posted by 88fingerslukee

Thanks, I'll keep an eye on it.

Anybody notice that the headset audio is now working? I've tested and it works including the headset mic! Awesome!

the charging has been talked about over at XDA. most have said even though it doesnt look like its charging, it actually is. the newly updated files fixed the headphone problem as well i believe. i didnt ready the whole update but i think it was mentioned as well as an increase in the earphone speaker vol.

here is the XDA thread in case you want to keep up with whats going on over there as well. http://forum.xda-developers.com/showthread.php?t=711692

scratch that. i see your already over there. LOL.