yashsingh1/xdaforums huggingface dataset:
[Flipside General] Dejamac:
Picked up a Flipside for my daughter for Christmas 2010. It is an entry level Android phone. To summarize our experience so far:

Pros: The phone itself is reasonably solid. Slide out keyboard is performing well. Touchscreen has good accuracy and adequate resolution. Daughter happy with texting performance. Reception for 3G has been as good as any other phone in our household. Call quality is not as bad as some other reviews indicated.

Cons: Battery life is terrible. Have yet to make it through 3/4 of a day on a charge. The camera quality is poor at best (no flash) and the camera lens has already cracked although I can't see any evidence of a drop or other damage. The MotoBlur interface is clumsy and seems to make the overall UI lag terribly. It suffers from random lag related issues as button presses are out of sync. No support in dev community for custom ROMs for this phone.

Recommendation: If you are new to smartphones and have to rely on a stock UI to do social networking for you it's not a bad price - go for it. If you are somewhat savvy, stay away. The MotoBlur interface will frustrate you in terms of quality and the drain on performance and battery life. We rooted the phone but are struggling to get the right combination of MotoBlur apps deleted to improve performance without crashing the phone. I will not buy another phone with MotoBlur installed and am considering trading out of this one so we have the option of applying custom ROMs.
[Flipside General] rvt1000:
Backflip

Sorry, a bit off topic but I can't figure this out.

I didn't see any threads for the Motorola backflip. Does that mean there is NO development for it? No rooting? No Roms? Or am I just missing something? Can anyone point me in the right direction??

Thanks.

I've found some development on other forums like theunlockr, attdroids, androidcentral. Was hoping for some development here on XDA but guess it doesn't exist.
[Flipside General] Trey_Richards:
Check over at ModMyMobile, they have an awesome Backflip community. I'm running CM6 on this Backflip.
[Flipside General] squ1rr3l:
My experience was not dissimilar, but unlike pretty much everybody else, I actually like motoblur (that is, I like having my facebook, twitter, gmail and phonebook contacts unified into a single set of contacts) - it's handy. But, as you say, it drains the hell out of the battery. Here's what I did to fix it, without rooting the phone.

I installed LauncherPro and use that has the home replacement. I don't use any social networking widgets. I use the facebook and twitter apps instead. I now consistently get 24 hours on the phone between charges. I had to factory reset the phone a couple of times experimenting to get this to work consistently.

Also, *NEVER* use the pre-installed task manager to place apps into the "auto-end" list. They just re-start, and it really kills the battery power.
[Flipside General] JBallin4life27:
Wow never heard someone say they like motoblur...but that's good info to save battery life
[Flipside General] sharethl:
I got one few days ago, hope the custom rom could come out.
[Touch Pro2, Tilt 2 Themes and Apps] htcuser12:
I remember someone mentioned an application to clean up rom area on the phone to remove any unused files left behind after upgrading/changing roms. I dont recall what the application name was or what to search for. Does any one here know the app that I am referring to?
[Touch Pro2, Tilt 2 Themes and Apps] Miami_Son:
Do a search for Task29. This is used when you do a lot of ROM flashing and want to make sure no remnants of previous ROMs are left behind. Nothing can delete files from ROM individually.
[Touch Pro2, Tilt 2 Themes and Apps] htcuser12:
Thanks

Thank you:):)
[Touch Pro2, Tilt 2 Themes and Apps] redpoint73:
To clarify, Task29 formats/wipes the entire memory where the ROM resides. You do it before flashing a new ROM. Not sure if that is what you were looking for, or not.
[Bravo General] svetius:
This is a placeholder for discussion about the new Motorola Bravo for AT&T.
[Bravo General] no clue:
Argh... all att android phone.

well... att care about copyright so...

Unable to install non-market app ( beside rooting and install w/ adb )

and att really care about users, so it can monitor my data traffic,..

Unable to stop Att bloatware on the background ( address, contact, and etc )

But, ( if you don't want to be restricted )

user must learn:

How to root the phone

How to safely use Titanium Backup

Other than that, Brovo rocks. Att? After 10 years with them, I recently move to t-mobile. :)
[Epic 4G General] ZenInsight:
First time I've tried to start a thread. I know that that USB host works on the Nexus one and Droid X. I'm not sure if it should work on any Android device as long as the correct drivers are used. I also don't know what file structures it can recognize (i.e. NTFS).

Anyone care to join a discussion about the possibility of doing this on the Epic?

Original Nexus One thread-

http://xdaforums.com/showthread.php?t=694427
[Vibrant Android Development] zaduma:
Wow, I am afraid to mess with this today. (expecting an important phone call)

I will flash it tomorrow morning however. And post some results, I have an idea about what to do with this.

Thanks Travis!
[Vibrant Android Development] ttabbal:
I hope you find it useful! I forgot to note one thing. If you want to see what your pre-init scripts are up to, there's some info in /init.log. Not a ton, but you can at least see if your script was started and such from there.

Also, if anyone cares, it works on Frankin-Twiz Final. :) I decided to check it out once I got this little project working.

I'm curious to see what people come up with, I've seen some complaints about not being able to edit the ramdisk without building a kernel. So now they can. :)
[Vibrant Android Development] justanothercrowd:
You mind sharing your init setup. I am familiar with Unhelpfuls method and just want to see what you have changed from his.

I stayed away from his method with Voodoo as it was causing issues at diff points of development and went with the run-parts solution. But it may be in better shape now that you have gone over it.

Most users will only need one hook but options are always good. :)

I've always been one the fence about the runtime OC/UV. Most people are looking for a stable voltage file that will work with their phones in the thread, but it is def awesome for those that are familiar with what they are doing.
[Vibrant Android Development] eugene373:
Talk to braka, we been hi-jacking the init for a bit, I've been working on getting a Desire pport working on are rom.. ( Well, barak has been hi-jacking the init ) I just build kernels.
[Vibrant Android Development] ttabbal:
The whole ramdisk is here:

http://github.com/travistabbal/linux-galaxy/tree/ttabbal-v1.0/usr/initrd_files_t959/

The pre-init stuff is in /init.sh.

The basic stuff is the same as his really, I just put the sync hooks in to stall the boot based on an older version of his stuff. The current version didn't seem to work for me. The boot didn't wait, and I couldn't see any reason it would, so I just used the property setting style.

As I said, I haven't tried voodoo with it yet, but I don't see any reason it wouldn't work. You might want to pull the "exec /sbin/init" out if you want more pre-init scripts available, but other than that, it should work fine. A fair bit of the ramdisk came from your voodoo release, useful stuff in there. :)

If you see any issues with the init.d stuff, let me know and I'll look into them and if I can fix them, send a pull request over to Unhelpful.

Yeah, 3 hooks is overkill, but I figured there might be some use for them all. Most scripts can run in the "standard" hook and work just fine.

I kept the runtime OC/UV stuff just because it was more work to take it out. :) If you have a nice stable file, I'm happy to include it in the downloads as a default. I'm sure I could pull at least older versions from your github, I honestly haven't messed with it much beyond adding the 600Mhz step and seeing that the phone would use it. I honestly don't see much call for changing that stuff constantly at runtime, but it's nice for experimenting. If it crashes due to low voltage, just reboot and no harm done. :)

As I'm sure someone will ask, no I won't test it with voodoo. I can't, my phone has the extra NAND so it's not compatible with voodoo. :) When Beta5 comes out, I'll test it though.
[Vibrant Android Development] ttabbal:
I'm uploading a 1.1 now. The only big change is that I've fixed the backlight notification patch from Unhelpful's tree so it works with Vibrant now! Install the kernel, then copy lights.default.so to /system/lib/hw to get apps able to use it. Anything that can do LED notifications now turns on the button backlights instead.

See the other BLN threads for Q&A's, etc.. The big one, no, we can't flash/fade the LEDs. It would require changes to the binary firmware and nobody wants to try writing it.

http://www.tabbal.net/files/t959-ttabbal-v1.1.tar

http://www.tabbal.net/files/lights.default.so

This has been tested on my phone running Bionix 1.7 and worked with the MMS and GMail apps. I haven't tested the others.

Again, it's an Odin tar file. Put it in the PDA section and flash. If people ask for an update.zip, I'll put one together.

The warning above applies. This flashes a kernel, so it will overwrite whatever you have now. So if you have voodoo, disable it or add the voodoo script to init.d with an E prefix ie. "Evoodoo".
[Vibrant Android Development] dzeinz:
Thanks

I've been looking forward for a way to use the backlight buttons as notification since the phone came out and the idea was hatched a few days later. I'm admittedly new to all this so I have no idea what else this is capable of but I am VERY thankful for the button lights. Also there is another xda thread up with many replies and people offering up some rewards for making this work.
[Vibrant Android Development] skater991:
Can this be applied to eugenes froyo ?
[Vibrant Android Development] ttabbal:
Rewards? Heh... I had no idea people were that interested in it. :) Hope it helps. My github has source, so I hope other kernel devs for vibrant add it.
[Vibrant Android Development] ttabbal:
Not sure. Froyo usually needs a different kernel. If JAC or KK kernels work, this one should. At worst, it will boot loop and you will have to flash a compatible kernel in download mode. So make sure you can get into download mode before trying it.
[Vibrant Android Development] bahnburner:
Thanks for this. It's working great, and I'm so glad to finally have backlight notifications.
[Vibrant Android Development] metalfan78:
Definitely would like an update.zip, just not comfortable doing it through odin...but I would love to have this

The cake is a lie!
[Vibrant Android Development] ttabbal:
Well, since you asked nicely. :)

http://www.tabbal.net/files/Kernel-ttabbal-v1.1.zip

MD5: 606a1ecaa934f97bd26f0bfb617b23b8

Tested just now via Clockwork. It even installs the library for you, so the button notification should work out of the box.

Running great for me on Bionix 1.9.1.
[Vibrant Android Development] metalfan78:
Wow...thanks, ill give it a go. So just flash through clockwork and good to go?

The cake is a lie!
[Vibrant Android Development] ttabbal:
Yup. :)

Let me know what you think.
[Vibrant Android Development] s0niqu3:
Is this ready for overclocking like JAC's OC/UV kernels? If so, any chance of posting a demo script for the OC/UV settings?

Also, can we add a user-script to enable AOSP bootanimation.zip files, or is support still commented out in this kernel?

Thanks for your time and hard work, cheers, =)
[Vibrant Android Development] d_bot:
I have been wanting button notification since i got the phone. Can you choose which button lights up based on what the notification is?

for example menu = txt, home = missed call, etc....that would be awesome!
[Vibrant Android Development] ttabbal:
It's based on Unhelpful's way of doing OC/UV, you have to modify a file and push it to the phone to enable it, then set up the min/max settings with a script or SetCPU. There's a lot of detail over in Unhelpful's thread on the Captivate forum, so it's probably better to point you over there. They have scripts and such for it as well.

Not sure on the boot animation. I'll see if I can find it.
[Vibrant Android Development] ttabbal:
That would be awesome, but it's not that complex. It's all of them for a notification. The Android API wouldn't really be able to deal with that level, but perhaps we could assign the buttons colors and use the color that the app requested? Maybe, but I'm not sure we can turn on just one of them from the code we have right now. The code looks to make a somewhat simple call that turns them all on at the same time. Hopefully as more people look into things, we will learn how to do stuff like that.
[Vibrant Android Development] d_bot:
well it's a step in the right direction, much rather have any notification light to no notification light.

Thanks for the work man!
[Vibrant Android Development] metalfan78:
Thanks, just flashed, on bionix 1.9.1, now I just have to wait for something that needs a notification............lol

The cake is a lie!
[Vibrant Android Development] s0niqu3:
Thanks for the help.

Do you know of any way to reading the OC/UV settings from JAC's kernel (without having to download his source) so I can make my own freq_volt_table that mirrors his settings?

Cheers, =)
[Vibrant Android Development] Siks:
Did Samsung ever release source for the JI6 update or is this based on JFD? Just wondering if I'd have to flash the files req. for older kernel support first as I haven't yet since updating.

Sent via XDA app on my SGH-T959UVJI6 Vibrant.

(Root/Deodex/MobileAP/AccurateBattery)
[Vibrant Android Development] ttabbal:
I don't. I asked if he wanted to share his settings, but he never replied. You could check his github, but you would have to dig in the source. I think I have an idea where to look, but haven't had time. If I find something, I'll post it here.
[Vibrant Android Development] ttabbal:
I haven't seen any ji6 source. I think you do need the kernel compatibility files. Just flash bionix on there. :) It really is nice.
[Vibrant Android Development] In Absentia:
Has anyone checked out the hardware to see if this is even possible? For example, how many LEDs there are and if they're just plain white or multicolor LEDs? My guess is that, for simplicity (since it doesn't seem like Samsung intended for this kind of functionality), it's just a single, white LED that lights up all four buttons or nothing.
[Vibrant Android Development] speedysilwady:
GT

They are 4 individual leds but I don't believe they change color...but it would be so awesome if they could lol
[Vibrant Android Development] xavyi:
I agree. if somehow they could change colors, this would be amazing!

I'm looking forward to trying this on my phone, been waiting for this since i got my vibrant!

+1
[Vibrant Android Development] vamopyros_wrath:
If anyone can upload the cpu_freq_table from JACs or Kings OC kernel, then ill try this. I'm a little apprehensive to change it myself considering I don't know what settings to use, and both of the kernels I mentioned work fine for me, so why fix what ain't broke. I just really want the buttoned notifications top notch work ttaball!
[Vibrant Android Development] bdveteran18:
First off I would like to thank you for all of the work you have put into this. Very neat project and a lot of people have been wanting something like this so kudos to you.

I planned on flashing bionix 1.9 today and was just double checking my steps before proceeding. This is an update for the Kernel and notification mod? Once I'm done flashing bionix, I just flash this update.zip on top via clockwork? Also which level of bionix are you using? Thanks in advance!
[Vibrant Android Development] ttabbal:
Glad to see interest. :) yes, it updates the kernel and adds the backlight notifications. It should run fine on any rom that jac and kk kernels run on.

I am on bionix 1.9.1, it's a very nice rom. I flash the rom, do the reboots and such and make sure the basics are working before I change out the kernel. Probably not nessicary, but it limits the variables if something doesn't work.
[Vibrant Android Development] opiomorph:
Just to make sure I'm understanding this correctly: I'm running Bionix 1.9.1 with KK's OC/UV kernel. If I flash this .zip, will that replace KK's OC/UV kernel with yours so that I lose OC/UV, or will it just update the kernel to enable the LED notifications?

Separate questions: how does the LED notification light behave? That is, when you have notifications, does it blink or just stay on continuously? Also (and I may be getting ahead of myself here), is this behavior customizable?
[Vibrant Android Development] bdveteran18:
Ok thank you for the speedy response. I am just going to run the stock kernel and give that I try with this. Thank you again
[Vibrant Android Development] rizzxx7:
Does the entire row suppose to illuminate or just the back button ?
[Vibrant Android Development] In Absentia:
Thanks, good to know. Looks like it's time for a new hardware mod: RGB LEDs! ;)
[Vibrant Android Development] bahnburner:
I did notice one issue. This kernel disables USB debugging on reboot for some reason.
[Vibrant Android Development] ttabbal:
Interesting.. That's not happening here. Any other info about your setup?
[Vibrant Android Development] bahnburner:
JI6 leak, lockscreen mod, evo blackbar, nakedtw, and epicish themes, no lagfix.

Not sure what's causing it. Gonna wipe and flash to JI6 OTA and see if that takes care of it.
[Vibrant Android Development] rizzxx7:
Not happening for me either
[Vibrant Android Development] vamopyros_wrath:
Can someone please post their cpu_freq_table? I edited the one that came with it for 1.2ghz, but it caused a whole bunch of force closes somehow...also the backlight notification buttons did not light up for texts? That's odd, considering its supposed to work with that recovery zip ttabbal uploaded...I'm running bionix 1.9.1 with no lagfix...
[Vibrant Android Development] ttabbal:
Did you turn on led notification in the app? I think it's disabled by default on the messaging app.
[Vibrant Android Development] bahnburner:
Full factory reset, then flashed JI6 OTA, kernel backwards-compatability package, then the kernel. Same issue. I enable USB debugging, reboot, and it's disabled again.
[Vibrant Android Development] kaine13x7:
Very good questions and pretty much sums up my questions as well.
[Vibrant Android Development] ttabbal:
The kernel replaces whatever kernel you have now. It does have oc/uv capability, but it is disabled by default.

The lights stay on, no flashing. It's a limitation in the binary only firmware. That's the reason it's not customizable as well.
[Vibrant Android Development] opiomorph:
So can I just use setCPU to set the clock speeds like I do with my current kernel?

Also, please excuse the ignorance on my part, but I'm surprised that if you can turn the lights on at all, you can't start some kind of timer and have it turn the lights on and off at set intervals.
[Vibrant Android Development] ttabbal:
Oc is disabled by default. You need to write to the freq_volt_table file to enable it. Then you can use boot scripts or setcpu to turn on the oc side. The details are in the thread in the captivate forum, unhelpful's kernel thread. This kernel is based on his and does that the same way. I'm planning to try to get a stable setup and will probably provide an update zip for those that want oc/uv.

We could do the timer thing you mention, but it would require waking up the cpu every time, which burns battery. I think the i9000 guys tried it and it was just too battery hungry. It might be possible to do it in the kernel driver with a timer interrupt, but I'm not sure if anyone has tried that kind of low level stuff or if there is an interrupt available to use. It would still pull the cpu out of sleep mode though.
[Vibrant Android Development] opiomorph:
Thanks for the info! Like has been mentioned in the the thread already, people have been waiting for this since release day.
[Vibrant Android Development] xanderdad:
I have this installed on my Vibrant running the Master emperor 1.1.2 ROM. It works awesome and installed first try through clockwork. However I tried to install this on my wife's Vibrant running JI6 and it just hangs at the Samsung Vibrant screen. I tried clockwork and through ODIN. I restored her phone through ODIN and tried again fresh and still had the hang issue.

Any ideas?
[Vibrant Android Development] ttabbal:
Try flashing the old kernel support files. That is probably required for the stock ji6. Bionix and master include them for you.
[Vibrant Android Development] vamopyros_wrath:
I flashed the kernel again just to try, but it force closes better keyboard and hangs when I try to use said keyboard also there is no option in twmessaging to turn on led notifications so... I thought it turned on the buttons for anything that had a status bar notification like unhelpful. I also need to find a working cpu_freq_table so if anybody could upload theirs that would be awesome. thanks!
[Vibrant Android Development] mentalex2:
First off, thank you so much for this kernel. I've flashed from JACS to this, and back to JACS with no problems whatsoever. I want to keep this kernel on at all times, but I'm just curious about its battery use. Compared to JACS OCUV 1.1, how would you say this kernel performs battery wise?
[Vibrant Android Development] ttabbal:
Not sure why better keyboard would have a problem. Anyone else have it? I like swype fine so I don't want to buy it just to test. I wish they had a demo version.

This notification code is the same as unhelpful's. I just made it work on the vibrant. I think all these mods require the app to ask for the led notifications. For messaging, there's cent or aosp.
[Vibrant Android Development] xanderdad:
Sorry if this is a rookie question, but where are the old kernal support files and how do I flash them with ODIN?

I greatly appreciate your effort and support.
[Vibrant Android Development] ttabbal:
This kernel defaults to stock voltages and clocks, so battery should be about the same as stock. You can try editing the freq_volt_table to enable under volting, but it might cause stability issues. I'm planning to check jac's source to make a file based on his settings for people to start from.
[Vibrant Android Development] ttabbal:
Use the search in forum button and search for "kernel back support" by eugene. I'm on my phone and the app doesn't let you copy/paste the link...

If it's a zip and you can't get to recovery, use odin to flash a different kernel, but recovery should still work.
[Vibrant Android Development] bahnburner:
Notifications work on samsung messaging for me.
[Vibrant Android Development] xanderdad:
Will do. Thanks a lot for your help.
[Vibrant Android Development] d_bot:
thanks for this man!

Really enjoying notification lights. can't wait to see what else will come from this. thanks again.
[Vibrant Android Development] s0niqu3:
Hi again,

I was wondering if you have any plans on porting unhelpful's fixes to CWM recovery to this kernel? It seems with 1.6 he switched from the stock recovery to clockwork, and he managed to enable ext4 support in CWM, so voodoo users won't need to disable voodoo to read/write to the data partition, wipe dalvik-cache, etc.

He did mention that update.zip files would need to be re-written to support the ext4 data partition, though I've yet to find the specifics on it.

Anyway, thanks again for your work, any headway on JAC's freqeuncy settings too? Or tracking down the en_GB bug?

Cheers, =)