Database Develop

7 days with CyanogenMod 7

This is work in progress and I will update it for 7 days. Original posting can be found here
I'm sure you have heard someone telling you would spend way too much time with your smart phone. As if one could spend time with or without a tool. My phone, besides some rare occasions, is always with or near me. Yet it doesn't mean I spend time with it! I spend time with people, and I might spend my time spending time with using my smart phone to write an email. An if I spend time adjusting it to my needs or the latest desire aroused reading some blogs, so what? I do this for the sake of communication!
How come nobody understands that find difference in concept?
Day 1
25/05/2011, 11 a.m.:
Been checking my emails on the go twice, surfing on xda forum, chatting with the HTC support, writing an email to a friend, again checking my mails but also the market updates - what a pain to see there are no updates available for my installed apps. I check if it is not Sunday. No it’s not Sunday!
I discover how handy Evernotes can be. Copied an address out of the chat conversation and send it straight off to Evernotes. Must admit it was a little fight until I had marked the exact text line I wanted to have copied as it did not recognize it on its own. It would have blown me away had it read my thoughts.
I’m really thinking about one of those tables all the time. I’m kind of pissed somehow about the unfortunate fact there is no real handwriting recognition function on phones or tablets yet that really works - would be mind-blowing! I read the HTC Flyer does make advanced use of the stylus pen for note-taking somehow. I’ve seen some handwritten notes and compared them to the scribbling I am producing this very moment on real paper and there doesn’t seem to be that much of a difference.
However, I will have to type that later and I question this concept of me thoroughly doing it without giving up after a couple of minutes.
I’ve had way too many thoughts die due to the lack of an adequate and effective tool to digitalize my thoughts. I’m way much more impressed by my analogue brain-eye-arm-paper-to-key motion sequence I’ve happily produced as I realize I have really typed and added almost everything I wanted to say.
25/05/2011, 5.51 p.m.:
I wonder if I should give cyanogen latest night builds #87 a try again and get rid of my perfectly working Android Revolution ROM setup. I’m downloading, charging and backing up my phone for every eventuality...
Day 2
26/05/2011, 5.33 a.m.:
I have CyanogenMod Nightly Build #87 setup & running. Will see how it gets through the day. Fingers crossed the battery will not drain exaustingly.
26/05/2011,5.45p.m.:
In the mood for taking some screenshots and willing to do a brief review of my cyanogenmod 7 experiences...
Day 4
28/05/20011, 7.55.a.m.:
Can't hardly believe I haven't changed that much. Phone is working pretty fine, except there seems to be a problem between Fullscreen Caller ID and the call recorder that came with the modified kernel I flashed yesterday. I just won't use FSCI, instead, when I make a phone call it will try to use both the default dialer as well as the full screen dialer as the same time. The result is devastating: it will dial the number twice.
Day 6
30/05/2011, 1.53 p.m.:
Left home at 7.30 pm, battery went down to 51% by 12 a.m. and 32% by 2 p.m., whilst all I did were a few twitter & google mail updates, no phone calls, watching videos or other heavy-consuming processes.
Seems like the un-official CM7 nightly ROM I have flashed (Chezbell-cm7-20110529) is a battery killer! SetCPU is enabled, with a powersave governor profile activated when display is off, undervolted –25mA script running and I am nevertheless more than half-way out of battery within not even 7 hours – not really a full working-day yet!
Feeling unhappy and unsatisfied, after that the phone had been running so smoothly during the weekends ( some heavy 3G and EDGE-surfing in bad reception areas, gps navigation etc etc without a problem and far less battery drain). Phone was way more responsive with CM7 #87. Will switch to LORDmodUE 2.1 kernel tonight and see if it helps.
Day 7
31/05/2011, 3.13 p.m.:
I did it! I ruined it all! My sd card is totally erased! Holy frigging s’#!§t! What happened I still can’t recall exactly but I guess in any case I should learn to be more careful and most important: read and think before I act! I flashed a kernel while surfing the xda on my way home and now I don’t even find that stupid thread.
I guess it is a good point to stop my documentation now and draw my conclusions of my 7 days with cyanogenmod nightlies now.

Admins: please delete this thread. I've posted it to HTC DesireHD thread as I think it is more suitable...

What should be the most responsive/quick firmware for omap4430 512mb 10.1" G9?

I have my G9 for about 2 years now, and it's the first generation 512mb G9 1.0ghz.
All these years I updated every firmware that Archos released, so also used to the bugs and problems that sometimes occured.
Using 4.0.28 a long time now, but I think it's not repsonsive and has a lot of lag. Sometimes waiting quite a while to start an app for example.
I know that's also caused by the 1.0ghz and 512mb, but I want to try a custom rom IF that's faster.
I know all the custom firmwares are based on the official firmware, I read almost all the topic about them, but I'm not sure which firmware to choose. Hope someone can give me some clues if installing another firmware could make my G9 faster. And if so, which of the firmwares should do the trick? Somewhere I read the 4.0.7 should cause less lagging on the older generation tablets.

hars73 said:
I have my G9 for about 2 years now, and it's the first generation 512mb G9 1.0ghz.
All these years I updated every firmware that Archos released, so also used to the bugs and problems that sometimes occured.
Using 4.0.28 a long time now, but I think it's not repsonsive and has a lot of lag. Sometimes waiting quite a while to start an app for example.
I know that's also caused by the 1.0ghz and 512mb, but I want to try a custom rom IF that's faster.
I know all the custom firmwares are based on the official firmware, I read almost all the topic about them, but I'm not sure which firmware to choose. Hope someone can give me some clues if installing another firmware could make my G9 faster. And if so, which of the firmwares should do the trick? Somewhere I read the 4.0.7 should cause less lagging on the older generation tablets.
Click to expand...
Click to collapse
I'd be interested in that answer also, I'm on Surdu's custom ROM which was great at first, but now it's lagging like crazy. I can't see anything running in the background that would cause it.

hars73 said:
Using 4.0.28 a long time now, but I think it's not repsonsive and has a lot of lag. Sometimes waiting quite a while to start an app for example.
I know that's also caused by the 1.0ghz and 512mb, but I want to try a custom rom IF that's faster.
Click to expand...
Click to collapse
Although there are a few 'custom' ROMS that have some features like overclocking... overall, the VERY SMALL increase in performance of them simply is not worth it (at least not to me).
The slow down is also not really due to having only a 1GHz CPU and/or only 512MB of RAM either. It's a combination of 2 things...
#1) The totally STUPID way Archos changed their Media Center apps (Video and Music) so that the device constantly starts 'indexing' files (even when it should not do so). Heck, it even tries to 'index' pictures, music, or video files of certain game apps when you try to install them. When your device is 'lagging' take a look down in the lower right notifications to see if there is circular arrows indicating it is 'indexing'. If it is, that will slow the device down to a snails speed until it gets done.
#2) Many of the new Google updates (Google's own app updates) are now becoming far to over bloated with foolish (and, as far as I'm concerned totally unnecessary fluff).
The best solution to #1 (on my end anyway) was to simply go back to 4.0.7, but there is some extra clean up work needed to get that all straightened out. Even then you can still end up with the #2 problems (simply because Google wants everyone to buy new devices so that they and everyone else can make more money).
Sorry, I'm just way too tired and about to fall asleep here to explain all the details about how to get back to 4.0.7 and clean things up right now. All I can say for now is that I am far more happy with 4.0.7 than ANY other firmware on my end. YMMV.

55mls said:
Although there are a few 'custom' ROMS that have some features like overclocking... overall, the VERY SMALL increase in performance of them simply is not worth it (at least not to me).
The slow down is also not really due to having only a 1GHz CPU and/or only 512MB of RAM either. It's a combination of 2 things...
#1) The totally STUPID way Archos changed their Media Center apps (Video and Music) so that the device constantly starts 'indexing' files (even when it should not do so). Heck, it even tries to 'index' pictures, music, or video files of certain game apps when you try to install them. When your device is 'lagging' take a look down in the lower right notifications to see if there is circular arrows indicating it is 'indexing'. If it is, that will slow the device down to a snails speed until it gets done.
#2) Many of the new Google updates (Google's own app updates) are now becoming far to over bloated with foolish (and, as far as I'm concerned totally unnecessary fluff).
The best solution to #1 (on my end anyway) was to simply go back to 4.0.7, but there is some extra clean up work needed to get that all straightened out. Even then you can still end up with the #2 problems (simply because Google wants everyone to buy new devices so that they and everyone else can make more money).
Sorry, I'm just way too tired and about to fall asleep here to explain all the details about how to get back to 4.0.7 and clean things up right now. All I can say for now is that I am far more happy with 4.0.7 than ANY other firmware on my end. YMMV.
Click to expand...
Click to collapse
In know about the stupid indexing service. I can see it running after rebooting my tablet, but almost never when using it.
Maybe I'm going to install the official SDE from Archos (that can also be installed on 4.0.28 since a few months) and after that install a rooted 4.0.7 and then disable all the services I don't need. That might help a bit.

I suggest 4.0.28 or 4.0.7. 55mls hates firmware after 4.0.7 but .28 has been good for me. I don't store any media files so indexing doesn't affect me. Prior firmware have bugs with some games for example too.
Also on my 80 G9, I think 4.0.7 has some wifi strangeness. Disconnects occasionally.
Alternatively you can roll back to 3.2.80. This one works quite well overall functionally. However it's certainly not the fastest. The GUI seems slower to me than with the 4.x OS. Honeycomb also has some caveats like occasional lack of app support and the fact that it's sort of a Android 4 prototype in general. On the other other hand, Honeycomb is an interesting bit of history and I like its UI theme.

having the same tablet here (also with ""only"" 512mb ram).
i'm running 4.0.7. now, which works a lot better than 4.0.28 for me, but still has some lags from time to time..

I guess I should have also mentioned a 3rd reason in my previous post that some people may not be aware of...
When installing apps, some do require extra 'temporary file' and/or 'cache file' storage space. By default, Android normally will pop up a "memory low" notification when the amount of memory drops below 500MB. Of course, that means the systems has already gotten so low on memory that it can no longer operate correctly.
On my end (and my devices) I've found that things start to slow down already even when the 'free space' gets down to 1GB. In general, if you can keep the 'free space' up to at least 1GB (preferably 1.5 or more) then there is very little of any slow down.
Of course, now days, almost all the newer devices come with at least 16GB of flash memory and 2GB of RAM (not to mention quad core processors) simply to be able to handle all of the extra fluff Google keeps adding into things with their own upgrades.
Since Google is making the exact same mistakes Microsoft did years ago (taking a good OS and cluttering it up with so much extra fluff that nobody wanted/needed)... well, I've pretty much lost all interest in Android now. I bought my Archos G9 tablets for only one reason and that is to do what Archos claimed they did at the time. I did not expect, nor did I ever want them to end up having to go thru multiple upgrades (from either Archos or Google) to do anything more or less than that. Unfortunately, every upgrade now seems to actually lower (or even restrict) being able to use my Archos devices BELOW what I originally could use them for.

55mls said:
On my end (and my devices) I've found that things start to slow down already even when the 'free space' gets down to 1GB. In general, if you can keep the 'free space' up to at least 1GB (preferably 1.5 or more) then there is very little of any slow down.
Click to expand...
Click to collapse
This seems to be something all devices have a problem with. It's probably a flash RAM issue. When the flash gets near full, it needs to do more erases+writes to store new data and this just kills write performance.

swaaye said:
This seems to be something all devices have a problem with. It's probably a flash RAM issue. When the flash gets near full, it needs to do more erases+writes to store new data and this just kills write performance.
Click to expand...
Click to collapse
My son installed a lot of games on my Archos in the past and there was not a lot of free memory left. This week he bought a Asus MemoPad HD7, so I uninstalled all the games on my Archos.
And it seems my Archos is a lot more responsive now and has less lags. :good:
Still on the official 4.0.28, but this is good enough for now.

hars73 said:
My son installed a lot of games on my Archos in the past and there was not a lot of free memory left. This week he bought a Asus MemoPad HD7, so I uninstalled all the games on my Archos.
And it seems my Archos is a lot more responsive now and has less lags. :good:
Still on the official 4.0.28, but this is good enough for now.
Click to expand...
Click to collapse
Another thing you can do, especially if you have a 512MB device, is to keep watch for apps that run extra background processes. For example, do a reboot and load the system monitor app and see what is loading automatically on boot up. The 512MB devices really don't have enough RAM to go around beyond the basics.

[Q] Screen becoming unresponsive.

Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.

Latonya1 said:
i had same problem and what i did is i opened battery from the device and inserted its again and did a factory reset on my device
Click to expand...
Click to collapse
Removing the battery on the kindle isn't an easy feat. Are we talking about the same device, or did you attempt this on a phone? Because if this worked with the kindle, I am more than happy to put the time into trying but I want to make sure.
Thanks for the reply.

dlenoxx said:
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Click to expand...
Click to collapse
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed

Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

itouchables said:
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
I should have read over what kinology was before flashing it.. I'm sure it's a great rom, but I'm wanting something more android-e. Went great though, as far as the install- and thanks for the tip. Worse case I'll have that file to fall back on.

stunts513 said:
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Click to expand...
Click to collapse
As I've been doing a bit more testing trying to figure out what is going on, it does seem to happen more often when under 100~75mg of memory available. Idling now at 550 memory available now, thanks to a few tweaks here and there which has almost erased the problem when doing things like browsing the internet, youtube, netflix, etc. It's just happening now during games. Not as much- but still, in the middle of a game of Kingdom Rush it's a little frustrating to all of sudden have no control. And currently I've still got almost 7 gigs of space available as far as harddrive goes so that doesn't seem to effect it by much (at least for me).
Setting the I/O to noop, overclocking to 1500 (leaving the minimum to 350), and setting the zram compression to 28% were the tweaks. Also having Task Killer by rechild set to kill tasks when screen off has been a great fix when I do lose the touch pad controls as it'll free up some memory when I turn it off, leave it off for a minute, then turn it back on without really interrupting progress in several apps.
Still searching for a true, 100% fix so tips are still welcome and I'll keep everyone posted if I run across anything myself.

Fire Tablet Solution to Combat the Lag Scheduled Reboot

I purchased some some 7th gen fire tabs (x2 7" and x2 8") I use these as wall mounted controllers for home automation. I foolishly made my purchase off the back of a quick google for Fire tab root and making the assumption its possible after scanning the results. At this point I wasn't even sure id need to root the device.
Around the time of my purchase it looks like Amazon released an update which prevents rooting and I was 'lucky' enough to have devices with the newer firmware version. I use fullykioskbrowser on these and so far with the help of xda and other parts of the web I have disabled the lock screen giving me the ability to automate the screen turning on and off. Awesome!
My one final problem is these tablet run to almost a complete standstill! This makes them unusable until I manually take apart their beautiful wall mount and turn them off and back on again. I would like to schedule a reboot of the device enabling it to be snappy all the time.
Does anybody know how I can achieve this? Lots of the apps available including fullykioskbrowser require root. Which I obviously cannot do! (Yet? Is anybody close, working on or admitted defeat on this yet?) The apps that don't need root seem to imitate screen taps to navigate to a reboot using software but I don't think amazon have this.
Is there anything I can do to schedule the reboot of my fire tablets? Or a next best thing?

New again or better?

Background (short version): I finally replaced the charging port and my 2012 Nexus 7 is back up and running... Sort of... Navigation is impossible and I've tried every non-rooted method I can find, to clear memory and storage. It's slightly improved now that it's stripped down, but still hardly functional. I'm aware there have historically been, countless ways to root then flash custom roms to help with this. Most roms are probably a bit more than what I need and the developer support for each is hit or miss, for such a dated device.
My question: What do you recommend I do (linked tutorial preferred) for a straight forward process to get this tablet running, so that I can stream my favorite video services and play a couple of simple games? I'll be using the tablet for light browsing too, but that's about it. Right now, I can't even navigate through the Settings menu without dedicating 30+ minutes. I'm prepared to factory reset, root and flash, but I don't want to go down the wrong rabbit home.

Time to scrap it. You'll keep wasting time trying to make it usable, and it will continue being a bad experience.

TheMystic said:
Time to scrap it. You'll keep wasting time trying to make it usable, and it will continue being a bad experience.
Click to expand...
Click to collapse
Oof... I mean sure, but I'd like to use it instead and there's no reason it shouldn't be capable of running a couple video streaming apps

kevinbakon said:
there's no reason it shouldn't be capable of running a couple video streaming apps
Click to expand...
Click to collapse
There is. It is called Planned Obsolescence. Not your fault or device's fault.
There will be no support for devices or Android versions that are older than a certain age/ version.

TheMystic said:
There is. It is called Planned Obsolescence. Not your fault or device's fault.
There will be no support for devices or Android versions that are older than a certain age/ version.
Click to expand...
Click to collapse