yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] wheilitjohnny:
I know some people have already discussed this in the noRefresh App thread.

But I got a new idea

I don't wanna create a module and embed that to applications

Instead, I created a new Input Device in the kernel

After that, I set the device ( dev/input/event3 ) permission to allow read / write for others.

Then, write an app using JNI to catch the Input Device and set the mode of refreshing.

The prototype proved that this idea works, as i worked out it already, but not very perfect, still in experiment

I am just in some problems of threading, as I am not a professional programmer

This is wt i have now:

http://www.youtube.com/watch?v=GkFyvRR6In8

NEW!! : http://www.youtube.com/watch?v=cucG03rg3tg

I know that my method is a bit dirty,

but at least it works XD

I hope that someone would like to help

Upload those code soon
[Nook Touch General] wheilitjohnny:
By the way, why can't i change content of init.rc ?

It removes my changes after reboot..... How to solve?
[Nook Touch General] notriddle:
You need to modify uRamdisk to change init.rc.
[Nook Touch General] wheilitjohnny:
Would you like to tell me how to unpack the uRamdisk? I use both Windows and Ubuntu, any methods on these two platform is ok. Thanks!
[Nook Touch General] mali100:
Try the script from this post http://xdaforums.com/showpost.php?p=24135886&postcount=72
[Nook Touch General] Googie2149:
This is simply amazing. Since you already have it working, polishing it shouldn't take too long (I think, I'm still a beginner programmer).
[Nook Touch General] Renate:
I don't think /dev/input is a good place to park that.

There are any number of things that could show up there and affect order.

Why not put it in its own directory?

Maybe I'm missing something, but if we use your method you still expect applications to have to be modified to read/write from event3 to control display mode?

As it is now, you only need a single function call to switch display modes. Yes, there is a little bit of housework to do before that, but what could be simpler than a single function?
[Nook Touch General] wheilitjohnny:
I think no place else is more suitable than /dev/input.

As /dev/input is the linux kernel's input system.

In the driver, I would only use the input report system but not use the I/O system.

Maybe even setup a input/event searching function to solve the problem later.

The case now is that, the touch screen originally just provide event2,

but if we need to extract move and fingerup information on upper level, it may waste some time.

In order to make the whole algorithm easier and faster, I added 1 more event in the zForce driver,

to only output FingerMove and FingerUp state.

As the reporting system is starting from the kernel, this hack would need to change uImage + uRamdisk + Add an App. The project is quite huge.

My final target is to make the application remembering your choice on what mode u need for the focusing application.

AlwaysOn / OnlyWhenDragging / AlwaysOff, so on.

Of coz the click-to-call function still work.

Isn't it a better workflow and more intuitive, isn't it the thing that we would expect?
[Nook Touch General] Renate:
I already have an dev/input/event3 on my system and sometimes event4, 5, 6.

That's why I don't think that whatever it is you are doing belongs there.

Is the point to allow coders for user applications to interface with your driver?

Is this supposed to work without modifying user applications?

What information would be going in/out of event3?

Clearly I am missing something here.
[Nook Touch General] wheilitjohnny:
Actually not necessary to be event3, the system will auto-ly create a new eventx, just in normal case, without any extra USB devices, a nook should only have up to event2. So, I use event3 as an example here.

We can later make the program auto-ly search back which is the needed eventx.

Yes, u r right, we no need to modify any other applications and this is exactly the point y i am creating this!
[Nook Touch General] wheilitjohnny:
Anyone know how to call a FullScreen Refresh in a service?
[Nook Touch General] mrWax:
always on?

Look really great. Since blinking after scrolling is incomfortable is it possible to have also "always on " mode using your new ideas?
[Nook Touch General] wheilitjohnny:
My final target is to make the application remembering your choice on what mode u need for the focusing application.

AlwaysOn / OnlyWhenDragging / AlwaysOff, so on.

Of coz the click-to-call function still work.

Also an Over-Ride mode, for more flexible using.

But the most basic part need to be handled well now, as it is not very perfect now.

I still don't figure out how to call the e-ink driver to refresh the screen =-=
[Nook Touch General] mali100:
Have you tried

echo 1 > /sys/class/graphics/fb0/epd_refresh

?
[Nook Touch General] Renate:
Are you saying that your idea does not require modifying user applications?

If it doesn't, then there is no need to have a public interface.

It will be only your code talking to your code.

What is the point of this /dev/input/event3? You say that it will be writable. What's going in and out?

Some apps will be using gestures, some dragging. How are you going to keep track of that all?

I have one application that works perfectly fine now, one activity uses swipe gestures to page up/down while another activity uses drag with a user choice of A2 and display while dragging or else only panning at ACTION_UP.

All this requires less than 10 lines of code.

With multitouch, many applications don't even need A2. Even normal panning in Opera Mobile works much better now that Opera doesn't try to display while panning.
[Nook Touch General] wheilitjohnny:
Maybe my english is too bad, cannot express the idea well.

I know, we can make such an application with noRefreshDrag working on its own well.

But how about other applications, it is impossible for us to change all applications.

So, my idea is making it system based.

My prototype is very good now, after several adjustment.

Not limited to only 1 application, but the whole system.

The approach is like this:

1. zForce driver provide extra information to InputEvent

2. A JNI catch the InputEvent

3. A service get the data and set the update mode

We only need to write 1 application to handle the setting of this chain.

This is what i mean, hope that u get what i mean now.
[Nook Touch General] wheilitjohnny:
Let me try it now!

wow, it works great
[Nook Touch General] Renate:
I guess that this is the part that I don't understand.

What is this extra information?
[Nook Touch General] wheilitjohnny:
It created an extra Event, l called it Event3 before.

Driver reports only move and finger_up to Event3.

Just providing a channel to pass an information from driver to user-space.

You may ask why not directly using the existing Event, need to create another one.

That is because, the original one only have touch and position information, parsing them back to move information need a bit of work. As the hardware provided the move information, then don't waste it.
[Nook Touch General] Renate:
public boolean dispatchTouchEvent(MotionEvent event)
{
switch(event.getAction())
{
case MotionEvent.ACTION_DOWN:
break;
case MotionEvent.ACTION_MOVE:
break;
case MotionEvent.ACTION_UP:
break;
}
return(true);
}
}

Isn't that everything that you could ask for?
[Nook Touch General] wheilitjohnny:
Sorry...... I don't get your meaning =-=

I am not a native english user..... so..

maybe I upload the code for u later XDDD

btw, here is where i am: http://www.youtube.com/watch?v=cucG03rg3tg

It is not only for 1 application, it is system-wide

Nearly no ghosting problem ( just when several drags that the system cannot catch up )

Hope that you would support my idea after watching XD
[Nook Touch General] klausef:
That's a neat structure idea. What if they went a step further and simply implemented DragNoRefresh within the original NoRefresh enabler? One app with all the functionality.

I've read the source and it seems that the NoRefresh enabler is really not much more than a wrapper to the

N2EpdController.enterA2Mode();

function; it creates an invisible fullscreen view, reads taps from it and checks them against its 'gesture algorithm' and then either switches to or away from A2 mode.

If it instead read drag or multitouch gestures we'd be set. Of course, it would still be nice for it to *automatically* detect movement on the screen; this method would not work for, say, kinetic scrolling, where the screen keeps moving even after the drag has finished. To alleviate this issue, we could poll the framebuffer around where the drag was and near the borders of the screen for a short time after the gesture finished. As long as change is read, A2 is kept activated.

Talking out of my rear end here, I'm sure y'all can think of cases where the above method would fail. I'd still be willing to dig in and hash up the described code, though
[Nook Touch General] wheilitjohnny:
ha XD

later we share the code

step by step approaching our target XD

I am actually building the app based on the noRefresh Enabler
[Nook Touch General] mrWax:
no-return to refresh mode

Hi! Could you, please, do one version with no-returning to refresh mode? i.e. after scrolling display stays in no-refresh.

thx
[Nook Touch General] dobbing:
Usability looks great; looking forward to you uploading the code for others to try it...
[Nook Touch General] mrWax:
how it look

Hi! just wanted to ask whats up with your proj, ?
[Nook Touch General] wheilitjohnny:
Although added Always On mode,

but frequently toggle between A2 and normal mode seems having some issues,

figuring out how to solve them now...
[Nook Touch General] mrWax:
It is sad that there is still no posibility of having always on - No-refresh.

It is so annoying. For example Ebookdroid after update stops no-refresh after loading every new page. That makes djvu unreadable for me again.

any ideas for some other app? or chance to make always on - no refresh? or if you have it - where to download?
[Nook Touch General] chriscsh:
why you feel shame on it?

it only a testing app

it still under development,

and i think the developers are working on it :p
[Nook Touch General] mrWax:
wrong word

sry mistake in translation :)
[Nook Touch General] djmadness:
This sounds great. The idea is fantastic. I hope you get it.
[Nook Touch General] The Archangel:
Thread moved to general. When the op has the links updated,I will move back.

@op when you have the links, pm me.
[Nook Touch General] imachine:
Waiting for an apk or an update.zip for CWM; NoRefreshToggle.apk doesn't work for me.
[Nook Touch General] xd4d3v:
Hi all.

the apk doesnt work for me either on my NST, are we missing something?
[Nook Touch General] Rafsen:
Here u got a working app:

http://xdaforums.com/showpost.php?p=22800284&postcount=10

I've tested it yesterday on my Nook (MinimalTouch root).
[Nook Touch General] Zorkman:
I guess this development has stopped?
[Samsung Galaxy Nexus] LSUtigers03:
Any chance these are legit OEM batteries? Two OEM batteries for $16 seems too good to be true.

OEM GSM Galaxy Nexus battery
[Samsung Galaxy Nexus] ttabbal:
It is too good to be true. EBay is crawling with fake "OEM" batteries with a sticker that looks exactly the same as the real one. Makes it almost impossible to tell from a pic. If you want a "real" OEM battery, you need to get it from a known good seller. Shimshop on EBay sounds reliable from reports here. There's also Expansys, they likely have the real deal. The pricing I've seen is about $30/per for the real ones. Much cheaper and it's probably a fake.
[Samsung Galaxy Nexus] asianxtreme:
i was thinking these: http://www.ebay.com/itm/Original-OE...ccessories&hash=item2a18a7b669#ht_4442wt_1247

looks legit but who knows.

Also newegg had some but I don't see them now.
[Samsung Galaxy Nexus] jonnythan:
I've been using the bargain-basement eBay China batteries in everything from DSLRs to cell phones for like 7 years. They never work quite as well as OEM but at 10% of the price for 90% of the performance I don't care.
[Samsung Galaxy Nexus] andymp3:
Its funny you posted this. I ordered 3 of them with charger and got them a few days ago. They are not OEM however they actually work pretty well. I sent seller email before i bought them and was told in his own words they are OEM samsung batteries.. I did this so when they were delivered i would have proof that seller was stating the fact they were OEM... I knew however for 14$ there was no way they would be real. This way when I contacted seller to complain i would have a leg to stand on. I sent him and email stating that they were fake and that I wanted to know what they were going to do about it and 1 hour later a paypal refund for the full amount was issued. These guys know they are selling fake stuff however unless you have a trained eye and know what you are looking for it would pass as an OEM product. For the price.... They are good batteries...lol.. To be honest i would have gladly paid the money if the seller would have come clean on the matter.. I will take pictures and post them when i get a chance..hope this helps....cheers

I took pic of all 3 with charger and a pic with a real OEM next to the eBay battery...can you tell the difference? lol... Oh and pics were taken with my Nexus so please excuse the quality...
[Samsung Galaxy Nexus] GuestK0080:
The "original" ones on eBay IMO are fakes. Also the typeface used on the label definitely doesn't match the OEM battery that comes with the phone. I would avoid them and buy from a trusted vendor like Expansys or Handtec.
[Samsung Galaxy Nexus] EP2008:
If you email the sellers of these real, but fake batteries, they will quickly say they made a mistake posting and the batteries are not genuine... I hate when sellers play games like that.

We should all mass-purchase these "original batteries" and demand refunds at the sellers expense, just to teach them a lesson. It's not right to knowingly scam the public.
[Samsung Galaxy Nexus] ljwnow:
Agreed. Usually you won't go wrong if the seller has included "genuine" in the listing. Be careful when they don't include that word. That's common ebay sense.
[Samsung Galaxy Nexus] Fountainhead931:
I go to Shenzhen and HK regularly, and I've been in the shanzhai/jiamao markets there and they have booths with blank batteries and the stickers that look almost exactly like all the major brands, they will make you up 100 or 50 or any qty you like on the spot. When they sell a counterfeit battery they always include a charger.....guess why? They caution you not to charge that counterfeit battery in your phone, it might explode or catch fire!

So they always sell the charger with the battery.

NO WAY would I put one of those P.O.S. in my phone.

They are tempting though.

PS: Not claiming accuracy in my pinyin terms but you get the idea :)
[Samsung Galaxy Nexus] andymp3:
Yeah ..i was pretty sure when I bought them that they were fakes so when I received them I was not so surprised.. I did however get 3 batteries and a charger for free..lol...They are actually pretty good...They don't heat up and seem to last as long as the original. They are about 90% as good as the OEM as far as discharge times. Overall I am quite happy with them...And for the price I can't go wrong..
[Samsung Galaxy Nexus] PROlific666:
Damn I wish I had seen this the only way I knew was that it was fake was the NFC didn't work.
[Samsung Galaxy Nexus] GateCityRadio:
I've been using ebay batteries in my G2 for a long time. For the price I'd say they are worth it. I had a 2200mah evo 4g battery from ebay in my G2 for over a year and I just recently had to replace it because it wasn't holding a charge quite as long as it used to. When I first got it, it would easily last a day, which was something the stock htc battery couldn't do. Now I have an extended 3500mah battery I paid only 6 dollars for and I can get 3 days off of a charge. I have a 2300mah battery on order for the nexus, I'll make a review thread and let you guys know how it does.
[EVO 4G General] 俯视、灵魂:
Tomorrow MIUI China station website, issue voting stickers, discussing whether to join Evo4G plate, please timely attention
[EVO 4G General] sitlet:
Ummmmm, what??
[EVO 4G General] MicrosoftBug:
Please find a Chinese friend that knows English.

Sent from my PC36100 using Xparent Blue Tapatalk
[EVO 4G General] souleman:
The official Chinese site (miui.com), is having a vote on their forums to decide if they should do an official port to the Evo4G. I'm just not sure if they are talking gingerbread or ICS, because I can't find the poll, unless it isn't going up until tomorrow.
[EVO 4G General] 88exp88:
Really an actual port by the actual devs of miui ics
[EVO 4G General] ECrispy:
I really hope we get official support for MIUI on the Evo - that would be so awesome. Don't even care for 4G, at least we'd get stable ports every Fri.
[HTC Vivid, Raider, Velocity] shael:
hey guys is there any root/roms for this device yet? ive tried searching and havent come up with anything... it all seems to be for the AT&T vivid...
[HTC Vivid, Raider, Velocity] Aus_Azn:
The Raider x710a is the HTC Vivid, at least that's what it says under my battery cover.

Does the Rogers device have the same code?

Root's always been available for Canadian Raiders as your bootloader was unlocked much earlier than ours. custom ROMs are interchangeable by region.
[HTC Vivid, Raider, Velocity] shael:
well its actually a bell one, same device but i tried loading the ics official RUU from AT&T and it was a no go?
[HTC Vivid, Raider, Velocity] christx:
set sail for fail, another day, another newb
[HTC Vivid, Raider, Velocity] shael:
just newb with this device, if you check my threads i use to cook roms for the magic...so stfu
[HTC Vivid, Raider, Velocity] Aus_Azn:
Learn the art of posting on XDA. This should be in general.

You asked for root and ROMs. For you, this has been available for what feels like centuries. Just looking at the dev board would have gotten your answer.

Now you're talking about ICS RUU, which is neither of those. Searching anywhere would have immediately told you that you need an OTA with the new HBOOT and the Canadian carriers have not released that yet!

Ai ya yai, it's no surprise that PG left.
[HTC Vivid, Raider, Velocity] shael:
ok so its rooted, and if im corrected there is no ics available to flash?
[HTC Vivid, Raider, Velocity] kozmikkick:
Yes.
[HTC Vivid, Raider, Velocity] willgill:
shael sorry for the harsh greetings from others. I am not sure when decurum and sensibility were flushed from our souls bit I'd like to wish you the best from Dallas, TX USA.

Good luck with the Raider.
[HTC Vivid, Raider, Velocity] Aus_Azn:
A lot of it flew out the window when PG left. There were so many people who kept asking the same questions over and over, who didn't search nor follow instructions, then proceeding to come here and whine about why their phone/ROM didn't work. PG got fed up. It's part of why the development here is so weak.

This posed question really is no different. I can provide decent responses to good questions and demonstrated competence, but it's immensely tedious to try to respond to the same questions over and over when the answer is readily plastered all over the place.

It was common understanding in the old Captivate forum that one is to search before posting, then post their question. For some reason, the problem wasn't nearly as pronounced there, and all places in which it appeared was in the General section. I feel like the convoluted (by comparison) HTC setup is causing a lot of angst among those new to this, but the information to do things properly is still present on the forums as much as it was before. All people must do is read thoroughly and follow directions. Nobody is responsible for your device except you, so it's your fault if you brick your $500+ phone.
[HTC Vivid, Raider, Velocity] christx:
You nailed it, while being politically correct at the same time :D
[HTC Vivid, Raider, Velocity] willgill:
I can understand the intolerance for whiners, but he wasn't whining. I know the history of PG and the reasons he left.

The quick quips telling someone to search really aren't helpful. Maybe they did and it was confusing or they didn't find the answer.

For that matter, if searching is always the response at XDA, we don't need XDA since all of the same answers are available on other websites and can be Googled.

The Internet is free and we can act however we wish. My wish is for a more helpful, less critical culture.
[HTC Vivid, Raider, Velocity] reterp:
Same questions everywhere i look

I have been using xda for years, i never post, i do this out of respect for the devs and people who have legit questions in the tread but since i just got my HTC raider last week (i have a G-Nexus as my main device) i started to Rom and ROot this device and i have seen so much anger on these threads, brothers i have the same hate for mundane and stupid questions that can be answered by control -F-, or the search button at the top, i have found a answer to every problem i have had for almost 3 years worth of androids (G1,DEXT,DesireZ,GalaxySVibrant,MOTOAtrix,Xt860,samsung note,galaxy nexus) Just for the love of god please use the search functions that we have at our disposal so that we dont loose DEV's like PG and we continue to make these phones better than they are

lets stand up for justice in the forums

Lets stand up for clean forums

LETS STAND UP FOR SOME BLOODY ICE CREAM SANDVICH
[HTC Vivid, Raider, Velocity] Aus_Azn:
I'm not talking about this isolated instance. I'm saying in general. OP didn't whine, but his second question posted a very simple and very common question whose answer is found all over the shop.

Every thread I've read ever since joining XDA has a clear instruction set. Never found any problems, and any unclear bits was usually cleaned up within at most a day. Especially for things that are guided/intuitive like RUU updating or CWM flashing. Anything deviating from that has always had clear and express instructions.

I agree with you on the searching front. It's just that by consequence, XDA is a pinnacle for Android development information and Google's search is not localized to the forum (though it can be forced), nor are all its threads indexed with the latest information on the latest issues, unlike the forum search and its ability to parse posts as they are made. Likewise, most of the information here cannot be found elsewhere unless heavily publicised.

My wish is for XDA's culture to have more autonomy and less incompetence. XDA is more of an instruction manual when it comes to knowing the ins, outs and modifications that you can do to your device.

Anyway, let's end this before it erupts. I am now abandoning this thread.
[Huawei Ideos X5 U8800] Stopa:
Hi.. I have problem with sending and receive MMS on my U8800.

I'm using newest CM 7.2 (120309 - .35 kernel) and I try send/received MMS under GPRS/EDGE/HSPA network using standard SMS app and GO!SMS as well.... without any success :(

When I was using B518 I don't have any problems with that, I tried to search some information about that issue in general fourm.. but I found nothing :|

Some ideas ??
[Huawei Ideos X5 U8800] dingdingdang:
Donload "go mms",it will solve the problem.
[Huawei Ideos X5 U8800] Stopa:
GO MMS... (o.0) There is no such application, Go sms send mms as well, just like standard android sms app. However i try to search Go mms in google, but without any succes :)
[Huawei Ideos X5 U8800] Stopa:
Anyone? ??
[Huawei Ideos X5 U8800] Stopa:
still valid..... :(
[Huawei Ideos X5 U8800] cokratex:
He means go sms. It should work.

Check your APN. I had a similar problem earlier, my mms apn was gone. Added it manually and after that it was ok.
[AT&T Samsung Galaxy S II SGH-I777] syonin:
I found that if you create the first email account using the Settings>Accounts&Sync>Add new account method. Then the Email.apk will launch without a problem.

I believe the issue is related to the runOnce "Create new account" wizard for the email app.

Also, if you have any other apps (gmail, maps, play store) that are FC just go to Settings>Applications> and find the app, force stop, clear data and cache, and retry.