yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, I was pretty scant in my details...

For the rootfs, just burn that partition. I wouldn't actually try shoehorning the rootfs into that partition, unless you really feel like doing it. I never did :p.

However, loop mounting is a pretty standard thing. I figured if you had any Linux experience, you'd know how to loop mount ;).

So plug in the SD to your Linux box. Mount all ze partitions. Then, assuming you have a copy of the system.ext2 and data.img files on your Linux box, loop mount them:

mount -o loop /path/to/system.ext2 /path/to/mount

/path/to/mount can be anything, just make sure it exists. I have an xda folder off of /media that I throw loop mounts into. I think there's a /mnt/loop as well if you want... Again, doesn't really matter just so long as it exists and isn't already being used ;).

Copy the junk over, rinse and repeat for the data.img. Just make sure you keep track of which partition you're pushing the files to - system.ext2 goes to p3, data.img goes to p4.

You can delete the data.img and system.ext2 files if you wish as they will now be on dedicated partitions...

I hope you read my post on C10 card issues too. hyc, one of our premiere developers, confirmed this suspicion by unintentionally frying a C10 card... Dedicated partitions have their advantages, but I don't know if they're resolve your issues. Good luck.

Edit - also, if I didn't drive the point home last time... This is a COMPLETELY unsupported configuration...
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Thanks for the info Arrrghhh. I was reading up Linux to get more up to par with it. I think I got it figured out now. I realize it is not supported. I just wanted to try it out. It is easy enough to go back to normal if I don't like it! :)

As for the C10 card, my 8GB Class 4 (or 6 can't remember) was acting up, which is why I went up to a 16GB Class 10(thought it was a 32GB, but I was wrong). I bought it for dual uses. As soon as I get a new phone I plan to use it for my new digital camera that captures 1080p/60p movies and 16MP photos, and I need all the SDcards I can get. In the meantime, I think I am just going to have to deal with the C10 card until I get the new phone, because I don't have a backup microSD at the moment, and really have no use of buying another microSD card, just standard SD's since it sounds like the Galaxy S3 is not going to have a microSD card slot.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You *could* actually format a 16-20MB or so root partition if you really want to. I never did with FRX because we were still doing so many patches to rootfs it would be too much hassle to update. So in a typical setup, rootfs is still loop mounted, while system and data are on real partitions. Still works well that way. If the rootfs isn't changing much any more, it might be worthwhile to put it on its own partition now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't see the point of putting the rootfs on a dedicated partition tho - is there an advantage to running it on a partition, other than to just eliminate a loop mount?

I see the advantages of putting the data.img or a dedicated partition... Just not the rootfs.
[Touch Pro2, Tilt 2 Android Development] kk0813:
I am using att tilt2 and installed GBX0B on 32gb class4 microsd card. every thing works fine other than battery. Battery drains very fast. I installed the led indicator included in the apps folder, and the led is always red/orange and does not show green. wifi, sync, data, gps are all turned off. I changed to airplane mode in windows mobile before hitting haret.exe.

Froyo 07 is working fine including sleep.

To see how it works with other kernels I replaced the two files included in the auto build kernel zip. But for all kernels (other than that's included in GBX0B bundle) included in the first post, I am getting Kernel panic - not syncing: ufs unable to mount root fs on unknown-block(0,0) and stops.

I formatted the microsd card with hp tool fat32 and still does not work with any other kernels.

Do I need to get a different rootfs ? I searched the forums and one person had the same issue but he replied back that it worked after card format, but not working in my case.

My main idea is to put the phone in sleep so that the battery last for few more hrs.

Can some one please provide a solution. Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you're using EVERYTHING from the GBX0B bundle? That means HaRET.exe, startup.txt? I had to change some things and if you're pulling ANYTHING from FRX then you won't be able to boot the newer kernels.

As far as not sleeping goes, does this happen on a completely fresh data.img in airplane mode? If so than I'm baffled, as I've never had that problem. 9/10 it's an app causing the no sleep condition.
[Touch Pro2, Tilt 2 Android Development] kk0813:
I took ts-calibration and startup file from the froyofrx07. Haret.exe every thing else is from gbx0b.

After your question, I just replaced the startup from the rhodium folder tilt2 from gbx0b and deleted data.img file. And using the same kernel and included in gbx0b. I am trying to see if it goes to sleep or not. Regarding using the other kernels rootfs mount error should this solve? or do I need to get any other rootfs? As I mentioned I am able to boot with 2.6.27 kernel that is included in the bundle but not with any other kernels that's posted in the link provided in the first post.

Thanks
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Your issue is in bold. Compare the 2 startup's, I had to add some lines to the GBX0B startup.txt ;).

rootfs has little (probably nothing) to do with the kernel booting. You are fine with the rootfs that ships with GBX0B.
[Touch Pro2, Tilt 2 Android Development] kk0813:
Hi, thank you. So startup file was the issue. Now I replaced the startup file from the gbx0b bundle and even kernel 3.3.1 from auto build booted fine.

Still the sleep issue is there. Before booting I deleted the data file. The led indicator does not change to green. Any way every thing works great. Thank you. I did not realize it could be startup file.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I've had a sleep issue since the newest version of GBx0B (see here and several more posts over the next few days). I made some minfree changes and eventually noticed that it does start sleeping after 12-48 hours, though I'm unclear on whether the minfree changes made any difference there.

I've noticed others report serious battery issues and tried to get them to use the led debug, but I haven't gotten them to confirm the sleep issue. I'd love to have more confirmed cases, might be easier to track the issue. And with HTC kicking keyboards, I no longer hope for a successor, so XDAndroid is my only hope.
[Touch Pro2, Tilt 2 Android Development] kk0813:
Thank you for the link, actually I read that when I first got this problem, but I went through the pages again and followed all the steps you did to find the issue, but for some reason my phone does not show green. Froyo frx07 sleep well and shoes green (gbx0b seems much fast compared to froyo) and even the battery last till end of day for moderate use, I am currently using gbx0b with kernal 3.2. still have to see how the battery goes. With the kernal that's included in this build, I charged the battery to 100% and left it over night and in the morning it was 10 % left. Day time with moderate use it lasts only till half day. Not sure how this goes with 3.2 kernel.
[Touch Pro2, Tilt 2 Android Development] detule:
Fortunz I've seen your posts in this thread so I am a little late responding to this.

In your original post you had wifi on in .27-> the device doesn't suspend when wifi is on this is a known fact across kernels. Later on you posted a 3.2 log here. This log actually shows your device going into full suspend -> unfortunately you did not have LedRegime turned to sleep debugging so you probably didn't notice. On the new kernels, what you want to see in your kernel log are lines iike these (taken from your 3.2 log)

02-08 14:31:38.660 INFO : PM: late suspend of devices complete after 1.983 msecs
02-08 14:31:38.661 INFO : PM: early resume of devices complete after 1.708 msecs

The first is the last line printed before the device suspends, the second is the first line printed when the device resumes. Don't be confused about the time-stamp -> it is not updated immediately when the device wakes up, rather it gets updated when it gets to this line in your log

02-08 14:31:38.770 WARN : Restarting tasks ... done.
02-08 14:34:50.041 INFO : suspend: exit suspend, ret = 0 (2012-02-08 20:34:50.041014840 UTC)

showing that your device was in fact in full suspend/power collapse for about three minutes.

In future efforts, when using +.39 please use this version of XdaLedRegime (different from the version that works for .27).

But i think you got the gist of what arrrghhh was saying -> if you are still having issues it's more than likely issue particular to your device -> as in sd card you are using, apps you have installed, etc. The 400 and 500 are basically the same device and my guess is other would have seen this if it was a kernel failure.
[Touch Pro2, Tilt 2 Android Development] fortunz:
Even before I was able to confirm that 3.2 eventually slept, based on battery life. But .27 does that too. With the new ledregime (thanks for that), it looks like it is capable of sleeping immediately after boot, not just 12-48 hours later. The old log you looked at (which were taken shortly after a boot) appears to confirm that, and my two boots this morning do as well. Yay. :) 3.2 rules

However, for the record, the problem is real for the bundled .27, however sporadic it may be. My second .27 log has no wifi (or any other radio) on from boot to the taking of the log. It was done on a brand new, clean data image. I didn't install apps other than gets logs and led stuff, I didn't even sign in to google. It consistently failed to sleep across 3 sd cards, 2 of which were formatted with hptool. And others have experienced the problem, they show up complaining of newly horrible battery life since switching to gbx0b, but then, as many complainers are wont to do, they fail to follow up by turning on ledregime or providing logs. But they are out there. You just have to believe ;)

I'm defensive only because hearing "it's your apps or your sd card" again is... bleh. I went to extremes to rule out my particular setup and offered to go farther if pointed in the right direction. But I do appreciate you checking on it and responding, and tipping me off on the new regime app. @kk, grab that apk, and hopefully you too will find 3.2 is indeed behaving well.
[Touch Pro2, Tilt 2 Android Development] detule:
It's fine, I should have clarified my post to say that if you are experiencing suspend issues on .39+, in all likelihood it's something particular to your setup. Truth of the matter is, I haven't used .27 (except sporadically to test things) ever since jonpry and WisTilt2 started working on .39 (it's been almost a year now!) so I am no authority to say what works and does not work there.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is really the "issue" folks - which I don't think is an issue at all, it's how development works in the open source world.

The devs don't want to work on .27 anymore - can you blame them? But it's the most compatible kernel, so I kinda have to bundle it. I try to encourage RHOD users to hop on the new kernel train, because that's where all the fixes are going. I mean c'mon, how many phones run 3.3.1!?!? :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
How about this. If you guys want to use .35+, post in detule's thread. I really don't want kernel questions about wifi and bt not working, that NOT THE POINT OF THIS BUILD.

We're trying to sort out any issues with the BUILD, as in userland. So please folks, test on .27 and report here. Test on another kernel, don't post here!!! Thanks.

lol, newest bundle has the GLES. :rolleyes: I know I said that, but that would require you to read it.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
hey arrgghh!!!!

i'm not sure if this was addressed, but some of the startup.txt's have a slight typo!

usually it's like

but some of them look like

!!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Crap. I'll look over 'em. I did a blanket replace, and tested it before I did the replace... so I kinda assumed they all went well lol.

Thanks for pointing that out.
[Touch Pro2, Tilt 2 Android Development] SgtMac02:
So, I downloaded this yesterday and am running the stock bundle as posted. I'm running it from the root of the SD card on a RHOD500 on ATT's GSM network. (I did have a rather significant amount of trouble getting my CSVs, but that is another story) I'll give you my observations so far...

Seems like most things are working fairly accurately. Camera seems to work fine.

Wifi connects and functions properly, but seems to require me to manually turn off wifi connection and turn it back on in order to reestablish functional connectivity with my network even if it says I'm connected.

I'm not using any data plan, so I have no insights as to that functionality.

Bluetooth worked correctly for phone calls with two different devices. It did not, however, work for the media playback through my Jabra Clipper. I'm guessing this is probably known, but wanted to make sure you were aware.

Also, (as you might be aware) I tried using headphones with the 3.5 jack and I can hear everything, but it disabled the mic so I couldn't use the headphone jack during calls as the phone is capable of in WinMo.

I tested out the GoogleMaps issue you mentioned, and I too saw some artifacts throughout. Didn't seem to be associated with anything in particular, and they shifted locations as I zoomed, so they weren't tied to anything on the map.

I also noticed that overall, the phone seems a bit more sluggish than it did in previous builds, particularly in relation to applications. They seem to keep wanting to throw up the Force Close/Wait dialogue. They aren't crashing out, and if I wait, they continue to work, but it just seems like the apps don't run as fast as they did in Froyo.

None of these are complaints, and I'm not expecting anyone to jump through hoops for me. I just wanted to update you on my experience with testing this build and hope that my experiences might help in some way with the awesome stuff you guys are doing. If I can do anything to help, I'd be glad to. Keep up the great work, and thanks a million!
[Touch Pro2, Tilt 2 Android Development] fortunz:
I won't speak specifically to applications, and of course different devices/uses can vary, because I haven't been using as many on GB, but I've found the system overall to be more responsive than froyo was for me. When I first boot into FRX7, it used to hang a lot, to the point where I'd intentionally not use it for an extra 5 minutes or so to let things shake out. Ditto when it started syncing. In GB, the device becomes responsive much more quickly. I can use it comfortably as soon as I see the lock screen.

Have you checked out the performance tweaks thread? You might find something to ease your troubles there. I recommend considering supercharger.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, I never use wifi. Is this an old bug or new?

One-offs are going to be difficult, but I guess it could've been the application. What were you using to play media? Logs are going to be helpful here.

Look around the Android forums... this is actually a bug with Android, not our port. There's all sorts of native Android users complaining about this (saw it in my gf's Optimus S forums) so it's hopefully something that can be fixed, but it will be a hack since again this is an Android bug.

Detule said downgrading Google Maps fixed the issues. I'm guessing v6.x of Maps just doesn't jive on old devices...

Hrm. I did notice it was sluggish, but I've been using OMGB for a while, so I figured my basis for comparison was off. All I have to suggest is...

This.
[Touch Pro2, Tilt 2 Android Development] SgtMac02:
Well, wifi was a little flaky in a similar manner in the last build too. It seems to be a bit intermittent. For example, I have wifi at home and at work. I connected to my work wifi. It worked fine for the short time I was here after that, then I went home and connected to home wifi for the first time. Later that night I went to try something again and though it still said it was connected, I had to disable and enable the wifi again and let it reconnect in order to actually get it to work. Then when I came back to work today, it automatically showed as being connected to that network, but had to manually disable/enable again for it to work. Then a little while ago I walked out of range (across the street) and came back and it reconnected fine on it's own and kept working...I don't know if there is anything I can do to help isolate the issue or if there are any logs that would help with this, but if you want any more details or observations of the behavior, I'd be glad to help. As mentioned, I have no data plan and use solely wifi, so I can test all sorts of scenarios if it will help you guys out in the dev process.

I use the built in media player. I might be able to test it with a different a2dp device later if I can borrow one, but I suspect the results would likely be the same. I think the issue is more likely feature related (transmitting media audio playback) than device related (Jabra Clipper issue). So...how can I get you the log you'd need in order to help with this? I'm still really new to this stuff, but would like to help in the small ways that I can.

Good to know it's a known issue that might be being worked on. I know it's probably low on the priority list, but knowing that it spans all Android, that gives me hope that someone might find a fix for it.

I'd love to try to NAND flash, but I'm afraid to take that plunge. (BTW, what does OMGB stand for?) Also, it seems from reviewing that thread that some of the key features I want don't work so well there yet. Specifically, I listen to a lot of audiobooks on my phone, so I need the headphone jack working correctly. I'll keep waiting for that build to get better and I'll try the other speed tweaks in the meantime.

Thanks for the fast and detailed reply. You do great things here and have the patience of a saint.

This.
[Touch Pro2, Tilt 2 Android Development] marcopolo:
Screen and Google Account problem!

Even I am facing the same problem.:confused: I have replaced the kernel with the latest 2.6.39 which has resolved the phone hanging issue (during the call) but at times, my unlock screen won't come.

Also, I found a strange thing that I cannot add my google account in this ROM, due to which I cannot access Market place neither my gmail mails or contacts :(:(

I tried adding my gmail account using Exchange Settings but it is not taking that. Any solutions to this? I have updated my CSV files.
[Touch Pro2, Tilt 2 Android Development] detule:
No idea what you are saying about the unlock screen. When does this happen, before a call, during a call, after a call? I think it's been mentioned numerous times, use GetLogs to capture the issue.

Settings -> Accounts & Sync -> Add account -> Google -> etc. this approach doesn't work?

---------- Post added at 06:58 PM ---------- Previous post was at 06:48 PM ----------

Not sure if this will help but you can try Settings->Wireless&Networks->Wifi settings->press menu key->Advanced->Sleep Policy->Never

Normally I would be concerned how this affects the device suspend cycle, but I am fairly certain that the device does not suspend at all when wifi is checked ON anyways (someone correct me if I am wrong).
[Touch Pro2, Tilt 2 Android Development] marcopolo:
Well, this happens when I boot my phone on Android. I was taking about the lock screen, my bad... :(
[Touch Pro2, Tilt 2 Android Development] detule:
Absolutely. Every time you migrate to a new system.ext2 you should start with a fresh data.img.
[Touch Pro2, Tilt 2 Android Development] walter79:
My Wifi is not working with. 35 kernel. Rhodium 100.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess you can try to force always on wifi like detule suggests. Otherwise, I guess you can also try to force it on using csipsimple (I heard this works, for whatever reason).

If you don't want to keep wifi always on, I would try to pull logs of the failure. So turn on wifi, use it, make sure it works. Let the device sleep, don't touch it. Wake it up, try to use the 'net again. If you're connected but it fails, pull logs. Perhaps we can figure out why..

Probably. Logs are going to help here for sure.

http://xdandroid.com/wiki/Logs

rpierce99's app makes it quite easy, and it's located in AndroidApps\Other. If not, the manual method is effective - but a lot more work. Sometimes necessary if you need to leave logs running...

That's nice, I don't think wifi is enabled in that kernel. Please, if you're testing .27 report in this thread. If you're using ANY other kernel, use detule's kernel thread. Seriously, this is distracting at best.
[Touch Pro2, Tilt 2 Android Development] SgtMac02:
Thanks arrrghhh and detule.

I actually had already set wifi sleep to "never". As I mentioned I don't have a data plan, so I rely solely on wifi...therefore I wanted it on all the time. It does not do pretty things to battey life. I got less than a full day's use out of it with the old builds. I haven't fully tested in this build yet.

Also, I tested the bluetooth a bit further. I was able to test with a friend's Altec Lansing Backbeat headphones. They worked on the first try. So I came back and tried Jabra Clipper again and it wouldn't even connect. I had to unpair it and repair it in order to get it to connect. Then when I tried mp3 playback, it wouldn't play at all (timer didn't budge) as opposed to sound coming from the speaker instead of headphones as on previous attempt. I unpaired and tried again and it then worked as expected and played through the headphones.

TLDR: Bluetooth media playback is pretty sketchy.

I did pull the log but I have no idea what I'm looking at. You're welcome to browse through it and see if there's anything probative. I've also attached my CSV files since I recall you asking for people to share them with you so you could try to consolidate that.
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
NICE!

Bah! I know! I just didn't get the bundle since I already had that fixed...I just put that bit in so you would know that I had that fixed as well and you wouldn't asked if I had fixed that! Now what kind of things were you seeing in maps? That's what I was really asking....u know what...nevermind. You're right elsewhere. This isn't the place for that...this is an audio thread. On that note (audio pun not intended) the GBX0B+.27-Audio combo works GREAT on my RHOD400. SUPERB. Nand that sucka and life will be roses. Audio works, Speaker works, BT in-call audio works (I don't have A2DP or whatever so no comment there), usbEXT audio worked (music, didn't try a call), 3.5mm Headphone jack works.

ONLY problem I've had - not sure if it's audio or camera related is the camera app crashes AFTER attempting to record a video. Probably camera, probably a known issue, just throwing it out there. Also, I haven't tested but I'm sure TV out doesn't work and nobody's probably working on it, but I figured I'd throw it out there as the only other thing I can think of the doesn't work at the moment.

LOVE IT! THANK ALL DEVS!