yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] fonix232:
No logcat can be done sadly. The filesystem gets damaged during the update, and some file won't be copied.

Instead of formatting the whole system partition, why not simply do a recursive removal of files?

delete_recursive("/system");

Also mount it with busybox:

run_program("/sbin/busybox", "mount", "/system");

This applies to every partition. Safer and easier to use than the CWM built-in one.

Apart from these two things, it's all okay. I had to make a whole blob for my tab to work, and luckily I got it back to life in less than 15 mins! Almost missed the morning bus tho :D

My solution for the microSD support is half-ready. First, you need the original vold.fstab from any existing ROM, and push it to /system/etc (during the build process preferably). But somehow this failed for me, it did not automount the partition. You can, for now, add a little extension to init.ventana.rc, so it mounts the stuff automatically:

mount vfat /dev/block/mmcblk1p1 /Removable/MicroSD nosuid nodev

Now the only annoying bug is really the sleep one - audio kinda works, BT too, although sometimes can't switch on. Background light setting is still a no-go. Headset not working, nor display rotation.

Also, please, next time you compile a kernel, enable config storing and /proc/conf.gz access to the config ;) I want to compile the kernel with your latest additions, and can't because I can't find which config you used for it.

EDIT:

Just saw your commits. Just asking, will you add the libsensors source to the tree, or it will have a different git repo?

EDIT2:

Began compiling CM9 for the TF101, let's hope it won't fail... :D
[Eee Pad Transformer Android Development] UnknownAccount:
Were missing vold.fstab at sytem/etc :cool:
[Eee Pad Transformer Android Development] Sharpe351:
Yea, I had to do it in order to flash it. It also is a gripe for me having to deal with CWM. Version 3.x.x.x is so slow. I wished someone could update to version 5.x.x.x. It would make backup/restore a whole lot faster. It takes me 45-50 minutes to restore HC in CWM. I also have to reflash the kernal every time I go back and forth. The port is coming along nicely though. I had alot more functionality in this iteration Paul. Cudos sir. At the speed you're developing, we could be nearly usable as a daily in a few weeks or so. :)
[Eee Pad Transformer Android Development] Sharpe351:
I tried installing it via Root Explorer, fixing permissions in CWM and reboot, but to no avail. I don't think the kernal sees it yet.
[Eee Pad Transformer Android Development] UnknownAccount:
The New Port doesn't even seems to boot O___O

Installation takes half minute, somehthings wrong :I
[Eee Pad Transformer Android Development] Sharpe351:
In order to install, I have to wipe data, and system, just to flash it. Otherwise it won't flash, along with mounting /system in CWM before flashing. Nandroid alone will not restore my tablet. I also must flash the kernal.
[Eee Pad Transformer Android Development] UnknownAccount:
Yupp Solved the Problem :)

OP shall update the post :D

You need to Mount System Before Flashing ^^
[Eee Pad Transformer Android Development] paulburton:
That's really odd... I've just built a new update zip, anybody want to try it? (As a bonus incentive it makes the backlight work, manually at least!) It flashes fine for me, it is over the top of the nvflashed one but since it's formatting the system partition anyway that shouldn't really matter. I could do delete_recursive, but the end result should be the same and a format just feels cleaner. Mount is actually in update-binary which is built from source and should work fine - I'm curious why you feel busybox would be safer? Both are basically just doing a syscall, which I'd rather not need to drag in busybox to do.

Good to hear, congratulations on catching the bus :)

The external storage stuff is one of the many things I've not even looked at yet, thanks for the info :)

Yup, lots to do still. Backlight should work with the zip above, though only manually since the light sensor isn't working yet.

Yeah I pushed the defconfig because I saw your message, it's exactly what I built with. Do bear in mind that I keep rewriting history in the kernel repository as I go, so if you do any work on it do it in a branch and be ready to rebase. Might be slightly inconvenient, but it avoids the mess of many commits of a half working kernel. The end goal being a patch set that adds the TF101 & drivers cleanly and can be applied atop newer releases. I'll put libsensors in the device repository alongside libaudio etc.

Good luck!
[Eee Pad Transformer Android Development] Sharpe351:
I think something goes wonky and CWM is ignoring the script. Try to wipe /system and /data then mount /system manually and flash it twice. That worked for me.

**edit** Just to be on the safe side, anyone that tries this should only do so if you can use NVflash to get out of it. It seems that with the installations being borked for some reason, it may prove difficult to get back to normal if something goes really wrong. I would not suggest trying this on sbk2 tablets until the build is further along.
[Eee Pad Transformer Android Development] UnknownAccount:
You should update the info at first post :) and write as the guy above my post wrote :cool:

Brightness control doesnt work (however in 1.st flashable it did)

Wifi with WPA2 can connect ;)
[Eee Pad Transformer Android Development] paulburton:
Try it from the settings app or the popup you get by tapping the clock. The keyboard dock brightness keys don't work yet.
[Eee Pad Transformer Android Development] UnknownAccount:
i did that and still doesnt work :/

lets play around and see what doesn't work :)
[Eee Pad Transformer Android Development] fonix232:
I'll take a look at it ASAP. USB does not work (ADB does, fortunately, but MTP needs to be enabled in kernel, what needs patching in order. Kernels 3.x and up are all have MTP mode by default in source!).

Busybox stuff worked before, your mount obviously not. So I just figured, if it was working before, and your way doing it won't, then let's get back to the good ole' way :D

It was kind of a run, what I hate to do in the morning, especially with a huge, A/1 drawing board at my side...

If I'm right, some patches to Vold should do it.

I'll do a check in a minute, just have to charge my tab a bit. One more thing, charging parts aren't working, it won't display!

Okay, thanks for all of this. I do not plan to modify the kernel, I'm no good at C/C++, so only building so far.

One more request I would have for today: the vendor setup files (with all the ADB pulls, preferably from your AOSP system) OR the vendor tree, on git. For the last hour I've been fixing CM compile errors, my previous post was made during a build (I could even hardly type, so slow...), and it still pops up messages like missing libraries (so far one, bcm4329.ko). A unified vendor tree could hold all the proprietary stuff AND extensive things like the wifi module, and easier to update.

Also, DO NOT set the DATA partition size in boardconfig. As we all have different versions of the TF, there is no way to ensure everyone's good. We won't mount really the data partition using sizes (use the busybox method, easier), so it can be excluded for now.
[Eee Pad Transformer Android Development] UnknownAccount:
OK Confirmation!

Wifi Work's WPA2 *Tested*

Sound Works *Keyboard-Test* (Bit Low in speaker)

USB *It been Recognized By Windows Installing Driver's*

*Not Working*

Storage

Headphone's
[Eee Pad Transformer Android Development] paulburton:
That size is only used when creating userdata.img, and since that isn't being flashed it's irrelevant. Think of it as a maximum size which the build system will complain about if it exceeds (not that it ever will). It has no effect on anything else, the partition is in the GPT created by the bootloader and that determines the size of the partition the kernel sees.
[Eee Pad Transformer Android Development] fonix232:
Okay, the new zip installs, it's booting now!

I know the kernel uses the GPT for the sizes, BUT, those sizes you set in BoardConfig are also used in the mount commands.

Re-flashed with a clean system, and looks like I was wrong: it won't install correctly. Mount fails.
[Eee Pad Transformer Android Development] KMyers:
Hello, can anyone confirm if Bluetooth is working on this build? (Need to tether from my Phone to my Tablet)
[Nexus S Q&A, Help & Troubleshooting] ßarbarious:
I have an interesting issue. When i restart my phone, i get no signal, but when i turn to airplane mode and than normal mode again, i get signal. Every restart, it repeats. What's the matter with my phone?

(Nexus S with NexusBeam)
[Nexus S Q&A, Help & Troubleshooting] WHITE*RABBIT:
Maybe add a power widget on your screen and see if its connected to the mobile network after boot up..

sent from my ics 4.0
[Nexus S Q&A, Help & Troubleshooting] ßarbarious:
Phone recognizes my service provider but as i said no signal. I am really unfamiliar to android i get phone 3 months ago somehow i managed to root :) Actually its very long story. On stock room there was no stock a problem like that. I flashed to NexusBeam first but i didnt like ICS so i decided to turn Gingerbread 2.3.6. I managed to turn stock rom BUT there was no signal like that. I did not come up with idea like turning phone to airplane mode that time. I flashed to NexusBeam again and it worked well. But after several restarts, i got same problem.

To sum up i doubt that i made something wrong :( Might it be efs or something like that?
[Nexus S Q&A, Help & Troubleshooting] WHITE*RABBIT:
When you flashed the different roms, did you wipe dalvik cache more then once?? If I were you, I'd back up everything with titanium backup then do a master reset... wipe the data and the dalvik like 3 times over!

sent from my ics 4.0
[Galaxy Ace S5830 General] -SGA-:
Just got bored of CM7 and decided to see what I could do with my stock ROM. I have OC'ed to 902MHz and am happy with the CPU performance, but I/O is poor. Can I change the file system to something that can read/write faster? Any help would be great!

Thanks
[Galaxy Ace S5830 General] philipxtian18:
try turbo boost i think it will help :) http://xdaforums.com/showthread.php?t=1380006
[Galaxy Ace S5830 General] mdfzhi:
sounds like u use cfroot. so just install nofrills cpu control from market, open it and set io scheduler to noop. the difference from default deadline is noticable.
[Galaxy S II General] thteddieboii:
I think usb isnt working because you removed mtp application?
[Galaxy S II General] krazykat:
Yeah, my mtp works fine. Didn't remove anything. =)
[Galaxy S II General] rathian:
Ah, yes yes... i notice it now... u r right... i will go add it back and see if it works... cos usb storage doesnt work anymore, we have to use mtp to get it working...

EDIT: ok, i restored the MtpApplication.apk and that got Android file transfer to detect the phone via MTP... however, the AFT app is unable to see the contents.. i suspect there is more stuff to it... well.. for now i am jus happy doing bluetooth pushing or adb pushing... haha...
[Galaxy S II General] AnhPN:
Can run Viber?
[Galaxy S II General] rathian:
Nope, viber doesnt work... FC on start....
[Galaxy S II General] interfreak:
Simply download Bezke's ROM and most of these issues disappear. Also, his ROM is almost completely devoid of Samsung apps. No stuffing around removing them.

http://xdaforums.com/showthread.php?t=1393569

Also, although the phone only shows the 3G symbol, speed tests I've done clearly show it can download at H/H+ speeds. Stock ICS does not have a H+ symbol anyway when working (only H).

In other words, it may only ever show 3G, but H/H+ works just fine.

MTP works perfectly on Bezke's ROM also.

To fix the brightness setting in the stock browser, simply open it, press the menu button and select 'Brightness/colour'. Set your desired brightness.

:)
[Galaxy S II General] rathian:
what i'm offering here is jus a view for ppl who dun wanna install custom roms and just want to tweak their own stock KP8 to their liking... i'm not offering a cooked rom here, i'm jus offering knowledge from getting like 30 FCs in a day tweaking and testing what works and what doesnt...

as for the browser, once u kill the process and start it again, the settings are resetted.. so the brightness n colour settings do not stay through a reboot or termination...
[Galaxy S II General] dk206:
or instead of doing all of that above just wait for the official build :)
[Galaxy S II General] klarmacker:
calendar is not working and some other apps crash...

this is not working...
[Galaxy S II General] interfreak:
Calender DOES work by simply replacing the calender.apk file in system/app with the one posted in Bezke's thread.

What other apps crash?
[Galaxy S II General] deathst:
If you removed MtpApplication.apk.. MTP will not work :)
[Verizon Droid Incredible 2] NeWcS:
So I flashed my Verizon HTC Inc2 to cricket(QPST). Got root. My issue is I can not receive calls. I can make them fine, email, txt, internet etc.. When someone calls me it just goes straight to voice-mail.

Not sure if this is an issue with google voice which I have setup(And can't get rid of) and think it could be part of the problem or something I did wrong when I flashed. Can anyone help me troubleshot this?

Thank you!

**Not that I think it matters but I am running Skyraider ROM**
[Nokia Lumia 900] day2die:
Pocketnow has recently leaked specs for the Lumia 900. Among them is that the Lumia 900 will support the 1700MHz band.

It has concluded that the Lumia 900 will then support UMTS 3G for T-Mobile USA.

On closer inspection, however, this not be the case. You see, AT&T uses AWS for LTE, but not for UMTS.

We will take a look at the HTC Vivid and Samsung Galaxy S II Skyrocket (the only two LTE phone for AT&T at the moment) as examples. Both of these handsets uses the Qualcomm Snapdragon processor.

Both handsets support the 1700 Mhz band for LTE, but not for UMTS and as a result will not work on T-Mobile's UMTS network.

In addition, there has been little evidence that there exist Snapdragon processor that support pentaband.

As a result of this whole investigation and to the dismay of many T-Mobile customers, I have to conclude that the Lumia 900 will likely NOT support T-Mobile 3G.
[Nokia Lumia 900] crav4speed:
That is not correct... T-mobile uses the AWS band (1700/2100) for it's UMTS network.

AT&T has never used the AWS band and after the failed merger is required to give some of it's AWS spectrum to T-Mobile as compensation. AT&T uses the 700 MHz band for it's LTE network.

If I remember correctly, there are no integrated LTE radios curently. The current crop of LTE phones have a separate LTE radio to complement the GSM/UMTS radio therefore, if the Ace actually does comes with a pentaband radio, it still is possible the AWS band will support T-Mobile's AWS UMTS network.
[Nokia Lumia 900] efjay:
You are both right, at&t uses both the 700MHz and 1700MHz bands for its LTE network, as mentioned in this article http://www.theverge.com/2011/12/16/2640728/pantech-p9070-att-lte-850mhz-fcc. Remains to be seen what the 900 actually supports but if it was designed with the falied merger with Tmo in mind the 1700 band may not be used for LTE but could have been intended for Tmo compatibility. The 710 coming to Tmo next week has support for at&t's network so its possible the 900 was designed with the same intent. We'll know soon enough.
[Nokia Lumia 900] Strike_Eagle:
I thought the AT&T - T-Mobile Merge has been cancelled?
[Nokia Lumia 900] prohibido_por_la_ley:
It is cancelled
[Nokia Lumia 900] day2die:
If the Lumia 900 uses the Qualcomm MDM9200 LTE modem and is anything like the HTC Vivid, its support band might look like this:

As you can see, the HTC Vivid support AWS, but only for LTE.

I hope that I am wrong for the sake of all the T-Mobile users that want the Lumia 900.
[Nokia Lumia 900] Tsury:
I am relatively new to WP7, and I am looking for a new high end device.

Since my country only has 3G, is there an (upcoming) device that is on par with the Lumia 900 that supports 3G?

Thanks.
[Nokia Lumia 900] day2die:
Don't worry. I am 99.99% sure that the Lumia 900 will be available in Europe.
[Nokia Lumia 900] MartyLK:
According this report, AT&T will get a 900. Looks like I might get the chance to play with one.

http://goo.gl/tP4I2
[Nokia Lumia 900] jhoff80:
Looks like you were right:

http://www.nokia.com/us-en/products/phone/lumia900/specifications/
[Nokia Lumia 900] efjay:
Yep, Tmobile users stuck with the low end crap.
[Nokia Lumia 900] hiko36:
If the bands are there, why would it limit T-Mobile customers from using them?
[Nokia Lumia 900] jeremyshaw:
Not exactly limit, but no HSDPA data access. Only EDGE/GPRS.
[Nokia Lumia 900] geoken:
This is a huge disappointment. I want to like keep using WP7 but the hardware restrictions hobble the device makers too much. Nokia was the biggest proponents of pentaband but now they can't even support it due to chipset restrictions. It really puts a big hurdle in front of my decision to buy their phone when it requires me to use a carrier that costs twice as much and has data caps.

If this was pentaband I'd probably choose it above the Galaxy Nexus, but as it stands owning this phone would mean an extra $40 a month on my phone bill.
[Nokia Lumia 900] day2die:
T-Mobile users need not worry though. T-Mobile is adding 1900MHz spectrum for HSPA+.
[Nokia Lumia 900] vetvito:
Blame Nokia and carriers for their decision. Not the OS.
[Nokia Lumia 900] PoisonWolf:
Ah well, what you're going to do?

T-Mobile always seems stuck with the low-end crap simply because they don't have the money to purchase exclusivity for the good stuff.

Makes me just want to sign up for their hotspot and start getting international unlocked phones instead and forget the whole idea of carrier branded phones.
[Nokia Lumia 900] geoken:
Why shouldn't I blame the OS? Last I checked Nokia seemed pretty fond of pentaband devices. All their recent high end phones (up to and including the N9) were pentaband. They didn't stop using pentaband until they started developing WP7 phones and were forced to use chipsets that don’t support pentaband.

There are 3 reasons Nokia wouldn't make a pentaband WP7 phone;

1. The OS doesn't support any chipsets that would allow a pentaband radio

2. Nokia doesn't want to make pentaband phones

3. The carriers told Nokia not to make a pentaband phone

Option 1 is provably true. Option 2 is unlikely since Nokia had been making all their recent high end phones pentaband. Option 3 is also unlikely because the phone was first released in Europe where carriers have less sway and where Nokia was already selling pentaband phones.
[Nokia Lumia 900] vetvito:
its number 3. As the discussion is about the Lumia 900, a exclusive US device. Blame the CARRIER AT&T. This is not a unlocked world phone.
[Nokia Lumia 900] efjay:
The Nokia 710 has quad band UMTS frequencies and it uses the exact same chipset as the other 2nd gen WP7 devices so its definitely possible for Nokia to at least inclde support for both US carriers, though not pentaband. This was obviously a deliberate decision to make it at&t compabible only.
[Nokia Lumia 900] brad1825:
Nokia Lumia 900 on the 1700 band

This is the saddest news I have heard in a long time.

I was really excited when I saw that the Nokia Lumia 900 carried the 1700 band,

However, if it's true that it will only work as LTE, that's just depressing.

I'm still hopeful that it could still work, but I went ahead and purchased a Radar 4G off eBay until we can get further testing with the device.

It doesn't come out for at least a couple months, then it will be a while later until we can get an unlock tool for it.

Still hopeful.
[Nokia Lumia 900] crav4speed:
I was so hoping for that to be the case nationwide. But over at Howard Forums, people suggested it would only be deployed where there was not enough AWS spectrum. So, if that's the case, I'm stuck with only AWS in NYC. :( I truly hope that it's a nationwide deployment. I think T-Mobile should just convert all it's 1900 spectrum to hspa+ and become a UMTS only network then we'd be able to use any AT&T or T-Mo phone!
[Nokia Lumia 900] geoken:
I find it hard to choose 3 when the sim free 800 didn't offer pentaband like it's brother the N9.
[Nokia Lumia 900] mikeschevelle:
subscribed, .....been looking for a device to make the switch from Android, but need at least 3g
[Nokia Lumia 900] DavidinCT:
Dude, Don't even got there. At least you get a choice.

I have Verizon and while they have the best coverage where I live, I don't have a choice on WP7 devices. The Trophy is my only option and when it comes to WP7 devices, the Trophy is called "low end crap" or bottom of the barrel.

I really hope they release this phone in a CDMA/3G/LTE version for Verizon. It's about the only phone on the market that will get me to sign a 2 year contract.

I, like everyone else here, hope they can get a High end WP7 device on their carrier.
[Nokia Lumia 900] jdep1:
http://www.phonearena.com/news/Report-says-Nokia-Lumia-900-coming-to-T-Mobile-in-Q3-with-12MP-camera_id25895

I hope to see the nokia 900 on tmobile. The lumia 710 was a downgrade for me coming from an HTC sensation on ICS but I got tired of android going in to the old mistakes of windows like some apps don't support wvga, open a menu u get another menu in to another menu & so on.. Anyways back to topic I got the samsung focus s unlocked for tmobile untill the lumia 900 with a12mp cam makes it to tmobile :D
[Nokia Lumia 900] :
Still looking forward to it.
[Nokia Lumia 900] jacklivehere:
From SGSII Skyrocket forum reports their phone with Modem( MDM9200 -Same as Nokia 900), works with T-Mobile after flashing T-Mobile Radio Rom. This shows MDM9200 Chipset infact supports AWS/T-Mobile bands, but need to see if nokia will release such radio rom
[Nokia Lumia 900] PaullikesWINMO:
Is there hope ?

Given that the Lumia 710 from Rogers in Canada is PentaBand, would it be remotely possible they would do the same for the Lumia 900 ?

http://www.gsmarena.com/nokia_lumia_710-4276.php

I did buy the Lumia 710 and unlocked it and I'm using it on Mobilicity which has the same bands as T-Mobile. No big news there as the Lumia 710 sold by T-Mobile works in the USA on T-Mobile, but the Rogers model would also work with no issue on AT&T.

This is not meant to mislead anyone, but thought I would point out what did happen with the 710 and maybe, just maybe, the same might happen with the Lumia 900?
[Nokia Lumia 900] geoken:
http://pocketnow.com/windows-phone/nokia-lumia-900-visits-fcc-with-its-att-lte-bands

The recent FCC info from the Lumia 900 is yielding some promising info. Apparently it lists HSPA+ support on 1700. They list WCDMA IV as supported.
[Nokia Lumia 900] cx1:
The unlocked world phone doesn't support it either.
[Nokia Lumia 900] Fabian Cortez:
You are correct.

The phone will support T-Mobile's HSPA+ on 1700 MHz and the refarmed 1900 MHz. It will also support T-Mobile's LTE once launched in 2013 as AT&T and T-Mobile use the same AWS (1700 MHz) band for LTE.
[Nokia Lumia 900] geoken:
Do those pics mean the international version will also support the bands? Or does the FINAS review Nokia products even when they're export only?
[Nokia Lumia 900] Fabian Cortez:
I'm not too sure about that. That's simply one of fifteen documents on the FCC's website.

I'll provide a link once I surpass eight posts...
[Nokia Lumia 900] 937dytboi:
From the looks of things it seems the phone is a quad band and will work on T-mobile. I may be wrong but this is what I was told and read. Im torn on if I should switch to AT&T or stay with T-mobile. AT&T iphone devices get 3g bars at my job while i get barely any bars to surf the net. T-mobile isnt very good in my area. LTE for AT&T isnt even launched in my area and nobody knows when it will so I would be paying for a service I cant even take advantage of. But since the unlocked version supports HSPA+ it would be great on T-mobile. I just need to know the pricw of the phone unlocked and when it will be available.