yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] detule:
In 3.3.4 wifi-nvram.txt should be created automatically for you - no fix should be needed.
[Touch Pro2, Tilt 2 Android Development] motisu:
Was BT support included in 3.3.4?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sounds like the nvram issue is fixed, and use ConnectBot ;).

Look thru the commits on GIT... but no, not yet.
[Touch Pro2, Tilt 2 Android Development] motisu:
I only asked because Detule said that he probably would include it so naturally, when it was upped, I ran to install and was disappointed that it didn't work...:( Hopefully, next round.
[Touch Pro2, Tilt 2 Android Development] jonners59:
An interesting 24hrs. My initial observations:

The phone boots up perfectly then suddenly, shortly after getting everything up, it goes in to reboot - XDANDROID animation. When it returns data connection is lost. Some times it reboots more than once. My old trick of booting in to "in flight mode" does not work. So sometimes I have to do reboots in an effort to get data back.

I have had trouble with Superuser and SU Update fixer. Both needed re-installing and neither seem to be working properly - they keep needing re-installs, though they seem better today. Also noted that during the boot up, I do not get the long list of messages "x app has been granted super user privileges".

The phone is markedly hesitant. By that I mean it seems to be sluggish in response. I.e. inbound calls normally can not be answered because by the time it responds the call is missed. I had one call crash on me and the phone then went in to reboot in to WMo.

Neither CoPilot nor any of the Google "map" applications worked. neither could get a GPS lock and the Google apps refused to fully load - black screen with the wait logo...

Sorry, it has not been positive. I am hoping it shall settle down and get better in some aspects.

Guys, MANY, MANY thanks for these, and sorry I was not logged in yesterday to pick them up. Much time spent working.

I'll try the code next time and feed back, but my thread today may ask other questions. arrrghhh was correct until I had that inbound phone call that crashed out on me.

It feels like too much is going on in the background and maybe the point raised a few days ago about boot order may help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You've restored some app that's wreaking havoc. Either start completely over, or go thru your startup apps one-by-one using the methods laid out in my speed improvements thread.

I guess your SD card could just be dead/dying....
[Touch Pro2, Tilt 2 Android Development] jonners59:
Cheers arrrghhh, I'll take a look, but the ones that stand out are data connectivity or the phone. But I'll try turning all off and turning them on one at a time.

I had a call this evening, after the caller hung up and I took the phone from my ear, the screen was blank, and non of the keys worked including on/off. It seemed dead and the only way to get it going was to reboot.

Could a script be put togeter that I could use that launches at boot and starts a log. Otherswise I just can't get to an app to create a log for you?

The card is OK.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
How do you know it's not an app? From what I recall, you had 10,000 apps installed and 5,000 of them running at once. I would see if these issues recur on a fresh data.img, no apps.

Seemed dead... did you try ADB? Did you wait 10 minutes? Did you try hitting power, wait 30 sec, hit power again?

Remember, just because the phone appears dead does not mean it is dead...

All logs start from boot - the issue is they wrap after they reach a certain size. I'm not aware of any way around this, you'd need some sort of system to archive the logs on the SD card - sounds insane.

How do you know for sure?
[Touch Pro2, Tilt 2 Android Development] frostyguy:
I just ended up downloading another copy of TE from the market, thanks again.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Note sure if this is build or kernel related, but is charging good enough to be used in Android or should I still turn the phone off to charge it (what I'm doing now). Only reason I ask is because after plugging it in, a few minutes later the light goes from orange to green even if the device has been running all day.

Using Kernel 3.3.4 if it's kernel related. Never been sure.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
I'm running GBX0C with kernel 3.3.4 on my Rhodium100. When the phone re-wakes the wifi can't connect with any network. The phone sees the different networks, but is unable to establish a connection. When wifi is disabled and re-enabled it works fine. This wasn't an issue in FRX07.

Click here for logs
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
After 24 hours of testing i had just 2 problems. No sound and no autobacklight:(

Everything else works flawless including WIFI, GPS and finnaly my camera works awesome nice work!

I'm on the latest kernel 3.3.4, running on a rhod100.

I will upload logs in the afternoon.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I've been running this release on Sprint CDMA Rhod since last week with the kernel pack that was the latest at the time (the one before 3.3.4). I've been happy as BT was apparently working, not very well, but I actually made a dozen plus calls with BT, and it was fine. Kind of, because after sleep it would not always recognize that the earpiece was there to connect to, or in couple of occasions when I turned on the earpiece the phone would completely freeze.

Then yesterday all heck broke loose. 1st the phone got completely unresponsive, i.e. no reaction of any kind on any key press. I was not home to see if was really dead by hooking ADB, so I did the battery pull.

After that stuck in bootani for 5+ minutes. Another battery pull, it booted, but would FC everything. Shutdown then reboot. Stuck in bootani, booted after 2 more tries, everything FC again. I checked then and saw 3.3.4 kernel. Put it on, wiped data, put original rootfs on and tried to start from scratch. As I posted in kernel thread, it would not go through initial boot getting stuck on calibration, as if ts-calibration file was not in the directory. After that I reverted to 3.3.2 and it went through, though I made no attempts to use BT for now.
[Touch Pro2, Tilt 2 Android Development] detule:
Sound is an issue on your end -> make sure you have followed the csv directions to the "t".

Auto backlight on rhod 100 - Make sure you boot with auto-backlight OFF in winmo. Even then, I am not sure if anyone has ever tested auto-backlight on RHOD100 -> i know you guys have funky panels. As far as i know, it's been tested to work on 210 and above. Perhaps test to see if it works for you on .27 - should be similar as in 3.x, same mechanism is used in both kernels. If it doesn't work then someone needs to do some haret tracing in winmo.

Bluetooth hasn't made it to 3.3.x. It's on my phone I just need to find time to run down to my car and see if pairing works fine. If for whatever reason you need bluetooth, probably 3.2.x is your best bet.

Impossible to tell re: any of your other problems -> you've supplied no logs, and the solution to these problems isn't obvious ObviousMan. FCs and stuck in bootani usually means issues with your data.img. However you are starting with a clean slate and still experiencing these problems, could be that your sdcard is dying. No idea.
[Touch Pro2, Tilt 2 Android Development] eik:
I tried out GBX0C. Phone runs smoothly, camera works. Unfortunately the problem still exists that the phone loses internet connection in low signal areas (commuting by train). Sometimes it can be fixed with airplane mode on/off, but often it requires a reboot.

Let me know if logs would be of any help (but I understood this is a known bug already).

Also I had the phone freeze completely on charging twice now.

Kernel 3.3.4

Rhod 100 uk /AUO
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Good to know that BT was not even suppose to work in 3.3.x

I tried 2 different SD cards (8gb class 4, 16gb class 10 - pretty much brand new), both formatted with HP tool. Yes, I gave up quickly and went back to 3.2 as I needed to use the phone and could not get to U/L logs.

Once 3.3.x with your BT update will make it into the build, I will try to do a proper debug if it starts going sideways. For now, sticking with 3.2.x

Thanks.

OM
[Touch Pro2, Tilt 2 Android Development] agibby5:
FWIW, I cannot get the APN setting to save... anyone else?
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Any more people who have trouble getting the phone asleep in GBX0C? I installed LedRegime to check if the phone went to sleep, but it seems it is almost the whole time awake. Well, that explains the bad battery life...

On FRX07 the phone was a real Sleaping Beauty... Logs needed?
[Touch Pro2, Tilt 2 Android Development] walter79:
Use CpuSpy to check deepsleep.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Hmm... CPU Spy tells me the following:

Time in state:

528MHz: 15%

245MHz: 84%

Unused CPU states:

122MHz, Deep Sleep

So it does seem that the phone doesn't go to sleep...

Logs are here
[Touch Pro2, Tilt 2 Android Development] Caldair:
I was having similar issues getting the phone to enter deep sleep, and after a day of testing it became apparent that my rhod100 wouldn't sleep if wifi was set to on, regardless of the wifi sleep policy (ie. When Screen Off). If I manually toggle wifi and then turn the screen off the device would sleep almost immediately. Sooo this was good to know but not good news as I don't use data and need wifi for everything. But I installed a program from the market called GreenPower free which can override androids inbuilt sleep policy for wifi and control when the wifi sleeps and wakes (and can control syncing schedule and data connection - haven't tested the latter)

For me after setting up GreenPower the way I wanted my phone now goes to sleep (deep sleep, xdaledregime green light) within minutes of turning the screen off and stays that way until wifi comes on after 1 hour and stays on for 2 min for sync, etc then deep sleeps again, and repeat!

The other day I was getting about 5 hours of screen off before battery died now I just got 13 hours of light to moderate usage and some periods of deep sleep on an incomplete charge (about 1.5 hours) from within Android.

This is on the latest kernel 3.3.4 (may 1) and latest bundle GB0XC (may 3), I don't know if this problem was unique to my device or if it may be similar to problems that others are experiencing but hopefully this helps some of you out like it has me.

As of now this old beauty just got a new lease on life as this is the first time I have found an Android build for the rhodium that can last a day off the juice.

Huge thanks to ALL the developers involved in XDAndroid and specifically to Detule and Arrrghhh for all their work on the MSM72whatever branch of the project!
[Touch Pro2, Tilt 2 Android Development] fortunz:
I still haven't installed GBX0C, but I had sleep problems in GBX0B with the bundled .27 kernel. Have you tried any .39+ kernels? Bear in mind, there are different xdaledregimes, the original apk doesn't work with the new kernel, so to see if it does indeed sleep, you need to install the right one with the right kernel.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
I only booted the bundled .27 kernel only once, but switched to 3.3.4 as quick as possible.

It seems like Caldair is right: when Wifi is enabled the phone doesn't go to sleep. When I manually disable wifi, it indeed goes to deep sleep, according to CPU Spy.
[Touch Pro2, Tilt 2 Android Development] walter79:
thats normal.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Hm, no. Normal is the wifi shuts itself off after 10 minutes, and then you get full sleep.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Agreed, my wifi does not cause any sleep issues currently, although I rarely use wifi.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I tested sleep situation with the latest (today's) 3.3.4 No issue with sleep. WiFi deactivated until awake.

OM
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Arrrghhh and/or Detule, I've recently upgraded to the latest 0C build and latest kernel on both my phone and my sons. Booted with .27 and changed to 3.3.4 after that. When I attempt to reboot, it stopsat /init: line 448 can't create /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold: nonexistent directory.

There are also lines above that as soon as the kernel loads (I believe) that notes insmod: can't read '/lib/modules/lzo_compress.ko' : no such file or directory laong with the same for /lib/modules/xvmalloc.ko, ramzswap.ko. Any thoughts? I can't even grab logs because it won't boot again, keeps getting stuck on this line and I also can't adb in at that point although I've tried.

Edit: This happens on both phones.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Hmm, Greenpower should be disabling Wifi now, and according to CPUSpy, the phone goes in Deep Sleep. But the battery usage is still incredibly high when sleeping... The battery loses about 10% a hour when sleeping...
[Touch Pro2, Tilt 2 Android Development] detule:
That line (and the other ones you listed) are actually normal. No idea why it would be dying on you, I added the bluetooth commits last night so perhaps I mucked something up. Maybe someone else can verify it's not working for them either.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I was planning on looking for a new card, but the funny thing is, it's happening on both mine and my kids phones, and I can't boot back to 0B and it runs without issue. I'll try a new data.img and go back to 3.3.3 and see what happens. This happened on even the 3.3.4 from 5.1, maybe I'll try seeing if it happened before that as well and let you know what happens.

Edit: WTF.... Just created a brand new data.img on .27, switched over to 3.3.3 from 0429 and it was running fine. Loaded up only the essentials, worked great. Tried camera which froze so I tried rebooting, only to get stuck at that point yet again. And I can boot back to GBX0B without issue... I'm at a total loss...
[Touch Pro2, Tilt 2 Android Development] Raul^:
I'm trying to boot GBX0B and it reboot every time. After some comment "can't execute /init - no such file or directory it countdown from 7 and reboots.

I forgot to add rel_path but that doesn't change anything.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please use 0C.

Also, which kernel?
[Touch Pro2, Tilt 2 Android Development] agibby5:
I'm using GBX0C and 3.3.4.

Two issues that are majorly annoying:

1. I can't get the APN settings to save and thus MMS incoming and outgoing do not work. I'm using a CDMA handset on Sprint. I've reported this before but it doesn't seem like it was ever replied to.

2. My phone and my girlfriends phone never enter sleep according to the LED notification app. We experience about 12 hour battery life and most of the time we have been leaving the phone on the charger. I've had sleep issues since I jumped up to GBX0C. Here are my logs: http://pastebin.com/cyAikNmL

I'm surprised that no one else has similar problems.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1. The settings you are using are incorrect then... Only the correct settings will save properly.

2. 12 hrs, that's pretty good. Are you sure you're using the correct app? Have you checked to make sure there's no apps preventing sleep? Either way, if the phone was never sleeping I seriously doubt you'd get 12 hours of battery life. Sure it could be better, but that's definitely not bad.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Rhod400 using Sprint and I have no issue with sleep nor do I have any issue setting up the Sprint MMS APN, nor sending or receiving MMS messages. Set APN as follows:

Name: Sprint MMS (not sure it matters what you call it really)

APN: Sprint MMS (not sure it matters what you call it really)

Port: 80

MMSC: http://mms.sprintpcs.com/servlets/mms

MMS Port: 80

On the ports I really don't know which port is supposed to have 80 so I put them in both places and it works fine for me. I am sure one of them is unneeded, but I didn't care to try to figure out which one. Everything else in the APN should not be touched (MCC should already be 310 and MNC should be 00). Save the APN and then check it to use it. It should work fine. If it still isn't saving then you need to blow up your data.img and build and start from scratch because something is wrong with it.
[Touch Pro2, Tilt 2 Android Development] agibby5:
I am using the new app. It never shows as in a sleep state. I linked to the logs in the post. Will they help to determine what is causing the problem? Am I to assume that the phone sitting untouched should only last 12 hours? That's what I'm getting. I like running xdandroid, but I find that I'm not using the phone nearly as much and most days it just sits there. At night, it sits on the charger because at some point it died completely. There could certainly be apps that prevent it from sleeping, but I thought I went through and disabled any settings that I thought would cause this.

These settings worked for me. The ones I got when I Googled were different. Thanks!
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Can you start with a new data.img with no app installed except for getlogs and the LEDsleep app? Save your old one as data.img.bak so you can go back to it if you need to. If it sleeps then, then start adding your apps back one by one, attempting to get your phone to sleep after you install each one (might even go as far as rebooting android after every app install then see if it goes to sleep).

I will say with a lot of activity my very old original battery was only getting 5-6 hours on a charge, with minimum useage it was maybe getting 10 hours, so if you are getting 12 hours on a battery probably as old as mine you are in good shape. I just bought two new extended batteries that go for the TP2's (and the extended back for it), and now I am getting excellent battery life. Moderate usage and getting almost 24 hours on a 2100mAh battery overclocking also.

I am starting to think charging batteries on our android build might not be the best thing for the batteries. I know my old battery was old, but I think either Android isn't charging it fully, overcharging it somehow possibly damaging the battery, or android is allowing to deplete too low and ruining the battery that way possibly. That is just a hunch on my part. I have a standalone battery charger, and I charge these new batteries on it, but the one time I charged one of the new batteries in the phone with Android running, the next day the battery did not last as long as it had when I charged it on the external battery charger. That is the only reason I have a hunch something is awry with charging within our build possibly. Of course this is purely speculation on my part based on my experience.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
This is what I used for APN and never had a problem:

settings: APN

Name: internet

APN: Android

Proxy:<Not set>

Port:<Not set>

Username:<Not set>

Password:<Not set>

Server:<Not set>

MMSC:http://63.215.195.152/servlets/mms?X-SPRINT-MDN=(10 digit phone number)

MMS proxy:<Not set>

MMS Port: 80

MMC:310

MNC:00

Authentication Type:<Not set>

APN type:<Not set>
[Touch Pro2, Tilt 2 Android Development] detule:
Linux localhost 3.3.4-g69ce2c7 #1 PREEMPT Sun May 6 15:24:44 PDT 2012 armv6l GNU/Linux

<snip>

05-09 09:25:55.729 I/PackageManager( 1385): Unpacking native libraries for /data/app/XdaLedRegime_.27.apk

Wrong app.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not sure if you follow NAND development at all, but ACL has been working on this exact issue. The code that charges the phone depends on certain values, most of which are assumed on HaRET. ACL reverse-engineered the WinMo battery code, and on NAND he's been making great strides to resolving the battery meter issues where it jumps around, and the charging issues where it thinks it's fully charged after just a few minutes - obviously it's not getting charged fully in that short amount of time.

I'm not sure his code will make its way back to HaRET... perhaps on the newer kernels.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Yeah I had heard that someone was messing with it, but is it possible to get this code into GBX0C, or at least develop a better battery calibrator app from it? I am more concerned of draining the battery too low more than I am not charging correctly. Frankily though most of the time it isn't that far off from the phone being off and charging. If I charge it to what it says is full in Android then turn the phone off and let it charge, it usually my light turns green within 30-60 minutes at most usually sooner. Of course that might be more of a symptom of my old battery than what it really should be doing.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
just replugg it when it light up green (while being off!) normaly it loads properly then (atleast for me!)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
NAND is the future... I don't know how much of the goodness going into that is going to make it back to HaRET. ACL said that code wasn't really portable, and I'm certainly in no position to port the code back to HaRET...

Of course, you can run SCBS on HaRET - which should fix 99.9% of the battery calibration issues.
[Touch Pro2, Tilt 2 Android Development] detule:
I know at least one person who might disagree.

Nand has its advantages, but many value the dual boot ability that haret offers. Choice is always good.

Ideally, nand and haret development should happen at the same time. For this to be the case, we need to merge the kernel trees. Currently this is what we are trying to push with the 3.x kernels, to make them simultaneously nand and haret friendly. This way, kernel updates can be delivered at the same time via the autobuild to both sets of users.

This may or may not be possible, but we should at least try to make it happen. An encouraging sign is that there is almost no difference between the haret 3.x kernel and the nand 3.x kernel currently in testing in the gbx0c nand thread.
[Touch Pro2, Tilt 2 Android Development] Caldair:
+1. I love the flexibility of having WM/Android at my disposal at any given time! That is just about the only reason that my rhodium isn't gathering dust right now.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Can you tell me any more about SCBS, or point me to a location to find out more?

Thanks.:o
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Unless that one person is me, add one to that total. The dual-boot, plus the safety net, are compelling reasons for me to stay on SD.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
http://forum.ppcgeeks.com/android-t...sting-scbs-improved-battery-meter-system.html
[Touch Pro2, Tilt 2 Android Development] walter79:
Boot gbx0C kernel on CM7.2 and ICS!

Detule can you add this to your init.gingerbread.rc

service netd /system/bin/netd
socket netd stream 0660 root system
[COLOR=Red]socket dnsproxyd stream 0660 root inet[/COLOR]
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Count me in as one that will always stay SD Dual-boot. I don't use WM almost at all, but it is good to have just in case everything craps out on Android (like permission errors where you can't open any app, market, terminal or anything to fix), and you are nowhere near a computer to run adb shell to run the fix_permissions script. You are screwed on NAND if this happens. Now obviously on NAND everything shuts down correctly so you probably are less likely to have corrupted file systems.

Detule, are you saying that I could potentially take the testing kernel in the NAND thread and try to boot GBX0C on it? I am trying to find out what you mean by "almost no difference".
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Unfortunately it looks like we have to use a kernel that is a year out of date to use this, or is Wistilt2's kernel pack part of the autobuild kernels?