ads

Affichage des articles dont le libellé est n7000. Afficher tous les articles
Affichage des articles dont le libellé est n7000. Afficher tous les articles

vendredi 2 octobre 2015

N7000 not turning on properly



My N7000 turned itself off the other day without a battery warning.
Everytime I press the power button the Samsung Galaxy screen comes on and then turns itself off again.
Same if I try to go into recovery mode the android icon comes up and then it turns itself off.
The phone is stock standard no mods at all.
Battery says 100%.
Any help would be appreciated.



samedi 26 septembre 2015

n7000 stuck on boot logo (nightowl 20150913)



I was running the latest night owl rom just fine. This morning however the phone was stuck on boot logo.
Restart, taking out the battery and even reflashing the rom or other versions doesn't help.
I can still access recovery (philz touch 6). I can wipe cache and format /cache but the phone crashes/reboots on wipe dalvik/art.

any suggestions?

thanks!



Seeking Custom ROM for N7000 with multi user function



Hi there,

i want to use my old Samsung Galaxy Note as Tablet for my little daugters. To protect the Phone (and also my daughters), i want use the multi user feature to be able to install Apps with my accounts and let her start only less alowed apps.

I always try some Custom ROMS with Android 4.2 or higher. But all of them without the Multiuser feature.

Could anybody provide me the name of a Custom ROM that provide the multi user function ? I found a old thred, that Revolt should support that. But the Version of the Revolt ROM that i found, was without this feature.

cu, Thiemo



jeudi 24 septembre 2015

A story of a drowned and almost recovered N7000



The story
I've put my n7000 by the sink, set water running and got distracted. By the time I came back my n7000 was lying in the water. I've just wiped it with a towel and put it aside with a careless thought "Wth, it's not the first time. Nothing bad can happen. This device is bulletproof!", after a couple of hours the device went to a reboot and started to shutdown completely each time it went to a sleep mode (reboots took 5-10 minutes). Also it was completely silent :(

Damage assess

After taking the device apart I saw some white residue under the Yamacha's mc1n2 audio chip, cleaned all the boards with alcohol and dried all the parts. Still the same symptoms where there: long boot times, no audio, shutdown in sleep mode, also the sound chip was getting warm quickly. Sad. ADB logs where showing errors of ALSA not finding a sound card and some mc1n2 related errors. The chip was dead.

Trying to recover
Took out my hot air gun and removed the chip completely, cleaned solder from the chip pads on the board. Hooray! Back to normal boot times! (Now definitely no audio :cyclops:) But still ALSA and mc1n2 related errors in the logs (was running latest CM 12.1 NightOwl rom). Also found another problem: couldn't get any audio even through bluetooth, all audio players where not even trying to play files, video players complainig that any video file cannot be played, only got success with MX Player's software codec, no audio through bluetooth though. Started experimenting with the CM 12.1 NightOwl rom sources, managed to build it (It would be nice if they had some simple instructions on how to configure and build it in the dedicated rom thread, can't post there due to noobs 10 posts limit). In the device's config settings found

Code:


# Audio
BOARD_USE_TINYALSA_AUDIO := true
BOARD_USE_YAMAHA_MC1N2_AUDIO := true


and set both to false. Yay! Bluetooth audio is back, players working! Still the problem with shutdowns in sleep mode remains, must be something with the SOC itself, or the power managing chip. Ended up installing "Wake Lock - PowerManager" and setting it up to start on boot and set a partial wakelock to keep the CPU awake.

Now I got almost working device to continue pushing it to the limit :)

The end :victory:

The question: could someone point out the low level parts of CM 12.1 and kernel responsible for putting the device into sleep (may be it is possible to narrow down the shutdown issue an somewhat fix it without having to keep the whole CPU awake)?