yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] slick_rick:
Try on a completely stock rom like one of sfhubs Odin in clicks. Or it could just be sprint for now.
[Samsung Epic 4G Touch] ScubaSteev:
I was told to but dont know hiw to use on mobile odin :p

Never wanted to take the chance of bricking :p
[Samsung Epic 4G Touch] ScubaSteev:
Do i just mobile odin the el26/CWM Kernel and then flash shfubs el26 stock rom?
[Samsung Epic 4G Touch] slick_rick:
No go to his fe22 odin one click thread and use that to go to stock twiz. From there update prl/profile. Then you can go ahead and mobile Odin the el26 cwm kernel and ref lash to whatever rom.
[Samsung Epic 4G Touch] ScubaSteev:
I thought since i have gb rom i have to use the el26?

And ive never used mobile odin to flash anything besides a el26 kernel so i have no clue how to flash a completely stock rom:p
[Samsung Epic 4G Touch] TeamERA:
I think system update support was removed from Ego to save battery life.
[Samsung Epic 4G Touch] ScubaSteev:
It wont update on blazer 4.1 either

Im going to flash dazed ics rom in a bit
[Samsung Epic 4G Touch] MeWarning:
I had that same problem on Frankenstein's last night. No matter what I tried they wouldn't update so I ended up going back to Calk's ROM. And I really liked Frankenstein's ROM and wish I could of stayed on it longer.

---------- Post added at 01:57 AM ---------- Previous post was at 01:49 AM ----------

You can still flash a GB kernel even though you have a ICS ROM installed. It won't boot the phone completely(it'll freeze on the Samsung Galaxy SII screen on startup). But you can still get into recovery and download modes. That's the benefit right there. You don't need to flash all that though. Which ROM do you want to be on? The part about using Odin to go to FE22 and then go to EL26 has an extra step in it. You really don't need to flash the FE22 before going to EL26.
[Samsung Epic 4G Touch] ScubaSteev:
Wait what? Lol

Im confused

Doesnt some ics roms have cwm
[Samsung Epic 4G Touch] MeWarning:
Ya some of them have CWM or a different custom recovery. What ROM is it that you want to install? What I mean is you don't need to flash to multiple other kernels/ROMs before eventually going to whichever ROM you want.
[Samsung Epic 4G Touch] slick_rick:
Go to the dev section and find sfhubs fe22 Odin one click and flash your phone with that. The reason you do this is so you will be on a stock rom where you can update prl and profile. After you do this, using Odin (with only auto reboot checked in top right corner), flash the el26 cwm kernel. Boot into recovery and from here you can flash back to Frankenstein or blazer whatever you want. You will need a computer.

So...

1. Fe22 Odin one click

2. Boot into fe22 stock rom and update prl/profile

3. Odin the el26 cwm kernel

4. Flash whatever new rom you want.
[Samsung Epic 4G Touch] ScubaSteev:
Just the thing....I don't have a computer:p
[Samsung Epic 4G Touch] slick_rick:
1. Mobile Odin el26 cwm kernel

2. Flash this rom http://xdaforums.com/showthread.php?p=26478829

3. Boot into rom and update prl/profile

4. Mobile Odin el26 cwm kernel

5. Boot back into recovery and flash rom of choice
[Samsung Epic 4G Touch] ScubaSteev:
The fe22?

And sweet...easier then I thought,just gotta wait for download.

Thanks slick:)
[Samsung Epic 4G Touch] slick_rick:
Doesn't need to be fe22, but needs to be stock touchwiz or close to so you can update prl/profile and that rom will let you do so. No problem, I'm ways here to help.
[Samsung Epic 4G Touch] ScubaSteev:
Well can I flash el26 stock rom ?
[Samsung Epic 4G Touch] TeamERA:
Fixed in the new update, sorry. Hey scubaSteve, I remember that "sisters friend" thing :)
[Samsung Epic 4G Touch] oscarthegrouch:
Did you try booting into recovery, wipe cache and dalvik, reboot, then try to update again?
[Samsung Galaxy Nexus] freerider_4life:
I've searched here and google as much as I could and I cannot find out why I cannot get my nexus to unlock or even get to the part to root

I'm using Wugfresh to try and unlock/root, and after I install the drivers (64bit) i hit unlock, I get the first prompt that asks me if is see a string of numbers and letters, I do, so I continue and it puts my phone in to Bootloader, then asks me if i see the string of letters and numbers again, but I do not see them. Anyone have any ideas?
[Samsung Galaxy Nexus] efrant:
That is because you have to install the drivers TWICE: once when the phone is booted normally, and once when the phone is booted into the bootloader.

And you should really try to avoid toolkits and learn how to do it manually, so that if things mess up, you know exactly why. There are many tutorials around. (The "flash" link in my sig will show you how to unlock even though it is a how-to-flash-a-stock-ROM.)
[Samsung Galaxy Nexus] freerider_4life:
I tried doing it the manual way and I kept getting stuck. I come from a jailbreak iphone, a lot of this is new to me.

I'll give er a shot your way and I'll see how it goes.
[Kindle Fire Android Development] twa_priv:
After installing this ROM on my GT 10.1 I decided to use the same sources to compile a build for the Kindle Fire.

The result is a CM9 ROM with the Framework, Settings and Launcher/Trebuchet enhancements from the SGT7 project.

The SGT7 codebase features:

* Status/combined bar is highly customizable

* additional trebuchet settings

* Edge swipe navigation (can be used to quickly toggle the status bar with a single swipe)

* Show/hide statusbar from power menu

Other minor changes:

* Removed Camera, DevTools, RomManager, VoiceDialer and TelephonyProvider apks

* Enabled USB mass storage by default

* Disabled debugging notify icon on statusbar

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/

Download:

20120711 - Linaro (Alternate download)

20120708 - Linaro (Alternate download)

20120707 - Linaro (Alternate download)

20120703 - Linaro (Alternate download link)

20120628

20120628 - Linaro

See second post for the changelog.

Installation:

Make sure you have the latest FFF and TWRP 2.1.x installed

Make a backup !!!

Wipe data/factory reset

Wipe cache

Wipe dalvik

Install ROM

Install Google Apps

Reboot

I actually installed this build without a data wipe (coming from my own CM9 build with minor framework changes) and didn't have any issues. But YMMW - and if you have issues I suggest you start over and do a factury reset before flashing.

Thanks to:

hashcode

cdesai

sbradymobile

CyanogenMod

...

Sources:

https://github.com/sgt7

https://github.com/KFire-Android/kernel_omap

https://github.com/loosethisskin

Screenshots:
[Kindle Fire Android Development] twa_priv:
Changelog:

20120711

* Tweak: Different mount options for /data, /cache and /system

20120708

* Cherry-Pick: Frameworks-base: Fix wifi-sleep-policy

* Added new init.d script (02oom) which sets the lowmemorykiller as V6 would set them (thanks again to zeppelinrox and his work)

* Modified a services frameworks/base class to skip writing Out-Of-Memory (OOM) / lowmemorykiller values (which otherwise would overwrite the changes done in above init.d script)

20120707

* Fix tablet dock spacing

* Latest CM9/SGT7 changes

20120703

* Some kernel parameter and build.prop settings tweaks

20120629

* Compiled using hashcodes latest 3.0.31 kernel sources

20120628

* Clock status bar visibility fix

20120626

* Enabled Krait bionic optimizations

20120625

* Full 4.7.1 linaro build

* Deep sleep bug fixed

* Netflix/Youtube thumbnails are now properly loaded

* Additional optimizations

20120621

* Trebuchet: Added maximize workspace option to stretch desktop and disable tablet dock

* Fixes deep sleep issue of previous 20120620 build.

20120620 (Deep sleep issue - build removed)

* Add device settings OtterParts to control touchscreen filter. You might need to adjust the filter value after flashing. Go to Settings -> Advanced to do that.

* All sources/components compiled with linaro 4.7.1 (TARGET_TOOLS_PREFIX set to linaro)

20120617

* Fixes the sound mute bug.

* Kernel: Touchscreen sensitivity fix

20120614

* Kernel level touch filter and FireParts (shows up as Advanced category in Settings)

20120613

* CM9/SGT7 build using the linaro 4.7.1 toolchain.

* bootanimation: performance enhancements

* Cherry-Pick: build/core: Enable more optimizations

* Changed device config from mdpi to hdpi (thanks sbrady).

20120611

* New CID bootanimation

* Latest CM9/SGT7 framework, settings and launcher changes

20120608

* Edge swipe configurable distances

* Trebuchet settings UI changes

* Kernel includes hashcode's latest changes from today.

20120607

* Includes hashcode's latest kernel and device changes

20120605

* Make screenshot tone optional

20120604

* Experimental: Edge swipe navigation. It allows for customizable edge swipe actions including expand notifications, hide status bar, show recents panel, back, home, and menu. Screenshots here.

20120603

* Latest CM9/SGT7 framework, settings and launcher changes

20120602

* Add notification volume slider option to expanded combined entries

* New volume change tone preference

* Hide autobrightness toggle if it is not available

* Volume slider/mute button fixes

All thanks should go to sbradymobile for his changes/fixes.
[Kindle Fire Android Development] sthomas38:
Nice my friend :).

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] N3RD420:
Thanks running smooth so far
[Kindle Fire Android Development] serx7:
I really like the status/nav bar customizations, basically used them to add the power widgets & remove sliders that, for me, were just taking up space in the expanded status bar.

The Peek Notifications feature is kind of cool. The preview itself initially displays just above the status bar, but jumps downward over the status bar shortly before auto-hiding. Seems fine to me. (NOTE: if you select/deselect this option, the status bar disappears, but will reappear automatically after ~15 seconds. I assume this is the status bar being auto-restarted to kick in the change.)

Selecting the System -> Tablet Tweaks -> Recent Apps -> Large Thumbnails option fixed the display issue that the current Recent Apps list had - horizontally stretched & pixelated thumbnail images. W/ this option enabled, the Recent Apps thumbnails are now squared, aspect ratio of the thumbnail contents looks correct & the thumbnail contents are displayed (somewhat more) "crisply".

Thanks for this!

BTW, I flashed this over Trojan38's 5/28 Vanilla build with just cache/dalvik wipes. So far, no issues.

[Edit: One potential issue, but this might -not- be specific to this ROM at all (I never tried this on other CM9 ROMs for the KF). If I mute the volume using the 'mute' button to the left of the Expanded status bar volume slider (or if I use the power widget) and then unmute, the Notification volume is left at 0 instead of being restored to the previous volume slider setting. No biggie, just thought I'd mention it.]
[Kindle Fire Android Development] twa_priv:
You are right, this shouldn't happen. I'll see if I can figure out why this is.

Thx

Edit: This is fixed now (thanks to sbradymobile). New build uploaded.
[Kindle Fire Android Development] TexasRules777:
Hey twa..does this rom have the weather on the lock screen? Have really gotten used to that. :-)
[Kindle Fire Android Development] twa_priv:
Yes, it does.
[Kindle Fire Android Development] mdaa83:
This is definitely not specific to this ROM. I have experienced this in every CM9 ROM that I have installed on the KF so far. I think that this is the 5th that I have installed and I really like it so far; nicely done.
[Kindle Fire Android Development] twa_priv:
This unmute issue is fixed in the latest build. (and I don't think it happens on Trojan's vanialla builds).
[Kindle Fire Android Development] serx7:
Thanks twa_priv. Will d/l & install that in a little bit.
[Kindle Fire Android Development] foxdog66:
By chance, are these options submitted to cyanogenmod's code review? I'm assuming this is pretty much stock cyanogenmod with added customization options specific for tablets, is that correct?

Edit, I must say, these are some kick ass features! Just the kinda thing we need :D thanks for bringing them are way
[Kindle Fire Android Development] serx7:
twa: I just flashed the new build and retested the mute/unmute changes.

Looks good except for one scenario. If you fully expand the notification bar so that the volume control slider is visible and then click the Mute toggle that's located to the left of the Volume slider, the Volume power widget doesn't change to reflect the muted status. If you then set focus away from the fully expanded notification bar so that it auto-collapses, the volume remains muted, the Volume power widget still reflects an unmuted state, but the Volume slider's position is reset to 0.

So now, if you cycle the Volume power widget, Volume is not unmuted. If you fully expand the status bar to show the Volume slider, you'll see the Mute toggle is still enabled (fine) but the slider position is at 0 (unexpected). Sooo (oooh big deal lol) you have to slide the Volume slider back up to unmute :)

Really no big deal, but figured I'd mention it since I reported the orig issue w/ the mute/unmute behavior.

Aside from this (which I admit I rarely if ever do/will use), this SGT7 stuff is awesome.
[Kindle Fire Android Development] twa_priv:
That's probably not a device (otter) specific issue but rather still a problem with the sgt7 frameworks codebase - in fact I can reproduce it on my GT 10.1. I'll forward your findings to the sgt7 team.

Thanks
[Kindle Fire Android Development] TahrirSquare:
I love the customization this ROM offers, Is there any way to add a volume slider?
[Kindle Fire Android Development] sbradymobile:
I'll take a look, I think I know what the problem is.
[Kindle Fire Android Development] twa_priv:
Nice to see you over here ... just wanted to pm you (glad I don't have to bother you though).

I also noticed that there are also some synchronization issues between the mute button left of the volume slider and the volume button in the power widget.

For example, pressing the volume power widget button (so that the sound is muted) doesn't also update the mute volume slider button.

Thanks
[Kindle Fire Android Development] serx7:
Where do you want the Vol slider? There's one available in the status bar, selectable via Settings -> System -> Combined bar expanded settings -> Expanded settings entries -> Volume slider (need to scroll downward in the righthand pane to get to the entry)
[Kindle Fire Android Development] TahrirSquare:
I got that option checked but I don't see a volume slider still, also got a brightness slider checked but it's not there, All I got is the power widget
[Kindle Fire Android Development] pbailey212:
Use apex launcher and you can change the margins on your home screen

sent from my Nokia 5110
[Kindle Fire Android Development] twa_priv:
Here's a link https://github.com/KFire-Android/kernel_omap/pull/6 with a discussion regarding the touchscreen sensitivity.
[Kindle Fire Android Development] airmaxx23:
Any suggestions for the filter level value?
[Kindle Fire Android Development] twa_priv:
It was hardcoded to 70 in the previous build. That's a good start I'd think.
[Kindle Fire Android Development] airmaxx23:
I'm really liking this ROM but I see it has the same "wavy line" issue that the other CM9 ROMs have. Any idea what's casing it?
[Kindle Fire Android Development] twa_priv:
What app is this? So I can test it myself.
[Kindle Fire Android Development] airmaxx23:
Sketch Book Pro, Draw Something does the same thing when you draw a slow straight line at an angle. Straight vertical or horizontal lines are fine, the closer you get to 45 degrees the worse the waviness gets.

I started using this ROM yesterday and I've had two instances where uninstalling an app has caused my Kindle to reboot, any suggestions?
[Kindle Fire Android Development] webdroidmt:
Interesting, seems as in most things with choices, everyone has his/her own preferences. From reading the github activity, Intersect Raven seems to prefer a setting of 70 for basic use and 30 for stylus, while drkhd preferred 30 for basic use and stylus. Since I don't know how these parameters are gauged, seems like the difference between 30-70 is quite large.

Well, I just put it at 70 and I'll tweak if necessary. Thanks.

Mike T
[Kindle Fire Android Development] airmaxx23:
I've been messing with the setting today and I've settled on 20 for now. It makes the aiming controls in Max Payne work more smoothly and accurately for me and everything else seems fine so far.
[Kindle Fire Android Development] webdroidmt:
NVM, I misunderstood the sensitivity values. I just tried twenty, feels ok but I will test a few more settings to see where the sweet spot is for me for basic use.

Mike T
[Kindle Fire Android Development] imtoomuch:
I don't have that issue.
[Kindle Fire Android Development] serx7:
Anyone experiencing higher idle battery drain on the 0620 build vs the 0617?

On the 0617 build, I went from 100% to 88% in almost exactly 9 hours with < 8 minutes total screen on time (~1.33% / hr drain). On the 0620 build, I went from 100% to 71% in almost exactly 9 hours, also with < 8 minutes screen on time (~3.22% / hr drain).

On the 0617 build, CPUSpy showed about 50/50 300MHz and Deep Sleep (virtually nothing @ the higher clock freqs). On the 0620 build, CPUSpy shows virtually no Deep Sleep (2 minutes 12 sec, also virtually nothing @ the higher clock freqs).

Wifi was on the whole time in both test scenarios, and my timing/location history was exactly the same (off charger @ 100% in the morning, screen off, put in bag, drive kid to daycare, drive to work, check email quickly a few times during the day, screen off otherwise, check Kindle batt level before leaving the office).

[Edit: b/n both test runs, Badass Battery didn't show anything suspicious/different in terms of excessive wakelocking/time held awake... as far as I can tell]
[Kindle Fire Android Development] twa_priv:
It might very well be that the linaro changes introduced some issues. Frankly, I haven't been longer than a few hours on a single build in the last few days because I constantly tested new compile options / tried to fix things.

But on the other hand - you're the first one who reports this issue. But the build is not even out 24Hrs, so we'll see.

I finally managed to do a full linaro build using -O3 -fstrict-aliasing for arm, thumb and kernel modules. All still seems to work, I managed to even get the MX Player runtime linker error fixed. Benchmark results seem to be a little better than on the current build.

I'll post a new test build later today.
[Kindle Fire Android Development] lovejoy777:
hi twa_priv

are you receiving any new messages from me? as the message i sent you doesn't show up in my sent messages (sorry for out of topic)

cheers steve
[Kindle Fire Android Development] twa_priv:
Yes, I just replied. You need to change your xda prefs to keep sent messages :)
[Kindle Fire Android Development] x0xhellx0x:
Love your work man and thank you for your additions to the kernel no I can dynamically build again much respect
[Kindle Fire Android Development] twa_priv:
Thanks.

I've made a few more kernel hacks (modified a few makefiles) to allow the kernel to be compiled in strict mode (not sure if it really has a performance benefit though - but I did it anyway :))

Those, other fixes related to strict-aliasing in about 8 other repos and more changes to android_build now allow me to build all (arm, thumb & kernel) with strict-aliasing.

Everything I usually test (netflix, mx player, hd videos ...) still seems to work.

But it seems there might be some battery drain issue going on in my recent build ... would have been too easy otherwise :)

I'm going to push all those to my github when I get a chance. Maybe I'll also post my local manifest so that more start playing around with linaro also - and supply possible fixes.
[Kindle Fire Android Development] x0xhellx0x:
I'm just glad to be part of the big picture and get some good stuff out to people
[Kindle Fire Android Development] lovejoy777:
all sorted

still compiling

defo need new pc if im going to play like this :-)

thanks again steve
[Kindle Fire Android Development] da-pharoah:
Haven't ran this, yet, but it looks sweet bro! good job and keep up the good work bro! :)
[Kindle Fire Android Development] serx7:
No worries, at all. Just figured I'd share what I had observed to see if anyone else was seeing the same thing. Things have been busier than usual @ work the past few days, so the KF sits idle a lot more than usual for me.

I wiped everything and restored my 0617 backup, then let it sit for ~3.75 hrs on the restored 0617 build. Batt rundown returned to what it was before (ie: slower burn down than the 0620 build), and CPUSpy indicates just over 3 hrs in Deep Sleep, ~33 min @ 300MHz, the remaining few min at 1008 & 1200MHz.

Battery Monitor mV vs time plot is below. The longer (and steeper) burn down was on the 0620 build, the shorter (and shallower) burn down is after the 0617 restore.
[Kindle Fire Android Development] xari228:
Yes, me!

I usually use my KF to read/play games during lunch at work, but then it'll sit idle from about 1pm 'til 10:30pm (bedtime).

On previous builds, I usually only would lose 3-10% during this idle period.

Yesterday, on the 0620 build, my KF was at 51% when I put it to sleep at 1pm, but was all the way down to 15% when I woke it up at 10:30pm.

[I don't know if it makes any difference, but I usually have my CPU governor set to OnDemand, but yesterday I had decided to try it on Interactive. I charged to 100% overnight and have switched back to OnDemand and plan to stay with the 0620 build today to see whether that makes any difference.]
[Kindle Fire Android Development] xari228:
Oh dear.

From 6am - 10am I lost 14% during idle (0620 build, OnDemand governor).

Am reverting to 0617 build.
[Kindle Fire Android Development] twa_priv:
I'm going to take down the 0620 link until the deep sleep issue is sorted out.
[Kindle Fire Android Development] twa_priv:
New 20120621 build is up. Not linaro this time - deep sleep works fine again.

I keep looking into what broke it and once I figured it out I'll post a new optimized linaro build.
[Kindle Fire Android Development] airmaxx23:
Thank you, downloading now.
[Kindle Fire Android Development] serx7:
Cool, thanks twa.

But what about my Quadrant scores? KIDDING :D
[Kindle Fire Android Development] sbradymobile:
I just updated Trebuchet with a maximize workspace option. It disables the dock and stretches the cells to fill the area.

@twa_priv Let me know if it needs adjustments for 10" tabs (code in sgt7 github).

The touch filter included is only for the initial down event. Without the filter simple touches are translated into moves which can cause issues with views that have move handling (e.g. expanding the notification bar). The waviness seems to be a side effect of Android's touch coordinate scaling that occurs with slow drags (more touch points) rather than a device specific flaw. My Galaxy Tab, for example, displays the identical behavior of a fast swipe looking straight and a slow swipe looking wavy.
[Kindle Fire Android Development] raiderep:
Damn, I've been so obsessed with my new EVO I forgot about my kindle...poor thing! Just flashed the 6-20 build before bed and it is really nice. Trying this linaro system for the first time and will be looking forward to your fix for deep sleep. I guess I better start making time for my kindle again!

Sent from my EVO
[Kindle Fire Android Development] twa_priv:
Thanks.

My current build is only missing the last "Adjust maximize workspace cell spacing for small icons" commit and it seems to work well. But I'll kick off another build which includes this one and upload it later on.

Was 10'' tabls a typo ? The KF is 7'' - but I'll also make a build for my GT 10.1 Wifi later on anyway :)