yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] mowglilp:
I wasn't asking you to assume, you just can't set maximum setting and have auto-brightness as well, once you check that box, the setting becomes unavailable.Anyway, i don't want to argue with you, but please take more time and read what i have to say because in my very first post i stated i don't know how to get those logs, nevermind that because while we were arguing for no reason i found out, however the app crashed on me, so i'll try to retrieve the logs some time later cause now i need a stable platform so can't run XDAndroid.

The kernel from FX06 is named "2.6.27.46-01312-gea57c39".Like i said before, replacing data.img from GBX with the one from FX06 fixes the issue.The FX07.1 or FX07 bundle doesnt fix this problem either, only FX06.I will try and obtain those logs.So i think the problem with the screen comes when you either put the phone in stand-by, or when the screen becomes darker when phone enters idle.

Oh, and another detail, the brightness isn't always the way i set it, sometimes when i power on the phone it's so dark it's barely lit, puting it in stand-by and then power on again sometimes fixes it, or moving the brightness slider

And please understand that i didn't come here to complain, i want to share my problems with XDAndroid and maybe, with your kind help and knowledge, work something out as i know RHOD100 are a pain and some have issues that other might not.If you want me to praise XDAndroid i can do that as well, but we all know how awesome is, what a great job the devs and everyone involved did.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't swap data.img's... That's only going to introduce a host of other issues.

Please try the build with the old kernel.

Please read the FAQ, there's even an entire topic/wiki page on logs.

I don't think any other RHOD100 users have this issue, so I'm pretty sure you did something to introduce it to yourself. Triage it, break it down. Figure out where you went wrong.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
I got the log files, hope this sheds some light on my problem.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So what happens when you run the newest .27 kernel on GBX? What about that old FRX kernel on GBX? This is all part of triaging...
[Touch Pro2, Tilt 2 Android Development] mowglilp:
Nope, same issue with the older kernels as well.Just tried it and works just like the 3.3.36, on booting brightness is great and setting it to max blinds me :) however as soon as i send my device to sleep and wake it up again, it starts with the low brightness setting but the slide bar is at max and reajusting it to the maximum is pointless.You know how it is on any phone when you leave it on idle, it doesnt just go into stand-by, the screen dimms first and then it shuts off, that's how the screen looks to me, it's like the phone is in idle all the time.
[Touch Pro2, Tilt 2 Android Development] detule:
Hi,

In an earlier post you mentioned gbx + data from frx06 fixes your brightness issue. Just to be clear, which kernel were you using in this setup (I realize that the log you posted above has .27).
[Touch Pro2, Tilt 2 Android Development] r0mka:
Ok now i have tried to run FRX as you said and for now i have found that it runs with kernel .27. The latest that was running was 20101204_005141, but it did not produce any sound while calling and have frozen when i tried to use speakers while calling. I've tried a bit later kernel - .27 20110317_184049 and it kernel panicked. Latest .27 kernel, or from the bundle did not worked. .35+ kernels did not worked too (well at least the latest ones). Where does that lead me too? Should i try to run FRX 100% working and then do something with GBX or what?
[Touch Pro2, Tilt 2 Android Development] mowglilp:
@detule: the kernel i was using in the GBX was the one from the bundle:2.6.27.46-01365-gc8b9a4c, the only thing i took from frx06 was data.img.

@r0mka: had the same issue with FRX07 and GBX bundle pack, i took the GBX bunde and replaced the kernel with 3.3.36 and it works fine.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please quote posts so we know where you're coming from. IIRC you're the guy who couldn't run anything except one particular .35 kernel. Now you can't even run the .35 kernel?

Just pillage and start over. Format the card using the HP Tool. Full format, FAT32. Then redownload the bundle in the first post. Do not backup/restore anything. I want you to start completely over, fresh.

This makes no sense. The data.img itself has really no bearing on the screen brightness...

Can you provide logs from this functional setup? I guess if it works, then why fight it. Sounds like you solved it, in perhaps the strangest way possible. As far as I know, you're literally the only one with this issue so I'm still saying there's something you did to the setup that caused this. No clue what.
[Touch Pro2, Tilt 2 Android Development] r0mka:
I did that. My process was like this:

one last time tried GBX with .27,3.x kernels - no luck, .35 kernel - boot. Than i've copied all the info from sd card (pictures, music etc i need) to pc and tried to do a full format FAT32 with your given tool twice - both times no luck - at the very end it threw an error that format cannot be completed (it's a different sd card and i'm running win 8 cons.preview). After both failures tried fast format FAT32 and it worked. Than i've copied everything from FRX bundle with no changes, used RHOD100 startup and restored all photos and music back to sd card and tried to boot with no luck. I've changed kernel and modules to the latest and to the second latest (20120227_213021) both .27 kernels. Tried 3.x kerneles, tried some .35 and .39 kernels and with all of them no luck. Then just to check i've tried some old kernels as i mentioned (20101204_005141 and 20110317_184049) and posted my experience to xda. Is the diskpart tool useful for this purpose? I could try to do a full FAT32 format with it.
[Touch Pro2, Tilt 2 Android Development] Slipdoozy:
ive had problems with certain pictures and music and movies not agreeing with sdcard builds... all i can say is "just" install only [TESTING] XDAndroid GBX0C 2.3.7 Build. forget about all your music and pictures. full format with the HP tool or ive used MiniTool Partition Wizard Home Edition 7.1. by the way you are formatting just the card? (i mean not in the phone). once you have successfully done the prior. with no errors and fully working [TESTING] XDAndroid GBX0C 2.3.7 Build. then add some pictures. try that, without errors, then add more. at some point you will find a picture or music that doesnt agree with android.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Quick Format is probably the worst thing you could have done. At this point, find a computer where you CAN correctly format the thing and use that. Don't just say "HP Tool doesn't work on my computer" and give up and do the wrong thing despite being told repeatedly that Windows's default formatter does it wrong. You're just wasting everyone's time. Find another computer.

Or heck. Find a Linux LiveCD, boot to that, and format the SD card using mkfs.vfat.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This x1,000,000.

r0mka, I told you to use the HP Tool. You said it didn't work? Either you ran the tool wrong, your SD card is bunk, or something else... Not sure what else. I would try another SD card.
[Touch Pro2, Tilt 2 Android Development] r0mka:
it works fine with usb thumb drive but ir did not worked with two sd cards. I will try linux now then. After that if everything goes well i should try GBX not FRX yes?
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Arrrghhh, are you cdma or gsm? At the moment I can't see anything else seperating us besides the device.

Would you mind trying to get a location on gbx0b with the included .27 kernel with gps disabled?

This Is persisting accross multiple fresh data.img's and on partitioned too. As I say, works fine in froyo.
[Touch Pro2, Tilt 2 Android Development] nickleby:
I can't get my location using the Wireless Netowk too! :confused: I got the same message: "Your current location is temporarily unavailable". I don't even get the agreement dialogue when you select "Wireless Network Location" as in Froyo
[Touch Pro2, Tilt 2 Android Development] ryannathans:
FIX!

Stinger22 kindly messaged me with the solution to the location issue.

The problem lays within the google apps package.

Grab the bundle gapps-gb-20110828-signed.zip from this site: http://goo-inside.me/gapps/

Extract the zip, NetworkLocation.apk needs to replace its partner in /app

I just ended up extracting everything inside the system folder to replace it's outdated partner from GBX0B.

Eg, I extracted system/app/* to /app/ system/etc/* to /etc/ and so on...

But from what I understand, only the new NetworkLocation.apk is needed.

And after booting back into GBX0B, a working google maps, network location at last!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cool, thanks Stinger & ryannathans... I guess the gapps package needs some tweaking.
[Touch Pro2, Tilt 2 Android Development] SgtMac02:
Ok, here's an update to the wifi issue from yesterday. Twice so far today the wifi was not connecting, so I had to go into the Wifi settings page. I did not actually have to turn wifi off and on again, I simply had to wait a minute there for it to reconnect. First was this morning when I got to work, it still showed me as connected to my home wifi (miles away) and when I waited for a minute after viewing that screen, it picked up correctly. Then later in the day after having walked away from wifi signal, I had to do the same thing to get it to connect again (showed not connected until I went to settings and waited for connection). Then a third time while still sitting at my desk well within range, I picked up the phone to try to do something and it was disconnected again....as though the wifi had gone to sleep. But I still have it set to always on. It wouldn't reconnect until I went to the settings screen and waited a few seconds for it to connect. I grabbed a log that should contain ALL of this since it looks like it goes back to last night's reboot at midnight(ish). I hope this might help:

http://pastebin.com/Uk2iRs3P

Edit - Update:

Here's another log file. I was sitting at my desk well within range. Went to check my google voice and had no connection. Went to wifi settings and it still showed me as connected. Had to turn wifi off and then on again to get back online.

http://pastebin.com/vLePpGye

Hope something in one of these logs helps you guys out. It's all Greek to me.
[Touch Pro2, Tilt 2 Android Development] walter79:
Thanks for this build. With .27 kernel my wifi works. Networklocations works with fix. GPS did not work. I will do some test tomorrow.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I've got a friend with RHOD400 using the stock .27 kernel who had his audio cut out to be replaced with static, I've had him install getlogs and he promises to pull them next time it happens.

I had what seemed to be a repeatable case when I first installed GBX0B, though I didn't try it many times. I used alarm clock xtreme to play an mp3 alarm and it seemed to come up static and loud pops each time. That was on the original .27 kernel, but I've moved on to 3.x since. I'll go back to .27 this weekend, see if I can get it to repeat and post logs myself.
[Touch Pro2, Tilt 2 Android Development] webxplore:
Just installed GBX0B on a clean formatted card. Everything's fine except there is no ring sound (tried multiple ringtones) for incoming calls. Anyone experience this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I have the same device, no problem here. Can you preview them in the settings section?
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Nothing much to say here, just uploading my CSV files. RHOD500 using SharkieROM. I think I'll try to compare the various CSV's in the coming days. Still settling into our new house.
[Touch Pro2, Tilt 2 Android Development] webxplore:
I can preview them fine under settings. Let me start allover and try again.
[Touch Pro2, Tilt 2 Android Development] SgtMac02:
This might be in the wrong thread, but it happened while running this build, so I thought I'd start here....

So, yesterday afternoon on my way home, I was in the middle of a phone call when my phone took a complete **** on me. It dropped the call, and when I went to look, it said I had no service, then a few seconds later, it shut down completely. I could not reboot it even after plugging into a power source (I thought maybe the battery died). After being plugged in for a while, I was able to boot back up into WinMo, but now when I try to launch Haret, I get the following error:

"The file "Haret" cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file."

This morning, I went in and copied over all of the files again from my hard drive and replaced them all, and I still have the same issue. I get the same error when trying to launch the Haret file from either of the other two Froyo builds that I've also got on the card. Wondering if any of you have any thoughts on this. :(
[Touch Pro2, Tilt 2 Android Development] gjvk70:
This happens to me only when still connected to my PC with the usb cable. Could this be your problem?
[Touch Pro2, Tilt 2 Android Development] helicopter88:
Could you try to launch another wm app?
[Touch Pro2, Tilt 2 Android Development] vinceweis:
If I recall, I got this message when the rel_path statement is not set or wrong in the startup file. I have had similar problems if my sd card had partitions and I did not add no_partitions to the startup file.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WinMo issue. I can't remember the solution tho... Search around, I know others have had it, and it's a problem with Windows Mobile not wanting to run certain unsigned applications... such as HaRET.....
[Touch Pro2, Tilt 2 Android Development] jigwashere:
Have you tried reformatting the microSD card before copying the files over? Since this happened when your device crashed, I wonder if something on the card became corrupted.

There's also a registry setting you might consider changing: http://xdaforums.com/showpost.php?p=3312617&postcount=5

I'm interested in being a tester, but don't know where/how to get started or help. I'm new to XDAndroid, and so far loving it on my (stock Sprint WinMo 6.5) TP2. I just installed GetLogs.apk and will try to figure out how to use it.

I don't think you're terribly interested in issues I'm having with apps, is that true?

Sound works well for me, including through 3.5mm plug. WiFi tether works well, but when turned off I get a freeze and ultimately crash (or pull the battery). Do you need any BT tests? If so, what would you be looking for?

Reading the post above about GAPPS, I am unable to locate NetworkLocation.apk on my microSD card. Did I miss an install along the way? I do know that Google Sky Map shows me sun when I look up at the night sky, but I suppose that could be caused by any number of issues (clock, GPS, user skillset, etc.).

Anyway, I'm happy to pitch in if you like!
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
^ His appears to do the same thing, so it's up to you if you want to muck around in the registry or go through the process of getting the cab on your phone.

http://xdaforums.com/showpost.php?p=3973249&postcount=1

Link has a cab that allows you run unsigned apps (if that is in fact the issue)
[Touch Pro2, Tilt 2 Android Development] jigwashere:
I paired my headset, and but was unable to pair a keyboard.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You're trying to pair a BT keyboard... on a device that already has a physical keyboard? lol.

BT probably still has some work, but I don't know if we'll be able to get it done.... Logs are obviously going to help, but honestly BT might be a lost cause.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try whatever you want. If you're posting in this thread, you should be using GBX.

As for 2 SD cards not working, I'm betting you're doing something wrong or the card is set to "read-only".

Are you using some SD card reader, or your phone? I just put my phone (in WinMo) in mass storage mode so the card just shows up as another drive in Windows. Then, making sure you run the HP Tool as "administrator" (if you're on XP don't worry about this) do a full format, FAT32.
[Touch Pro2, Tilt 2 Android Development] r0mka:
I will go with GBX. I'm using an adapter you know the one in which you insert a micro sd card and it makes it into normal size sd card, for which my laptop has a reader. And yes the tool is set to run as administrator otherwise i can't start it. I will try to format with linux tomorrow and see where it goes, try some experimenting with kernels maybe ill find the right one. It is nice that the developer is willing to help and spend so much time on this so thank you again.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm no developer...

But at any rate, might want to try without the reader. Just use WinMo as I suggested previously - I almost always format my cards this way (or I use a mSD -> USB converter).
[Touch Pro2, Tilt 2 Android Development] mowglilp:
I was wrong, replacing data.img didn't work, at that time (4:00AM) it seemed to work.... and it did, but i didn't get the chance tu turn off the phone and see that it doesnt light up as bright once i turn the phone on again.

Anyway, i tried the .27 kernel, new root file, new init file (latest from xdandroid.com) and they all failed.Before doing these try-outs, i formated the card with HPtool and also did a hard reset on WinMo just to make sure no tweaks i've made interfere with XDAndroid.

So after trying pretty much everything that came through my mind, my only hope is that one of the devs has a clue.I under-estimated this issue, i tought all it would take would be a simple edit in a file or a replacement.Oh well... just have to wait for a new release.

Thanks for your help so far.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nothing is going to get fixed if there is some issue on your side of things.

As I've previously stated, other RHOD100 users do not have this issue (that I'm aware of...)

At any rate, did you try GBX on the old kernel that you said worked like I asked? Assuming it does, please pull logs from that.

I'm honestly not sure what could be the issue. I really want to be clear, that you cannot have auto backlight on in WinMo.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
Tried the old kernel with GBX and wouldn't even boot.Autobacklight is not set in WinMo or Android.The problem is strange indeed, it's just not waking up the screen (phone) to it's full brightness once i press the power button.As i said above, this problem doesn't exist right after booting, it works perfect, only after i put my phone in stand-by and power it on again, only then problem starts... so it can't be a bad setting in WinMo, hardware issue or even a bad install of XDAndroid.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm so glad you've ruled everything out :rolleyes:

I guess it's just impossible to fix then, eh? Oh well.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
I wouldn't say impossible, if it worked with FX06, it should work with the newer build, we just can't figure out what it is.Thanks again for the advice.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, which makes me think you're doing something wrong... which you've ruled out. So that leaves... yea, nothing evidently. Good luck.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
You said nobody reported this issue...

http://xdaforums.com/showthread.php?p=25860587&highlight=brightness#post25860587

"Initial observations. Installed onto my TP2 cdma with no issues. Was able to call out no issues. Found that when the system first booted the brightness level was at 100%, but as soon as some function caused the lcd to dim (or turn off) it stuck at low light settings. Reset function hangs the unit, power off rebooted it. Wifi is good. My screen needed to be calabrated so I triedhttp://rhodium-nand.googlecode.com/files/tscalib.apk, and it seemed to work. Overclocking seems to be disabled. Tried to get a gps lock, but didn't happen. Didn't spend to much time trying. Did try leo's agps injector too. Good start."

"WIFI works for me. The screen is a bit dim, and as reported in the first post, brightness control doesn't work. I tried to switch to Tilt2 keyboard by cp /system/etc/keymaps/tilt2/* /system/etc/keymaps/default, but that is obviously the wrong way to do it since it didn't work.

Screen orientation switching works. I haven't tried GPS or GSM yet."

So there is indeed a problem.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The first half of that text was my post, and the issue was resolved by the first update that was released where the manual auto brightness was fixed. The only screen issue I am having is the known issue of auto-backlight not working correctly. Have you not installed the ril and kernel updates? There have been 3 I think total.
[Touch Pro2, Tilt 2 Android Development] mowglilp:
If you would be so kind as to put upload those files, i would be thankful, or give me the links please, i tried the latest (or what i think are the latest) files and it didn't work, maybe that's where i went wrong so please give me some details.

Thanks and i'm glad you sorted it out for your phone.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Welll... Are you aware that all the text you quoted came from another thread.:eek:

[ROM][NAND] GBX0* + 3.3.x kernel

If you are aware of that, then I would suggest you look at the first post of that thread for all downloads relevant to it.

As far as this thread is concerned. I never had any screen issues with this SD build. The auto brightness can sometimes take a few seconds, but it is not that big of a deal. I have no complaints to file.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This ^^.

mowglilp, I'm not trying to be rude to you. Please don't drag crap from other threads to "bolster" your argument. There's some issue on your end, and you seem unwilling to admit that.
[Touch Pro2, Tilt 2 Android Development] besho2222:
arrrghhh, please help me choose the perfect distro, I downloaded this distro and also the latest kernel but the OS is so laggy, I tried the whole brainstorming ideas in the thread here on XDA, it does work but not that gr8, what is your quick advice for RHOD210 as I have to travel tom. and I wanna a perfectly -or near- working android for my medical school, as medical programs are much better on android than on WinMo
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Honestly then buy an Android device. This thing has an adreno130, to run most of the newer graphics stuff you need at least 200+.

Can't overcome hardware limitations with software. NAND runs a bit better to be honest, but it's not like a brand new phone... Check out the OMGB thread, it's quite good.