yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic Android Development] cellsafemode:
I too get issues over 595. Wifi will not work etc. at 595 everything is happy.

I pulled the .config, and you cleared everything up. I was just wondering if those extra patches or anything that made booting to the 1.2 correctly were missing from the standard github kernels that I've found.

I have two jobs so time is very limited but I'm hopeful to boot my own compiled kernel this weekend and then work on modifying the accelerometer driver, specifically the parts that handle determining orientation in order to create a sysfs file that controls orientation locking. Write a 1 to the file and it always reports the same orientation that it's currently in, tricking the entire android system into thinking you are never changing your orientation... write a 0 and it reports the real orientation.. and so on. Then write a little app that can be used as a widget or kept in notification bar so you can easily tap lock the orientation whenever needed. Allowing true landscape and portrait locking on any mytouch 3g.
[myTouch 3G, Magic Android Development] rattking:
Uhh yeah I trimmed that way down.. no debugging at all (I like to live dangerously)

later tests were less insane

http://www.mediafire.com/file/eqgv0sbb7t4c57s/config-test7

the only other thing to note is that kernel/mkbootimg.sh was edited to force the base address to 10000000 instead of copying the address of the previous kernel.. thats really why I posted it as for Fender/1.2 only. I didn't want anyone messing that up and blaming me when re-flashing Pershoots kernel didn't correct it
[myTouch 3G, Magic Android Development] cellsafemode:
It looks like the 1.2 patch is something that basically changes the 32A so if you patch your kernel source to support 1.2, you break building 32A kernels (you have to then have two trees or continually apply and remove the patch between builds). Is that the case, does the patch make your tree a 1.2 only tree when building for the 32A ?

If so I can edit the patch to introduce a kernel config under the saphire board selection to choose if you want to build for the mytouch 1.2 or 32A or 32B directly. So there is no confusion. Then instead of replacing values in the source like the patch does, wrap them in IFdef macros based on the kernel config options.

Then it should be easy to roll out 3 kernel compiles and do something similar to an auto kernel package and utilize a little logic to determine which to use. A rev board with 2.22 radio == 1.2 (i forget if there is another locale where the radio is different for the 1.2). Others can be chosen based on board rev only.
[myTouch 3G, Magic Android Development] ezterry:
Um... all my kernels to my knowledge work on 32a old radio, 1.2/32b old radio and 2708+ 32b new radios..

Just 3 config files and #ifs for the changes.. ebi1=3.22 radio, ebi0=2.22 radio, and 2708+ = 32b with 2.22.27.08+ radios. (And thus 3 binaries in the auto kernels)

Note the ebi1/ebi0 have both 32a and 32b versions that is what you see with the smi size logic in the kernel
[myTouch 3G, Magic Android Development] cellsafemode:
ok. I read the description of the 10M patch above wrong and thought it was also enabling 1.2 support ...
[myTouch 3G, Magic Android Development] cellsafemode:
Also, I'm wondering why exactly we use an initrd/initramfs setup. Our rootfs drivers are all compiled in so what's the real reason we bother with initrd ? Seems like we could speed up loading time if we avoid having to decompress and use an initramfs image and just get right into mounting root
[myTouch 3G, Magic Android Development] cellsafemode:
OK, sweet. I have 2.6.36.4-s2 working 100% on my mytouch 1.2. Now i can move forward with some actual development. :)
[myTouch 3G, Magic Android Development] tvall:
i might be wrong but i think android mounts the partitions directly to places in the initrd. never does a switch root out of it like most linux distros.

but im a noob and might be wrong lol
[myTouch 3G, Magic Android Development] ezterry:
The normal configuration is:

/ = ramdisk and contains init and adbd on the rom (and all of recovery)

/system = system partition

/cache = cache partition

/data = is userdata partition or internal MMC card depending on the device's design

/data/data = userdata if the device has an internal MMC card

** dream/sapphire only has /data on the MTD partition .. no internal MMC card.. just the external one (sd-card)

Can it be changed .. well that is more of a rom design than a kernel question.. just set the bootimage's command line to match if needed... but the above is aosp's expectation.
[myTouch 3G, Magic Android Development] cellsafemode:
OK,

2.6.36.4-s2 ezterry kernel for mytouch 1.2

http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe.zip.torrent

Source code at

http://signal-lost.homeip.net/files/ezterry_2.6.36.4-s2.torrent

Seed if you download. tTorrent app is a full torrent app for your phone. Or you can just load it on your computer (ideal) and then move it over usb while in recovery.

This is basically rattking's kernel install package with some minor asthetic edits to the install script and layout. The kernel is based off an older rattking .config with necessary changes to match configuration changes in the newer kernel as well as changes to certain schedulers and included drivers and features.

edit:

If you have trouble connecting to the torrent, make sure encryption is on.

IF you still have problems.. the direct link is http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe.zip But it would be nice if the torrent was used.

edit2:

Some info about the latest kernel for those who haven't checked it out...

the 10M patch is already applied in the upstream source, so you'll have that. I also turned on all the unsafe frequencies, but default you move around between 122 and 595. You can override that however with user apps.

NOTE: Swap is not enabled with this kernel. .. that's about all the important stuff for now. I just wanted to get a good stable starting point before i start diving in and breaking stuff.
[myTouch 3G, Magic Android Development] cellsafemode:
New version with some bugfixes.

I forgot to add in scsi support so the mass storage feature can function... some other minor changes too.

http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe2.zip.torrent
[myTouch 3G, Magic Android Development] cellsafemode:
7 hours of constant audio playback with the regular music player, on and off texting and web browsing over 3g (3g enabled entire time) and still got 50% power. I gotta compare to other kernels but that sounds pretty decent considering by now i'd be plugging the phone in.

my next half day off when i'm not 2 jobbing it i'll patch up the sensors so that I can enable and disable updating the orientation sensor via sysfs. Should be trivial then to have real orientation locking that's application independent. Should be sweet ! :)
[myTouch 3G, Magic Android Development] NetrixTardis:
Is your kernel mainly for gingerbread, or froyo? If I understand right, ezTerry's 2.6.36.4 kernels are for gingerbread...
[myTouch 3G, Magic Android Development] cellsafemode:
I've only tested it against gingeryoshi so I would say gingerbread or newer
[myTouch 3G, Magic Android Development] moises93:
Download link for the minor fixes you did isn't working. It says forbidden. Grr. But currently testing the first one with GingerYoshi.
[myTouch 3G, Magic Android Development] cellsafemode:
Damn... Well does http://signal-lost.homeip.net/files/2.6.36.4-s2-cellsafe2.zip work? I probably forgot to chmod the files to be readable to the webserver. It will be 5 hours till i get home to fix that :(
[myTouch 3G, Magic Android Development] cellsafemode:
The minor fixes one actually fixes some important things, they're just not going to make your phone not work. Things like changing the rate of sleep to something more sane. The first version sleeps way too much. Also you wont have mass storage or adb (you have to do that through recovery if you need to) basically usb is charge only in the first one. The second one is fully functional and I've been using it since i compiled it without any reboots or issues. I thought i fixed my permissions on the file after i made it but i guess in my haste i forgot.
[myTouch 3G, Magic Android Development] cellsafemode:
OK, fixed the torrents and such so all should be downloadable now. Sorry about that.

idle standby (phone sitting with screen off and 2g only) 25 day battery life based on 6 hours for 1% drop
[myTouch 3G, Magic Android Development] mistere372002:
I was told that the reason wifi calling app from tmo would not work is do to the kernel. I think that some Lin's are missing. But could you look onto finding what kernel changes are needed and consider placing them onto this kernel?
[myTouch 3G, Magic Android Development] cellsafemode:
Ok, I have orientation locking working in the kernel. At the moment it basically locks the entire magnetic sensor when you write to a new sysfs file i created. This successfully locks orientation in whatever position you were in when you wrote to the file. Things that this will cause to not work correctly are compass apps (you will be stuck facing whatever direction you locked the phone in)...basically anything that relies on current directional information. things that use GPS should remain largely unaffected.

You re-enable active magnetic sensor input by writing a 0 to the sysfs file. Then phone orientation is back to being dynamic.

I have only had this one night to work on it so perhaps there still is hope to isolate orientation flipping without blocking the raw magnetic sensor data but i doubt it.

Maybe it's possible to edit the libhardware sensors library in the OS rather than modify the kernel ....I haven't had time to check but that would be a more direct route i would think. As you would be able to block the orientation change event without mucking up the sensor data (theoretically).
[myTouch 3G, Magic Android Development] cellsafemode:
Ok it appears I can do this feature by modifying the sensorservice app which is responsible for sending out orientation change events to apps. So I'll probably go that route.

For now though I'm currently working on forward porting ezterry's 2.6.36.4 android related drivers and changes to 2.6.39. _lots_ of work to do so that should be fun.

I should have a great majority of it done by this weekend. Something bootable at least :)
[myTouch 3G, Magic Android Development] cellsafemode:
Ok, ezterry must have made some bluetooth changes to his source recently because his version of the same exact kernel i was building from (since i was building from his source git) has functional bluetooth where I couldn't get it to load up for the life of me.

I'll have to resync my local copy and check out the config in the running kernel i have now. Then i'll recompile and see how things go. I compile without small kernel enabled and other things are switched out like the IO schedular and such. Anyway I look forward to getting home and either today or tomorrow seeing what the hell was keeping bluetooth from working :)
[myTouch 3G, Magic Android Development] cellsafemode:
nevermind. ezterry's kernel doesn't have functional bluetooth either.

So it's gotta be either a ginger-yoshi incompatibility or the kernel's bluetooth is borked. I'm leaning towards the former.
[myTouch 3G, Magic Android Development] ezterry:
well I can't say if yoshi has any particular problems; but the kernel's bluetooth in general has worked for me.

If you are having problems with the CM6 Dream/Sapphire bluetooth firmware try the MT3G ota sapphire only firmware

From my MT3G-test3_S.zip rom you can find the CM6 one (default of CM6, ezgingerbread, and gingeryoshi) in work/brf6300.bin, while the sapphire OTA version is in system/etc/firmware/brf6300.bin

ezGB installed the CM6 version for Dream users; but left the sapphire version for sapphire users. To keep things simple I only use the combined version on ezGingerbread; but if you are having problems try the newer file.
[myTouch 3G, Magic Android Development] cellsafemode:
interesting.

I tried both firmwares...same behavior on either. Older 2.6.35 kernels by you work fine but I haven't had anything in 2.6.36 be fully functional.. ex. bluetooth may say it's turned on, but you can't do anything with it.

with your kernel and yoshi 1.2, bluetooth says it's on, but selecting to make the phone discoverable causes it to reload bt and not be discoverable and i can't scan for any devices. (totally non-functional)
[myTouch 3G, Magic Android Development] ezterry:
Guess the next question is does bluetooth work in ezGingerbread for you?

If not bluetooth is half in the kernel half out so both a dmsg and logcat are need to be examined.
[myTouch 3G, Magic Android Development] cellsafemode:
Haven't used ezgingerbread.

wont be able to mess around with it again till the weekend. Maybe i can convince someone else using gingeryoshi to try out 2.6.36 and see if they have the same issue. But i know i can drop back to your 2.6.35 kernel and it works completely.
[myTouch 3G, Magic Android Development] Exodusoffg:
I'm on gingeryoshi. Ill give the kernal a try and report back.

I think this is a great idea as our devices have less dedicated attention.

sent from fender

XDA Premium

Sapphire 32A Ship S-on G

HBoot 1.33.0013 (Sapp 31000)

Cpld-13

Radio 2.22.28.25
[myTouch 3G, Magic Android Development] Exodusoffg:
So I flashed your kernal..

My blue tooth problems

Can not connect to devices

An error window comes up when trying to connect.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error Window

Attention

Cannot establish communication with "device"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I have tried to connect to a headset and a computer & get the same results.

Turning on blue tooth works

Scanning for other devices works

Enable discovery works

sent from fender

XDA Premium

Sapphire 32A Ship S-on G

HBoot 1.33.0013 (Sapp 31000)

Cpld-13

Radio 2.22.28.25
[myTouch 3G, Magic Android Development] Exodusoffg:
I like the oc ability to 710. Ran it at 710 min and max for over 12 hours and no problems. Seems to be running cooler as well. Its a huge battery drain though.

I have oc'ed with other kernels at 614 and I always end up with phone freezing. Also the battery was very hot to the touch. Haven't had the heat problem yet.

Couple of areas of concern.

Only one option for CPU Governor "interactive" beings I haven't had any problems so far its ok. But I am use to have more options for this feature.

Also under the YoshiMod Settings > Performance settings>

there is no CompCache feature.
[myTouch 3G, Magic Android Development] raven198:
I just found this and I am wondering where you are at with your developement? I am using a 1.2/35mm as well. As Of this moment I am running Gingeryoshi 1.5 and I am using ezgb-2636-v1.5.1 for my kernel. My biggest problem is a HUGE battery drain. If I check say Twitter, within about 2 minutes I loose at least 8-10% of my battery. In an idle screen off sitting in my pocket mode, I loose about 2-3% every 30 minutes or so.

If your kernel is working out I would love to give it a try and see if that helps. Also, have you gotten BT working properly yet?

Please let me know.

Thanks
[myTouch 3G, Magic Android Development] raven198:
Is anyone checking this thread any more?
[myTouch 3G, Magic Android Development] WoefulDerelict:
I don't think the so.

I haven't seen the original author/dev post anything back in some time. I think someone working to keep the Fender/1.2 kernel fork working is long dead.
[Acer Iconia A500] jb0nd38372:
I keep reading post about people being "scared" that acer isn't going to update as fast as they would like. Or their is no Restore yet, bootloaders and other minor annoyances.

One thing I see is request for USB charging. Will never happen, the Acer's dual 3650mah batteries would never get charged under the .5 load that a usb port can supply, I doubt a usb port would even be able to turn the machine on. A quick look at the ac adapter shows it's putting out 12v and 1.5amp and that's capable of charging my machine from about 25% to 100% in about 2 hours. Thats very respectable in my eyes since I can run a full 10-12 hours with really moderate to heavy use (Video's/Music/Games) wifi always on and screen set to auto brightness.

Besides I didn't buy my acer for the software that it came with, I bought it because of the hardware. The Xoom Asus and Acer are pretty much twins as far as respective hardware. If your going to nit pick something, the xoom's SD card doesnt even function, the acer's does. And the Asus transformer lacks USB host all together if I understand correctly, I can't begin to imagine the fun things that could be done when the dev's start tweaking the kernel and making 3rd party apps as well that are capable of using both usb ports on the A500, esp if the mini usb is capable of being switched on as a host as well.. (god i wish i could program my ideas)

As far as the locked boot loader issue goes, it'll get unlocked, as well as recovery, it will come. Even if Acer decided to be a complete ass and never reaveal any flaws in their code base, someone will get it accomplished.

I got the HTC inspire as soon as it was released for AT&T, no recovery, locked bootloader. I lurked on the fourms and saw a mirror of the exact same thing here, i'm scared... im returning mine for this, this or that. Now look at the inspire; there are tons of rom's, and dev support is flourshing.

I'm staying with my A500. I've had it 1 week this Friday, and my until has had no battery drain issues, gps or any other bad issues I've read others having. i have rooted mine, renamed phone / telephony .apk > .bak, and it did help battery some. For the most part I wonder what some of these people are running in the background. (even live wallpapers can seriously strain the battery with the device idle. A good example is the Asus water live wallpaper that has been hacked to work with the A500)

My biggest problem with mine is the market refusing to download and install apps I find until I kill the MyApps service and task, then it works for a few downloads, then refuses again..

I can't see returning something with fairly minor software annoyances that will eventually get fixed anyway. Now granted I love to get under the hood and tinker (I am not a dev though) I see promise in Acer's future with this tablet.

I really can't justify buying a $599 Xoom when it's spec'ed the same as the acer, and has it's own shortcomings that readily already works with the A500.

Input please?
[Acer Iconia A500] edgie168:
it's the "hey, look at me look at me look at me" syndrome.

either you buy it, you don't. if you've already got it, you either keep it or you don't.

if you're so scared to drop $450-600 for something then you're never going to be satisfied. me, originally, i bought this to hold me over til the 32gb transformer came out, but the more i play with it--despite it's shortcomings--the more i like it. the screen is really nice, much nicer than i was led to believe due to various "reviews" on the 'net.

it's no ipad screen but then again, what other tablet in this form factor even comes close to the ipad screen?

people need to stop crying so much and learn to live with what they've got. i didn't exactly NEED this tablet, and i could have very well continued living without it so i really don't understand these folks who are just itching to spend money on something just so they can cry about it online.
[Acer Iconia A500] mrinternet:
Acer A500 Ace Enough ?

I think your query is 100% valid. Here in Australia we have the Galaxy Tab 10.1v out but in very short supply, no Xoom yet, so I bought the Acer A500 then got offered a Galaxy but am still waiting for the delivery, I also have an iPad2.

Based on honeycomb alone I like it better than the iOS on the iPad 2, but iOS is really a few years old now and honeycomb is new.

Add in the ACER's native USB that works with drives or keyboards etc, a working microsSD, and the Acer is a force to be dealt with even at more money.

I look forward to the Galaxy but the Acer feels like old hardware with a new operating system, whilst the iPad2 for instance feels like new hardware with an old OS.

Here in oz, I am more concerned at the lag of accessories / cases for anything other than the iPad2

The only hardware issue I have is that it doesn't charge by USB and you get a small residual charge when using it whilst connected to the power

If I was doing it all over again the galaxy tab 10.1v is likely to have been worth waiting for, and might be selling my Acer on eBay less than a week after purchase.

But only if I can get the idea of the working microsSD - not on any tablet yet (but the Xoom should be working in the future) , and USB.. the idea of plugging a usb stick in a tablet is soooo good.

I also find using the Acer as a PDF reader much better than the iPad2 (a big deal for me) and finally I find the bigger bezel and wider viewable screen, better onthe acer than the apple especially when typing.

Live wallpaper is awesome on the acer.

Typing is so much better on the Acer.. iOS 5 has a lot of ground to make up for.

So Galaxy I expect to be better than the Acer, in build quality but not features.

Between the Xoom and the Acer, I do not get the point of the price difference for the Xoom .

Hope that diatribe helps

@mr_internet :)
[Acer Iconia A500] Riffer:
In my case I sent it back because I am scared about the Iconia

bootloader is strictly closed at the moment and its

build quality (mine creaked on the right backside just where the border is - heard from few people having the same problem)

and in addition I had the chance to

get a Motorola Xoom at the same price as the Iconia - and because of its

great developer base plus the freedom to customize it in any way

I have choosen the Xoom about the Iconia.
[Acer Iconia A500] docfreed:
On The Fence

I'm concerned about a few things but nothing major:

1. The "wobbly" charging pin failing once I'm out of warranty - I've had this kind of charging pin on a (admittedly) crappy Archos and returned it to BB.

2. The lack of accessories

The software doesn't bother me since I rooted (easiest root I ever did) the devs will ultimately prevail - what does bother me is if the devs lose interest - then we're dead in the water.
[Acer Iconia A500] rorytmeadows:
...Probably because people aren't getting the attention from the public they thought they would from buying a tablet. I figure Apple sold so many for that reason...
[Acer Iconia A500] Neoprimal:
When you drop $450 on a device on impulse, you look for reasons to take it back. Plain and simple. I believe a majority of people purchasing the Acer A500 were looking forward to the Transformer. When that didn't come (properly, anyway) they hurriedly got the A500 on impulse because it was available.

I think we all know how impulse purchases go. We practically sit there and look for reasons to return the device because we know it's something that we didn't REALLY think through thoroughly and I suppose the responsible part of our psyche becomes hyperactive. Everything and anything becomes a problem and we start seeing issues that aren't really there (not saying this is true of everyone).

The people who returned their A500s are likely serial returners, ie: people who regularly impulse buy and return stuff and between the Galaxy Tab 10.1 and the other Honeycomb tablets coming in June, there's going to be plenty fodder for them to get through before they finally settle on a device. There's nothing wrong with that as it's their money and they should spend it how they see fit. There's also the fact that some people are genuinely having software or hardware issues and simply lost confidence in the device.

So why are people returning it? It's all relative. Some people have/had hardware issues. Some are having software issues that they'd rather not wait to see fixed. And some are looking for something "better" to come along down the line.