yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Markuzy:
On ICS? Try disabling like mentioned via settings>applications if you are on ICS

Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] xaad.xahid:
Thnxx guys for replying what if i replace the firmware with the international note firmware would it remove these apps ??
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] shivg86:
First of all umust be rooted to uninstall them and second framework has nothing to do with this.

And it is already advice that your phone is different fdom int ver of gtn7000
[myTouch 4G Q&A, Help & Troubleshooting] InvisibleNinja98:
I would like to keep the phone on Gingerbread, and remove all Sense, but keep the Android-Sense UI (example, Status Bar, settings look, etc.) I know I probably don't need QXM2SD and could someone tell me what that does? I'm curious...
[myTouch 4G Q&A, Help & Troubleshooting] saranhai:
not really sure what you mean...but here's a TouchWiz ROM in case you're interested http://xdaforums.com/showthread.php?t=1826792

sorta confused by your title and your question, your title asks how to port a TouchWiz ROM but your question asks how to remove Sense? lol

so i guess i'll answer both your questions...

Port TouchWiz: I don't recommend you doing this, it's a LOT harder than you think, since HTC Devices weren't designed for TouchWiz and vice versa. the closest to you can get TouchWiz without going through the pain of porting all the framework and apps and stuff, is with the ROM link that i posted above.

Remove Sense: Depending on how much Sense you want to remove, just delete the Sense apps you don't want. i assume you wouldn't want the launcher anymore, so delete Rosie.apk from /system/app. maybe you don't want the widgets anymore, delete them from the same location, /system/app.

hope i've answered your question, please be a bit clearer next time. :)
[myTouch 4G Q&A, Help & Troubleshooting] InvisibleNinja98:
Will that touchwiz work on ice cream sandwich too?
[myTouch 4G Q&A, Help & Troubleshooting] saranhai:
i don't see why it wouldn't. though you would need a newer version of TouchWiz, kinda like how Sense 2.1 wouldn't work on ICS.
[myTouch 4G Q&A, Help & Troubleshooting] InvisibleNinja98:
Didn't mean Ice Cream Sandwich, my fault. I meant Gingerbread.
[myTouch 4G Q&A, Help & Troubleshooting] THEindian:
Don't try it man, it won't be fun. Besides, touchwiz GB would be really difficult because most of the devices that ran touchwiz in the GB used the hummingbird processor. So processor incompatibility, have fun recompiling kernel source with andrendo and qualcomm drivers. Don't even get me started on wifi modules, ram, camera, screen. Its a lot easier on ICS.

One ICS, take an ICS rom as a base and port the framework(WHICH IS NOT EASY)
[myTouch 4G Q&A, Help & Troubleshooting] InvisibleNinja98:
Sounds like I just won't do it then..
[myTouch 4G Q&A, Help & Troubleshooting] saranhai:
hey man, we're not trying to discourage you or anything, if you really want to give it a shot, by all means! who knows, maybe you'll be able to do it :D

we're just warning ya and giving you a heads up of what it would be like if you were to try porting it.

if you wanna port it, by all means do it! don't let us hold you back :p
[myTouch 4G Q&A, Help & Troubleshooting] THEindian:
If anything, try ICS first, you wont need to edit the kernel as much as you would have to with GB
[myTouch 4G Q&A, Help & Troubleshooting] InvisibleNinja98:
It's all good.
[Droid Incredible Q&A, Help & Troubleshooting] kirkers:
So, I followed Scoty85's guide to downgrading to Froyo and re-upgrading to Gingerbread to achieve root + S-OFF. It all worked.

But then I ran into trouble with WiFi reception. The only time WiFi had worked well was the brief time I was downgraded to Froyo (2.2).

So I decided to flash the Froyo ROM. I thought that since I was now rooted, I could simply wipe everything except internal storage and the sdcard and install the same ROM I had used for the downgrade. I renamed it PB31IMG.zip so that HBOOT would automatically install it.

What a mistake that appears to have been! HBOOT shot out messages about "wrong image" and "no image", but then it seemed to go to work and parse the zip. It asked to install all sorts of things (boot, system, etc.) and I said yes (perhaps a bit foolishly...)

After the installation, the DINC worked okay, but every time I tried to boot into HBOOT and select "recovery", I got a red triangle and exclamation point and the phone froze. Only a battery pull could change things.

I then tried using ADB with the phone tethered via USB. Every command related to flashing ROMs or gaining superuser access produced "ERROR".

I renamed Clockwork Mod (CWM) Recovery 5.0.2.0 to PB31IMG.zip and got it to install via HBOOT. It ran for exactly one session, and then the red triangle scenario played itself out after that.

The only thing that saved me was following the entire procedure laid out on the EVOrootwiki website, which included zergRush allowing superuser access through an exploit. That does not work anymore in Gingerbread, so I was lucky to be in Froyo when I had my problems.

So I am home and dry, back in Gingerbread 2.3.4, but completely uncertain how to flash a ROM safely.

Should I only use "install from zip" and never use the "PB31IMG" approach? Is that why I had so much trouble?

I certainly will not do anything until I get greater clarity about how to go about this.
[Droid Incredible Q&A, Help & Troubleshooting] thehiggins:
I've flashed a dozen times using CWM's "install from zip" without any problems. I've never tried it via HBOOT in the manner you described. What I would do if you're feeling nervous is make a nandroid backup while everything is back to normal, so you can have peace-of-mind knowing that you can easily revert back to your current state. Next, flash whatever ROM sparks your interest using "install from zip" in CWM and everything should work out just fine (and you have your insurance now in case it doesn't).
[Droid Incredible Q&A, Help & Troubleshooting] ra9b:
There is no need to be worried. CWM usually runs the script prehand to see if it could harm your phone. If it can, you will get a message that says "installation aborted." Make a nandroid. Also, be sure to wipe data from the recovery screen, and then go to mounts/storage, and the format boot and system.
[Kindle Fire Q&A, Help & Troubleshooting] dcox52:
I was trying to root a kindle fire demo device and was able to get root and use it on the internet then I tried to remove the demo loop and now I have lost the operating system and it just sits there with the kindle fire logo and nothing works . HEIP me please I am fairly new at doing this.
[Kindle Fire Q&A, Help & Troubleshooting] kishorev:
Please go through the posts in Q&A section.. you will get a solution for this problem

Or you can post it Q&A section and you will get some quick solution..

Cheers
[HTC Desire S] Dabbleh:
Ok, so I was wondering whether anyone has ordered after market batteries before? Is it worth upgrading the stock battery? It seems that my battery won't even last a day.

Any reliable brands?

Thanks,

Dabbleh.
[HTC Desire S] ben_pyett:
Mugen.power battery is good, but it's not the batteries fault that they don't last a day, it's down to usage.

with realistic smart phone usage (which means active screen on time) no battery will last over a day.

They're are several threads on this subject in the accessories part of the forum, use search.

Sywepd form my DsereiS
[HTC Desire S] Dabbleh:
I did use search, it appears that some threads avoided my query.

Am looking in right forum now, this thread can be deleted.
[Sony Xperia P, U, Sola, Go] parthsony2000:
Hello everyone.

I have Xperia P (not rooted) and today got the OTG cable and tried it with transcend pen drive (16gb) but it gave error "High USB power counsumption. Please remove the device"

The same cable and pen drive works fine with my friend's Xperia S.

Please help me to get this issue fixed.

Sent from my LT22i
[Sony Xperia P, U, Sola, Go] CSL00:
Maybe the S and the P have different limits on OTG power consumption, they are different phones with different hardware after all (CPU, GPU etc), I use a Nokia OTG cable on my Xperia U and got a Sandisk 32gb working fine even on the stock ROM & kernel (i'm running both custom atm :) ).
[Sony Xperia P, U, Sola, Go] parthsony2000:
Thanks I'll try it with Nokia cable

Sent from my LT22i
[Sony Xperia P, U, Sola, Go] LastSoul88:
try use with usb hub...
[Sony Xperia P, U, Sola, Go] RavinduSha:
as far as I know Transcend pens doesn't work with usb otg. I have tested. here are my results

2GB kingston - working

4GB kingston - working

2GB transcend - not working

4GB transcend - not working
[Sony Xperia P, U, Sola, Go] Ruliindrapraja:
I have test too n my result

4GB, 8GB, 16GB Toshiba - working

4GB, 8GB, 16GB Sony - working
[Samsung Galaxy Fit GT 5670] Galaxy_Rohit:
Hi friends, Please suggest how to change fonts in Cyanogenmod 7.x as there is no similar option in settings unlike some stock based custom roms... :(
[Samsung Galaxy Fit GT 5670] dheeraj (dhlalit11):
https://play.google.com/store/apps/details?id=com.martino2k6.fontchangerlite

this is the thing which you need
[Samsung Galaxy Fit GT 5670] Galaxy_Rohit:
Thanks a lot...
[Galaxy Ace S5830i General] Qnrx:
when i was looking around on s5830i General forums i found something VERY Interesting...

in thread: http://xdaforums.com/showthread.php?t=1902313&page=2 someone posted that s5830V has the official samsung ICS rom.

so i went to check that on samsung's open source and guess what.

when u type s5830V in the search box on opensource.samsung.com it comes up with a file called GT-S5830V_SEA_ICS_Opensource.zip

The user that has V Model of the phone could succesfully flash a s5830i Rom on his device thru Odin 1.85, which means the V model has the same chipset as i Model.

Right now im downloading the zip file and will look around in it, but since im not that good at examinating rom's would someone please help me do it?

~Qnrx.
[Galaxy Ace S5830i General] GermainZ:
You'll need to compile it before flashing anyway.
[Galaxy Ace S5830i General] Qnrx:
i am going to compile it
[Galaxy Ace S5830i General] GermainZ:
I would highly suggest a backup phone. Nandroid backups won't do much if your hard brick your device.
[Galaxy Ace S5830i General] ZakooZ:
That ROM(sourcecodepackage) has a gingerbread build, I don't know why they called it ICS
[Galaxy Ace S5830i General] sgdva:
What you mean by that? A Nandroid won't get back the phone in a hardbrick? Only the usb jig?
[Galaxy Ace S5830i General] shariqx:
Working?

Did you complie and try the ICS on s5830i? Does it work?
[Galaxy Ace S5830i General] Qnrx:
nope didnt have much time lately
[Galaxy Ace S5830i General] WelshPaul:
ICS can be laggy on the best of phones, i wouldn't want to put it on my ace to be honest.
[Galaxy Ace S5830i General] meetdave0407:
How can i compile my 5830i???
[Galaxy Ace S5830i General] Abel669:
let us know how it goes my good man :)
[AT&T, Rogers HTC One X, Telstra One XL] 18th.abn:
Quit making threads..........

Sent from my HTC One X+ P-type_0.91.1

---------- Post added at 11:51 PM ---------- Previous post was at 11:48 PM ----------

4 threads..........amazing!!!!

Sent from my HTC One X+ P-type_0.91.1
[Nexus S Q&A, Help & Troubleshooting] bmuseed:
I am running AOKP jb 3 on my Nexus S4g and ever since I have switched to jelly bean, Crazy Home launcher fails to work and keeps giving stopped error.. I had the same problem with codenameandroid 4... anyone have any info?..
[Nexus S Q&A, Help & Troubleshooting] et4g:
It could be error in launcher wait for upcoming update or use an older version
[Android Q&A, Help & Troubleshooting] marcogiannetta:
Hi ;) Why my xperia x10 mini bootloop when I flash minicm9 or minicm10?

Sorry but my english is not so good.
[Nexus S Android Development] nightsky87:
So I decided to continue writing this today... :p

Unlike the voodoo color codes which rely on hardware (TL2796 AMOLED driver) to implement gamma correction, the color mixing process is a bit more involved on the software end. There are no chips on the Nexus S which can be configured to perform the mixing process natively. Instead, I have a few ideas on the implementation of the mixing process.

1. Rewrite the framebuffer

I've attempted doing this using native code by opening the /dev/graphics/fb0 device but the problem lies in timing. If the timing is off, the mixing either never occurs or is repeated several times for a given frame causing color distortions. This is further complicated by the use of double buffering on the device. Even more so with the switching behavior between double and triple buffering in JB! I've tried hijacking the VSYNC signal to operate on the timing (see colormix.c attached) but the result is still very glitchy. Or I may be doing it wrong... :eek:

2. Handle all routines that write to the framebuffer

Another way would be to handle all the writes to the framebuffer device. This eliminates the need for timing as processing occurs only once as the data is transferred to the framebuffer. I've seen the codes for cfbcopyarea.c, cfbimgblit.c, and cfbfillrect.c but I'm not sure where direct writes to the framebuffer (using mmap access) are handled (if at all handled). So again, I'm not too sure about this one.

3. Hijack the interface from the LCD driver

Yet another unsure idea by the way. Since the LCD driver interact with the physical hardware through 24 GPIO pins, there should be some code describing how data is transferred to these pins. At that level, it might be possible to manipulate the signal just before it is sent to avoid timing issues mentioned earlier.

Most of these ideas are speculative from a person who is not really that deep into development (I'm more of an image processing researcher :p). Any feedback and ideas from the community would be great!
[Nexus S Android Development] bedalus:
I'm down with matrices. Sign me up!
[Nexus S Android Development] noobiekins:
some good ideas here, if you manage to calibrate our screens without using voodoo, this idea can potentially be used on other amoled devices such as s3 to calibrate it, removing it's over-saturation
[Nexus S Android Development] nightsky87:
LOL. Matrices are fun! Thanks bedalus!

By the way, I took a look at the driver codes and it may be possible to find the next framebuffer using ioctl (from an external program).

case S3CFB_GET_CURR_FB_INFO:
next_fb_info.phy_start_addr = fix->smem_start;
next_fb_info.xres = var->xres;
next_fb_info.yres = var->yres;
next_fb_info.xres_virtual = var->xres_virtual;
next_fb_info.yres_virtual = var->yres_virtual;
next_fb_info.xoffset = var->xoffset;
next_fb_info.yoffset = var->yoffset;
next_fb_info.lcd_offset_x = 0;
next_fb_info.lcd_offset_y = 0;

if (copy_to_user((void *)arg,
(struct s3cfb_next_info *) &next_fb_info,
sizeof(struct s3cfb_next_info)))
return -EFAULT;
break;

Invoking this should at least resolve the double buffering issues if timed correctly with VSYNC. Again,

IF

.

Yes actually. You just need colorimeter readings of the locations of the red, green, and blue primaries to build the matrix for any other device and compensate for it.
[Nexus S Android Development] nightsky87:
So based on my last post I tried looking at the behavior of the framebuffer device. It seems that there are a few parameters which are being used by the device namely:

Dumping from a test program, I get one of two sets of values from the framebuffer device:

Start address: 4debf000
Visible resolution: 480, 800
Virtual resolution: 480, 5600
Offsets: 0, 800

Start address: 4debf000
Visible resolution: 480, 800
Virtual resolution: 480, 5600
Offsets: 0, 0

This more or less tells us that the framebuffer memory is actually divided into multiple buffers each with the visible size (480x800) of the display. They alternate (using the offsets) to provide the double buffering effect Android uses. However, what I can't understand is why there are 7 buffers allocated for the device instead of at most 3 (for triple buffering). It might be useful to take snapshots of the entire framebuffer and write them to consecutive bitmaps but I won't bother with that at the moment. :p

I've also tried using this behavior to synchronize the framebuffer writes using changes in the offset as a trigger:

for (;;)
{
do
{
// Extract variable framebuffer information
if(ioctl(fd, FBIOGET_VSCREENINFO, &next_vi) < 0)
{
perror("Cannot extract variable framebuffer information");
return -1;
}
} while (next_vi.yoffset == cur_vi.yoffset);

...
<insert color mixing here>
...
}

Unfortunately, the screen still doesn't update as desired. Lots of flickering involved. I'm not sure if the memory accesses are just too slow such that the screen refreshes before we completely rewrite the framebuffer or if its some other problem. I've attached the full code for anyone who might be able to shed some light on this. In this code, I just did a dummy rewrite (red = green, blue = green) instead of color mixing to avoid computation therefore minimizing CPU loading and to have a more pronounced effect on the screen.
[Nexus S Android Development] bedalus:
I'm clueless about video, but I'm digging around... These are the files that compile in /drivers/video/

/home/dave/android/androidkernel/drivers/video/backlight/lcd.o
/home/dave/android/androidkernel/drivers/video/backlight/backlight.o
/home/dave/android/androidkernel/drivers/video/backlight/built-in.o
/home/dave/android/androidkernel/drivers/video/fb_notify.o
/home/dave/android/androidkernel/drivers/video/display/built-in.o
/home/dave/android/androidkernel/drivers/video/fb.o
/home/dave/android/androidkernel/drivers/video/fbsysfs.o
/home/dave/android/androidkernel/drivers/video/samsung/s3cfb.o
/home/dave/android/androidkernel/drivers/video/samsung/s3cfb_nt35580.o
/home/dave/android/androidkernel/drivers/video/samsung/s3cfb_tl2796.o
/home/dave/android/androidkernel/drivers/video/samsung/s3cfb_fimd6x.o
/home/dave/android/androidkernel/drivers/video/samsung/built-in.o
/home/dave/android/androidkernel/drivers/video/cfbimgblt.o
/home/dave/android/androidkernel/drivers/video/fbmem.o
/home/dave/android/androidkernel/drivers/video/modedb.o
/home/dave/android/androidkernel/drivers/video/cfbcopyarea.o
/home/dave/android/androidkernel/drivers/video/fbcmap.o
/home/dave/android/androidkernel/drivers/video/omap2/displays/built-in.o
/home/dave/android/androidkernel/drivers/video/omap2/built-in.o
/home/dave/android/androidkernel/drivers/video/built-in.o
/home/dave/android/androidkernel/drivers/video/fbcvt.o
/home/dave/android/androidkernel/drivers/video/cfbfillrect.o
/home/dave/android/androidkernel/drivers/video/fbmon.o

I'm combing through these files now to see if there's any obvious points to hack in.
[Nexus S Android Development] nightsky87:
Great! And here I was having trouble figuring out which files were actually being used...

I'm not sure about other types of hacks but if we're talking about framebuffer rewriting (like what I've been trying to do), the following segment in s3cfb.c may be useful:

static irqreturn_t s3cfb_irq_frame(int irq, void *data)
{
struct s3cfb_global *fbdev = (struct s3cfb_global *)data;

s3cfb_clear_interrupt(fbdev);

fbdev->vsync_timestamp = ktime_get();
wmb();
wake_up_interruptible(&fbdev->vsync_wq);

return IRQ_HANDLED;
}

Assuming the system interrupt for VSYNC is enabled (which I assume to be the case otherwise the Choreographer API of JB shouldn't work), then maybe a hack there could be done to process the framebuffer just in time with the frame refresh. This is of course under the assumption that the rewrite is fast enough. I'll try sorting through those files as well to see if there's some easier hack. :p
[Nexus S Android Development] bedalus:
Couldn't you pre-process the data before it gets to the fb? It sounds like you want to read it and rewrite it. Did i understand correctly?
[Nexus S Android Development] nightsky87:
Yep, you got it right. Right now, I'm trying to read and re-write but as you said, ideally it should be pre-processed before it even arrives at the framebuffer. I'm not sure if its possible though. Applications can access the framebuffer by mmap-ing it onto shared memory which they can write directly to. I've found functions for fb_write and fb_mmap (both in fbmem.c) but I'm not sure if they're being used internally by the kernel to handle mmap and write requests. I have too little knowledge of kernel processes to know for sure. :p
[Nexus S Android Development] bedalus:
fb_write looks fully internal to me.

It looks like the OS is given access in drivers/video/fbsysfs.c
[Nexus S Android Development] nightsky87:
I'm not quite sure what you mean by internal. Does that mean that if we modify it, we can change how all data is written to the framebuffer?

As for fbsysfs.c, I can see how the OS writes the variable information pertaining to the framebuffer. However, I can't seem to find any reference to the actual data being written to the framebuffer. Did I miss something?
[Nexus S Android Development] bedalus:
I'm not 100% sure yet, but I think if you needed to, there is probably a way to hack in at that point.

However supercurio hacked into the gamma here arch/arm/mach-s5pv210/herring-panel.c

...and RGB: drivers/video/samsung/s3cfb_tl2796.c

Is your gamut correction totally independent of RGB/gamma?

EDIT: Oh, I see it now. You have to correct R based partly on G and B etc. Okay. I'll keep looking.
[Nexus S Android Development] nightsky87:
Yep... I realized that my attempt at buffer rewrites read and write from the framebuffer one byte at a time! Major I/O overheads! I totally forgot about that. :eek:

I'll try rewriting that code as well. :p
[Nexus S Android Development] bedalus:
Here's another file:

include/linux/tl2796.h

It contains the template for the RGB multipliers.

EDIT: I'm trying to see which files use this header now

EDIT: arch/arm/mach-s5pv210/herring-panel.c

...and drivers/video/samsung/s3cfb_tl2796.c

...these are the only two files, so the matrix transformation you want to perform probably needs to happen in one of these files only.
[Nexus S Android Development] nightsky87:
I think the RGB multipliers you're referring to are the same ones used by supercurio and they operate on a per-color basis. In fact, those two files don't directly modify RGB values as far as I can tell. By the time the signal reaches the TL2796 AMOLED driver, they're already mapped to the GPIO_LCD_D<> ports (see /arch/arm/mach-s5pv210/include/mach/gpio-herring.h for the physical mapping).

EDIT:

I did a grep on fb_write and bumped into this code in /include/linux/fb.h:

/* For framebuffers with strange non linear layouts or that do not
* work with normal memory mapped access
*/
ssize_t (*fb_read)(struct fb_info *info, char __user *buf,
size_t count, loff_t *ppos);
ssize_t (*fb_write)(struct fb_info *info, const char __user *buf,
size_t count, loff_t *ppos);

Since I can confirm that the framebuffers with our devices can support mmap, I suppose this means any app can directly read/write to the framebuffer without going through some intermediate function. This leaves us with framebuffer rewrites or hijacking the transfer of data from framebuffer to physical device. I like the second option better. :p
[Nexus S Android Development] bedalus:
After a lot of head scratching, I see what you mean.

I performed a search for S5PV210_GPF* and found these files:

drivers/gpio/gpio-s5pv210.c
arch/arm/mach-s5pv210/herring-panel.c
arch/arm/mach-s5pv210/setup-fb.c
arch/arm/mach-s5pv210/mach-herring.c

...all of which are compiled into the kernel.

Probably if the best place to intervene is on the GPIOs, it must be in one of these files. I'll keep looking!

EDIT: I just saw your edit in the previous post, and I agree! Option 2 seems preferable.