Bloodscythe wrote:@Nandaka
I tried clearing image cache as well, and sure enough, it could not load any novels.
I then used a file explorer to check android/data/com.erakk.lnreader and found there were NO files. It does indeed seem that clearing image cache deletes all the files.
Note: I am using test build 31. It seems each android system has a unique way of storing data in the internal sd card as my images are located in dfferent folders then yours.
That's why I place /files/ there last time, I forgot already _-_....
Erakk wrote:@Database problem: Fixed. I changed the delete method so it will delete inside projects instead of files.
better to use whitelisting (skip if equal to /databases/ or pages), because we don't know the image structure (usually if hosted in baka-tsuki directly, it will be in /project).
Erakk wrote:@Database problem: Fixed. I changed the delete method so it will delete inside projects instead of files.
better to use whitelisting (skip if equal to /databases/ or pages), because we don't know the image structure (usually if hosted in baka-tsuki directly, it will be in /project).
I want to assure you - MediaWiki doesn't support html tag <img>, there is no way append external image into page as image, not as link. Every image you find in pages can only been hosted on Baka-Tsuki. Also, you can use imageinfo prop with api for retrieving information and links for original images.
Alligator06 wrote:Hey,
I can't seem to find the gekkou short story on it, Is it just me or something with the app?
Using build 31 on an ICS android.
It's you. The Gekkou short story is only available as a pdf on Baka tsuki. The app can only find novels where the novel is hosted on an actual webpage.
The app can't grab a pdf off the net and then view it. You'll just have to A. Beg Baka Tsuki to host the actual short story OR B. Use a pdf readet for Android.
Alligator06 wrote:But it's posted right here Gekkou Short
Oh, looks like I only saw the pdf thing. Well, the other explanation is that the app doesn't grab the short story because the short story isn't in the usual format.
Okay, I suck at explanations but I'll try my best. Normally, novels are ordered in a specific way. Name, then the chapters underneath and then it repeats with more Novels. but the Gekkou Short Story doesn't follow this format, it's just listed under Short Stories. If you look around at other novels e.g. Campione,High School DxD you can see their short stories are listed under the Main novels and DO NOT have their own "short story" category so the app is still able to list them but it can't get the Gekkou short story because it's not under the main list but in another list altogether.
I hope you understood that.
Alligator06 wrote:But it's posted right here Gekkou Short
Oh, looks like I only saw the pdf thing. Well, the other explanation is that the app doesn't grab the short story because the short story isn't in the usual format.
Okay, I suck at explanations but I'll try my best. Normally, novels are ordered in a specific way. Name, then the chapters underneath and then it repeats with more Novels. but the Gekkou Short Story doesn't follow this format, it's just listed under Short Stories. If you look around at other novels e.g. Campione,High School DxD you can see their short stories are listed under the Main novels and DO NOT have their own "short story" category so the app is still able to list them but it can't get the Gekkou short story because it's not under the main list but in another list altogether.
I hope you understood that.
Hiya, the parser didn't include Short Stories (first time seen it), usually that kind of stuff will be put under Side Stories (e.g.: Infinite Stratos) or have it's heading prefixed with the Novel name, in this case: 'Gekkou Short Stories'.
Either I add the keyword (Short_Stor*) to the parser, or have its editor change the Heading.
Sorry guys, due to a strong rain, I have no Internet for now, so i cant compile any new builds from github.
The ISP tech guy is coming here tomorrow to fix things up... (i am on my phone 's 3g by the way.)
@Nandaka: if you update anything, just leave on github and I'll merge when I get things working again.
In theory, practice and theory are the same.
but, practically, they arent.
Erakk wrote:Sorry guys, due to a strong rain, I have no Internet for now, so i cant compile any new builds from github.
The ISP tech guy is coming here tomorrow to fix things up... (i am on my phone 's 3g by the way.)
@Nandaka: if you update anything, just leave on github and I'll merge when I get things working again.
So not only my hometown got flooded
EDIT:
Change Log:
- Update parser for handling Short_Stories (Gekkou)
- Some method refactor/move.
- Add option to handle external link with internal WebView, need to be tested.
Using Bakareader EX instead of Bakareader I have found that it doesnt seem to remember where I was reading.
Whenever I press back and enter the chapter again it just starts at the beginning of the chapter instead of where i was.
Im using a Motorola Droid 2 with firmware version 2.2.
Its really the only complain i have so far, keep up the good work.
Hmmm... Okay, I'm going to report on something I found out.
It seems that if you enter a chapter, leave and then enter again, more ram is getting used by the app.
So, when I first enter the app, it only uses about 15mb of Ram but repeatedly going in and out of chapters causes this to spike. It also seems to happen when you use next/previous as well as you're exiting and entering another chapter.
I tested this by exiting and entering a novel about 5 times or so and, sure enough, ram usage increased from 15mb to 25mb. There was even a time where it's cached ram was 77mb.
Now then, on high end devices running Honeycomb or higher, this is barely noticible as those systems have about 1GB or so of RAM. But on low end devices, Gingerbread or lower, this is a major drain on our devices and causes lag and other glitches to occur.
This maybe the cause for the problem above, the app not remembering a place in a chapter. This is viable I think as the only people who reported the glitch ran Gingerbread or below.
This was tested on LG E400 2.3.6 rooted device. Could other people test this to see if it's true for other firmware?
I can confirm this behaviour.
This also happens if you click on a picture to see it in its original size. I opened a picture about 7 times and the ram usage went from 44MB to 78MB.
It seems the app is caching the entire chapter in ram, but never frees it. I don't know if this is a normal behaviour of the Android-system or if it is a memory leak in the app.
Update2:
- Skip db path when deleting image cache
- Add Yes/No Dialog on delete db and image cache
- Update Parser for WikiAPI
- Add Exception Handling for Scrolling Event in Novel Content
- Change back the db path to /files/databases/ to conform with newer android.
Backup your db before updating
Tidon wrote:This also happens if you click on a picture to see it in its original size. I opened a picture about 7 times and the ram usage went from 44MB to 78MB.
It seems the app is caching the entire chapter in ram, but never frees it. I don't know if this is a normal behaviour of the Android-system or if it is a memory leak in the app.
I think this is the normal behaviour for Android, they only will release it when the memory is low. Maybe you can try to run another application which uses a lot of memory (games?) and see what it the behaviour?
If this is Android's RAM management system then it must be really poor.
Anyway, I think this behaviour is causing pretty much any of the instability inside the app.
Most of the activities in the app are not being killed but kept.
Would the app run much smoother if the activities were being shut down?
I mean, it seems pretty much pointless to keep every activity. If you finish reading one chapter, you're not going to go and read it again in the short time the app would be active, right?
Nandaka wrote:I think this is the normal behaviour for Android, they only will release it when the memory is low. Maybe you can try to run another application which uses a lot of memory (games?) and see what it the behaviour?
You're right, the system releases the memory if it is needed by another app.
What I don't understand is why the system won't reuse the allocated memory even if the same chapter is opened multiple times.
