Database Develop

[Q] Upgrade Nexus One to the Prime or just keep it?

I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks

lchiu7 said:
I bought the N1 on the day it came out and it's still going fine. Well I must provide soem caveats here so say it's not the original unit. I have gone through 2 RMA's with HTC and 2 paid for repairs for the power button. The last time the power button failed, the repair only lasted abouit 6 weeks and when I complained they sent me a refurb rather than fix it.
For me the only issues for the N1 are
- flaky touch sometimes (go to suspend and back usually fixes it)
- constantly running out of system memory and all apps I can move are moved to the SD card.
So it's either get a new phone or root the N1. Given that the phone works for what I want rooting and a new firmware might be the answer.
So given that I have never rooted a phone or installed new firmware, can people suggest the most appropriate firmware I should be looking at and the easiest way to get there. The phone is currently on 2.3.6 (OTA).
There is so much conflicting information out there it's hard to know what the best route is.
Thanks
Click to expand...
Click to collapse
I have a rooted N1 that I bought in February of 2010, a month after they became available. It was rooted when I bought it on eBay and running one of the CM ROMs. I don't know how to root a phone, sorry.
I DO know how to load ROMs and have variously updated and modded the phone myself. I have been fortunate in that my power button has never failed, but while I was running a series of OTA ROMs (ROMs based on the pure Android released from Google) I noticed that the latest ones disabled the trackball wake feature, meaning that the power button was the only way to wake the phone. I had gotten used to trackball wake with the first CyanogenMod ROM, and so once I learned that the power button was a weak spot, I decided that a CM ROM or a modded AOSP ROM was the only option.
As there were some issues with CM ROMs that took months to work out (see WONK), I went with an AOSP ROM that I found here http://forum.xda-developers.com/showthread.php?t=1121595 . It's now a dead thread, but the links to the 3.1 version of the ROM is still there. I use the apps2SD version of the 3.1 ROM.
There are several more ROMs that are more recent, but this one is the best one I have ever found. You will need to root your phone and install a custom recovery (like AmonRA or ClockworkMod) to use it, but I have found that everything works well and it is extremely stable. I have over 70 apps on my phone with over 80MB of internal memory still available.
The only problem I have ever had is an intermittent battery drain, which I was able to fix by wiping the cache files (Dalvik and regular caches). The custom recoveries have the ability to do this. Apparently any corruption of the cache files causes excessive battery drain, but wiping them (which causes the phone to rebuild them on the next boot - a 4 minute process!) gives you fresh cache files and fixes the problem.
If you are willing to learn how to root your phone and install a custom recovery, I can recommend that ROM. Once the first part is done, loading a custom ROM is as easy as putting the zipped ROM file on your SD card, getting to the bootloader and telling it to install the zip.

Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.

addam360 said:
Well just so you know, rooting or installing any ROM will never stop the touch input problems. Its my main dislike about the N1. Apps2SD would solve your storage issues though and all the extra little perks of rooting just sweeten the deal.
Replacing a phone is expensive and just not necessary for the N1 yet. May as well root in my opinion. CM7.1 is now perfectly stable, include trackball wake, can support A2SD as far as I know and has some nice extras too.
As well as that it shouldn't be TOO much longer until we get a decent ICS ROM.
Hope that helps you.
Click to expand...
Click to collapse
Thanks. I never expected the new ROM to fix the touch input problems. That is a fundamental hardware issue.
I was thinking along the same lines regarding ICS. It's gone AOS now and I now see somebody has built a port for the N1 already. So if I wait a bit if I choose to install some custom firmware, if the reports suggest ICS runs fine on the N1 (to confirm that Google didn't release it because there was a performance issue with the N1 and ICS) then that's the route I will take. In for a penny, in for a pound I guess!

lchiu7 said:
(to confirm that Google didn't release it because there was a performance issue with the N1 and ICS)
Click to expand...
Click to collapse
The issue is not because of performance, its the system partition size is not enough... Gosh! Did u know Galaxy Nexus's system dump is 600MB+

[Q] Having problems with rooted SGH-T679 running CyanogenMod 10

Hello everyone, thanks for taking the time to read my thread. i'm really having a hard time here. I'm trying to take pictures, but it has become so unstable, and I can't reply. and it keeps saying i don't have any space in my SD. I've NEVER had this problem with my other ROM/Default.
There are 2 SDs, one is the one i bought and put it, so i can put all my music and i thought the other i would be able to have it for pics and other stuff. But I can't see it. i've taken out so much music to try and make space (like 10 folders/albums). But it's still saying it doesn't have enough space.
I'm right now rooted. used ClockworkMod then installed CM10 I believe. or CM11 and right now i'm running android (I went from a 2.3.6) to 4.1.2. on an SGH-T679 and the ROM is CyanogenMod version, Build date Apr 2, 16H EDT 2019, CyanogenMod version 10-20130402-UNOFFICIAL-Ancora_tmo. I hope that's enough info.
So I'm guessing if anyone from these forums. Has anyone been through this? Or has heard of someone else having problems. Because my #1 thing is just walking around NYC, taking pics. But when I can only walk around and like take 3 or 4 pics. i'm like :crying: all day. And i don't have the $ to just buy a camera like that.
P.S. and since yesterday, It takes longer to load the battery while charging unlike before. I thought that it was weird. But then to waste/discharge the battery.
Thank you

This may or may not solve your problem, sometimes there are hidden files that stay on your internal storage and eat up all your room. In your file manager enable hidden files, then look for things you can remove. One of hem right off the bat would be .thumbnails, I'm sure there are more but honestly you have to look around your storage, there may be old downloads or cache files that are still there. Hope this helps.

I think i flashed my ROM, data, cache, dalvik-cache and I think data was the last one. and since i've done that. I can't start my phone. It says samsung. then the samsung cyanogenmod start up screen, and it just hangs there. can anyone help me with this pls? I pressed
start button + down volume button. Then it says that it's going to download the OS for me. But i think that just hangs too cause it takes a while. and then it goes back to the start up screens that won't go anywhere.
Thanks D'vari, but unfortunately i think i'm passed that. Now i need to know just how to start my phone and get it past the phone.

You probably have conflicting data somewhere. Try power + volume up. That should get you into recovery. Then wipe everything except system and you should be able to boot up.

It took so long, because i read somewhere else to press vol down + power button. so i was trying. And It got me into Odin, and that said an OS is important, do you want to dl an OS now? so i said, well, i don't think i even have one left, so i chose yes. then it would say it was downloading for hours. but then it would boot up into the boot up screen loop. which was kind of good, but i didn't think so at the moment. Then i read how to get into cwm in my phone. so then i did it, and i had to do an advanced restore before regular restore was coming back MD5 mismatch. So It's like i flashed my old system, restored it to factory cyanogenmod factory. Tomorrow i'll flash cm10 and google apps and something else that had swipe working on this phone. maybe it was just upgrading to CM10, because now it's in version 9 and swipe is not working.
Thanks for your help

cyanogenmod issues as well
I had the same issue last week when updating to 10.1. but it did say that it may take a while to boot up. I didn't stress it. I just plugged it in by my bed and went to bed. when I woke up the next morning, I had it!
I did the volume up/power-wipe clean-reboot and then I slept. give that a try. maybe you are just like me and worrying that it is taking too long and you have F-ed up your phone!
On a different note, this 10.1 is awesome. But I can't get it to recognize my sd card. it does show that one is mounted but wont save anything and wont let me access the files. I have wiped the sd card clean and formatted to fat32. but that is doing nothing for me. any other suggestions here? I need my music and the space! this is taking so much time, it almost isn't worth the effort. but I love the cyanogenmod 10.1. but can't keep if it wont work right. ???
Deefex said:
It took so long, because i read somewhere else to press vol down + power button. so i was trying. And It got me into Odin, and that said an OS is important, do you want to dl an OS now? so i said, well, i don't think i even have one left, so i chose yes. then it would say it was downloading for hours. but then it would boot up into the boot up screen loop. which was kind of good, but i didn't think so at the moment. Then i read how to get into cwm in my phone. so then i did it, and i had to do an advanced restore before regular restore was coming back MD5 mismatch. So It's like i flashed my old system, restored it to factory cyanogenmod factory. Tomorrow i'll flash cm10 and google apps and something else that had swipe working on this phone. maybe it was just upgrading to CM10, because now it's in version 9 and swipe is not working.
Thanks for your help
Click to expand...
Click to collapse

I'm using pac 4.2 and I can switch were I want my pics stored from the camera settings maybe that ROM would help your situtation.

Thank you for all your help. But i decided to switch over to JellyBean. But i've been having some minor problems with it. I just flashed this ROM after doing something stupid in CWM (as you all know) while using cyanogen. I actually really like this ROM. I though CM10 futuristic looking. this beats that by a lot of points. I just have a problem now. The icons in the apps menu/section, are spaced too far apart. IDK what I did to cause this. Cause i was messing with those options of icons rows and colums for the desktop, but i set it back to default and that still didn't do anything to the apps section.
The other problem I'm having is with the camera. I try to open it, but it just says camera can't go on, 'wait-report-close'. That type of message. IDK what it is because the main reason for switching was to be able to take lots of pics. I love taking pics with my phone. And i found out what had my internal memory soooo clogged up. I had a .txt music cache file that was 848MB. Once I erased that, I know have 50% free space.
It looks really retarded . I know i'll fix it somehow, someday. I think there's even an upgrade now for slimbean, maybe I should try that. But right now i'm in google play store. in the 'my apps' list. and going through what i used to have, and installing my old apps, one by one. a grueling task, but I really want to use this ROM as my main rom.

[Q] Power-On Lag/Freezeing

So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)

I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.

wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).

Samsung Galaxy S3 GT-i9305 random restarts even in Safe Mode

Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!

Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!

Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.

Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...

fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!

SM-N910F resurrection following eMMC issues

tldr; the thing with the oven appears to have worked, although you'd have to be stupid, desperate, or both to try it.
Much loved Galaxy Note 4 SM-N910F started to fail with freezes, reboots and so on. Looks like a phone dying of eMMC failure, according to the bulk of articles on the specific symptoms.
Happily, I'd replaced it (with a Note 10 - lovely phone, but not as revolutionary-lovely as the Note 4 was when it was new), and had had six years of happy use out of the thing. I could bin it with my head held high.
Might have a go at recovering it, though.
Attempts to factory reset failed, resulting in boot to download mode "Firmware Update Encountered An Issue" scary screen... I see. This could be a fun challenge before I bin it then!
Odin flash of Stock ROM fell over repeatedly with various fails - often with 'mmc read' and 'could not do normal boot' scary screens
Various versions and vintages of Odin all produced similar results
Un-brick seemed to work, in as much as I could then flash TWRP (https://forum.xda-developers.com/note-4/help/samsung-galaxy-note4-sm-n910f-unbrick-t3552826)
TWRP flashing of any rom seemed to fail and fall over - generally 5-10% (guess) into the process.
Now getting bolder, tried re-partitioning, various PIT files, NAND erase, and all the forbidden things. The errors kept coming, and my 'unbrick' microSD was earning its keep.
The thing is, I really liked this phone - and I wanted it to try newer ROMs on and so forth, so I resisted the urge to chuck it in the bin. That, and finding things like using TWRP terminal mode to re-format /system and /data in different partition types, and then back to ext4, seemed to improve matters - if only temporarily - all suggested that there might be life in the old girl yet.
A couple of my searches came across articles like this and this, that suggested that the issue might have to do with failing solder joints rather than the eMMC itself and ... well then they talked about putting your phone in the oven, and I dismissed them as madness.
I mean, if putting your phone in the oven would 'reflow' dodgy solder, it would re-flow ALL the solder in the phone, right? Makes no sense. Bloody stupid.
Not going to fall for some obvious troll hoax.
So I put my phone in a 100 deg C oven for 5 mins. Took it out, and let it cool to room temperature slowly over a couple of hours.
Now
Odin can flash a whole stock ROM with success
TWRP can flash a whole non-stock ROM with success
Odin can re-flash a whole stoc... oh. Failed at around 80%. Poo.
TWRP managed a reflash, though!
Odin managed a whole stock reflash, again!
Setting up the flashed phone, though, results in freezes and boot loops. Damnit.
Another day of frustrated mucking about, hovering the thing over the bin.
OK, one more go. This time 120 deg C for 6 minutes.
This time
First and every subsequent re-flash, in Odin and TWRP, works fine.
Odin'd it back to stock, then wipe and factory reset. All fine.
Reconfig process passes without incident.
Google Play updating itself and ALL THE APPS works fine.
Setting up accounts, streaming Youtube for hours, playing games... all fine. Much more stable than it'd been in a while.
It's been a week, now, without incident.
So I thought I'd mention it.
But I still think you'd need to be an idiot to bake your phone in the hope that it'd do *anything* other than make things much worse, right?

charleshking said:
But I still think you'd need to be an idiot to bake your phone in the hope that it'd do *anything* other than make things much worse, right?
Click to expand...
Click to collapse
Maybe.
There's an app called Wake Lock - PowerManager - I've installed on my son's 910F since a month or so and the phone still works.
It'll slightly take it's toll on battery, but hey you save some $ for the next phone.

@charleshking: Reflowing def does work, I know a guy that had to do it 3 times within 6 months to fix his gaming laptop. But it's only meant to be a temp fix, sooner or later the oven thing won't work (failed on him after the 4th try).
The Wake Lock manager app just holds open a wake lock so the phone never enters deep sleep/doze mode, which in the case of an EMMC failing phone can cause it to not wake up.
Last year I had a Note 4 T-Mobile N910T which had a failing EMMC, it had most of the issues you mentioned. But eventually it died, it caught on fire while I was charging it. I now have an N910T which is working with no issues, bought new on eBay almost a year ago.